User Tools

Site Tools


uc:uc2026

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
uc:uc2026 [2026/08/06 22:36] nchanoveuc:uc2026 [2026/08/06 22:42] (current) nchanove
Line 79: Line 79:
 Everything else is performing well. Agile and DIS have been decommissioned. APOLLO had some laser power adjustments. KOSMOS is cold and stable. Coming out of shutdown there were a few issues with the 3.5m telescope but those have been stable the last few days and hopefully can be addressed during the next engineering time. Everything else is performing well. Agile and DIS have been decommissioned. APOLLO had some laser power adjustments. KOSMOS is cold and stable. Coming out of shutdown there were a few issues with the 3.5m telescope but those have been stable the last few days and hopefully can be addressed during the next engineering time.
  
-Shutdown itself went very well. The report contains the latest updates concerning the situation at Sunspot. +Shutdown itself went very well. The site report above contains the latest updates concerning the situation at Sunspot. 
  
 Although this is generally a good practice, in light of the aforementioned instrument issues we recommend that Q4 proposers try to identify backup programs that would make use of a different instrument. Most importantly, observers should inspect their data as they are being acquired as this is the fastest way for the observatory staff to learn about and address problems that may arise. Although this is generally a good practice, in light of the aforementioned instrument issues we recommend that Q4 proposers try to identify backup programs that would make use of a different instrument. Most importantly, observers should inspect their data as they are being acquired as this is the fastest way for the observatory staff to learn about and address problems that may arise.
Line 91: Line 91:
 === 2026 Q4 3.5m scheduling === === 2026 Q4 3.5m scheduling ===
  
-The Q4 institutional allocations were sent out yesterday; proposals are due on August 25. In light of the anticipated housing crunch due to the loss of the housing trailer at Sunspot, it is //imperative// that anyone planning a class visit in Q4 should notify the scheduling team ASAP so we can understand the need for on-site accommodations.+The Q4 institutional allocations were sent out yesterday; proposals are due on August 25. In light of the anticipated on-site housing crunch due to the loss of the housing trailer at Sunspot, it is //imperative// that anyone planning a class visit in Q4 should notify the scheduling team ASAP so we can understand the need for on-site accommodations.
  
 === 2026 Q3 0.5 scheduling === === 2026 Q3 0.5 scheduling ===
Line 103: Line 103:
 As reported in last month's minutes, Jon Holtzman has added modules for KOSMOS and TripleSpec into the development branch of PypeIt. If there are any users that would be interested in trying those, they can do so if they download this version (e.g., see [[https://pypeit.readthedocs.io/en/stable/installing.html#development-or-pre-release-versions]], they would want the develop branch). If anyone has any questions they can contact Jon directly. These should be included in a release version relatively soon; it would be great to get some test users even sooner!  As reported in last month's minutes, Jon Holtzman has added modules for KOSMOS and TripleSpec into the development branch of PypeIt. If there are any users that would be interested in trying those, they can do so if they download this version (e.g., see [[https://pypeit.readthedocs.io/en/stable/installing.html#development-or-pre-release-versions]], they would want the develop branch). If anyone has any questions they can contact Jon directly. These should be included in a release version relatively soon; it would be great to get some test users even sooner! 
  
-Nancy reiterated the need a user group devoted to software testing (at the moment, for KOSMOS and TripleSpec users to try out these PypeIt modules). Adam K indicated that he is willing to help. UC reps: please ask your users (and/or work with your institutional schedulers to identify your KOSMOS and TripleSpec users) to help out with this testing and to have those users communicate with Jon Holtzman about their experiences.+Nancy reiterated the need for a user group devoted to software testing (at the moment, especially for KOSMOS and TripleSpec users to try out these PypeIt modules). Adam K indicated that he is willing to help. UC reps: please ask your users (and/or work with your institutional schedulers to identify your KOSMOS and TripleSpec users) to help out with this testing and to have those users communicate with Jon Holtzman about their experiences.
  
 ---- ----
Line 118: Line 118:
 === Pilot data archive with NOIRLab ===  === Pilot data archive with NOIRLab === 
  
-We are moving forward with the arrangement to have ARC 3.5m data ingested into the NOIRLab data archive. We will pilot this first with a single instrument (likely ARCES), which will allow us to work out any kinks. The decision was made to have this be an OPT-OUT arrangement, i.e. ARCES observations will automatically be sent over to NOIRLab (where they will remain not broadly accessible until after a TBD proprietary period) unless a user decides to opt out. Please direct all questions and comments to Nancy.+We are moving forward with an arrangement to have ARC 3.5m data ingested into the NOIRLab data archive. We will pilot this first with a single instrument (likely ARCES), which will allow us to work out any kinks. The decision was made to have this be an OPT-OUT arrangement, i.e. ARCES observations will automatically be sent over to NOIRLab (where they will remain not broadly accessible until after a TBD proprietary period) unless a user decides to opt out. Please direct all questions and comments to Nancy. 
 + 
 +----
  
 === ACTION ITEMS ===  === ACTION ITEMS === 
uc/uc2026.1786055817.txt.gz · Last modified: by nchanove

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki