apo-wiki

User Tools

Site Tools

Trace:
uc:uc20230307_march_7_2023

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
uc:uc20230307_march_7_2023 [2023/03/07 21:51]
nchanove 		uc:uc20230307_march_7_2023 [2023/03/07 22:59] (current)
nchanove
Line 58: Line 58:
 === Additional telescope and instrument discussion ===  === Additional telescope and instrument discussion === 
  
-The observatory has been hit with several snow storms that have significantly impacted observing over the past few weeks. The forecast is improving for the next week or so. March is shaping up to be a busy month: the UVa/DSSI team is here now, a CU class will be on site next week, and Sarah Tuttle will be here the week of March 20th for KOSMOS work. More visitors will be coming in Q2, so we expect to be remain quite busy through June. TUI work is continuing, with a Docker mode in the works. The ARCTIC diffuser has been acting up in cold weather; investigations into that issue are underway. The issue of the Agile time stamps in the image headers being incorrect is actively being worked on. The issue is with the trigger signal that comes from the high speed/high accuracy clock that's in the ICC machine. For users, this might be manifested as an error message, or it could affect header information even if there is no error message. The image time stamps are intended to be accurate to 0.01 s but currently there is no way to test that because the other machines are less accurate. Users should assume that the exact time stamps in their Agile image headers are unreliable, although the length of exposures and the photometry are both still fine. It is really just the precise timing that is affected; this issue started in mid-January. DIS scattered light is behaving as expected. There is a current issue with the TripleSpec instrument cart, which does not affect observing but does affect instrument fills during the day. As a result it could be taking longer to mount/unmount the instrument until the cart gets repaired; parts are on order. Work is proceeding for getting the 3.5m mirror ready for realuminization at Lowell this summer. We heard from KPNO that they will not be able to accommodate any external mirrors at their coating chamber this summer, so it's good that we decided to proceed with having the work done at Lowell.+The observatory has been hit with several snow storms that have significantly impacted observing over the past few weeks. The forecast is improving for the next week or so. March is shaping up to be a busy month: the UVa/DSSI team is here now, a CU class will be on site next week, and Sarah Tuttle will be here the week of March 20th for KOSMOS work. More visitors will be coming in Q2, so we expect to be remain quite busy through June. 
 + 
 +TUI work is continuing, with a Docker mode in the works. 
 + 
 +Instrument updates: 
 + 
 +  * The ARCTIC diffuser has been acting up in cold weather; investigations into that issue are underway. 
 +  * The issue of the Agile time stamps in the image headers being incorrect is actively being worked on. The issue is with the trigger signal that comes from the high speed/high accuracy clock that's in the ICC machine. For users, this might be manifested as an error message, or it could affect header information even if there is no error message. The image time stamps are intended to be accurate to 0.01 s but currently there is no way to test that because the other machines are less accurate. Users should assume that the exact time stamps in their Agile image headers are unreliable, although the length of exposures and the photometry are both still fine. It is really just the precise timing that is affected; this issue started in mid-January. 
 +  * DIS scattered light is behaving as expected. 
 +  * There is a current issue with the TripleSpec instrument cart, which does not affect observing but does affect instrument fills during the day. As a result it could take longer to mount/unmount the instrument until the cart gets repaired; parts are on order. 
 + 
 +Work is proceeding for getting the 3.5m mirror ready for realuminization at Lowell this summer. We heard from KPNO that they will not be able to accommodate any external mirrors at their coating chamber this summer, so it's good that we decided to proceed with having the work done at Lowell.
  
 ---- ----
Line 66: Line 77:
 In response to last month's action item to provide an update on quick-look data reduction software (in that context, for KOSMOS), we discussed several software options. pyKOSMOS is still in development and we were unable to get a status update before this meeting; Sarah will keep trying. In response to last month's action item to provide an update on quick-look data reduction software (in that context, for KOSMOS), we discussed several software options. pyKOSMOS is still in development and we were unable to get a status update before this meeting; Sarah will keep trying.
  
-Jon Holtzman presented an overview of pyvista, which he has been developing for several years. pyvista is intended to be a general purpose software package for reducing astronomical data (imaging and spectroscopy), although it was developed with APO instruments in mind. It is not intended to have a lot of fancy bells and whistles, but it does have a pedagogical aspect to it (i.e. it is not a black box) and is used to teach both undergraduates and graduate students about data reduction. Interested users can read more about it here: https://pyvista.readthedocs.io/en/latest/ and are welcome to give it a try; please contact Jon (holtz@nmsu.edu) with any questions. Several people at NMSU are using it for reducing their ARCES, KOSMOS, and DIS data; the photometry and TripleSpec packages are not done or fully documented yet. The spectroscopy reduction code builds off existing calibration spectra, and can include automated line identification. It propagates uncertainties through the pipeline and can display S/N images.+Jon Holtzman presented an overview of pyvista, which he has been developing for several years. pyvista is intended to be a general purpose software package for reducing astronomical data (imaging and spectroscopy), although it was developed with APO instruments in mind. It is not intended to have a lot of fancy bells and whistles, but it does have a pedagogical aspect to it (i.e. it is not a black box) and is used to teach both undergraduates and graduate students about data reduction. Interested users can read more about it here: https://pyvista.readthedocs.io/en/latest/ and are welcome to give it a try; please contact Jon (holtz@nmsu.edu) with any questions. Several people at NMSU are using it to reduce their ARCES, KOSMOS, and DIS data; the photometry and TripleSpec packages are not done or fully documented yet. The spectroscopy reduction code builds off existing calibration spectra, and can include automated line identification. It propagates uncertainties through the pipeline and can display S/N images.
  
 Other options for reducing spectrograph data include PypeIt (developed by X. Prochaska with a significant number of supporting helpers) and PyReduce. Eric B. reported that he tried to get PypeIt working with DIS data and had limited success; if someone wants to build on what he started it is possible, but it's a complex piece of software. Kevin reported that his group is using CERES to reduce ARCES data: https://github.com/rabrahm/ceres. Other options for reducing spectrograph data include PypeIt (developed by X. Prochaska with a significant number of supporting helpers) and PyReduce. Eric B. reported that he tried to get PypeIt working with DIS data and had limited success; if someone wants to build on what he started it is possible, but it's a complex piece of software. Kevin reported that his group is using CERES to reduce ARCES data: https://github.com/rabrahm/ceres.
Line 80: Line 91:
 Plans for a multi-band imager are still being formulated, and require discussions with the UVa instrument team to flesh out how such an instrument would fit into their planned progression of instrument development efforts. Plans for a multi-band imager are still being formulated, and require discussions with the UVa instrument team to flesh out how such an instrument would fit into their planned progression of instrument development efforts.
  
-Regarding a new echelle spectrograph, a small team from JHU and UVa is working on a conceptual design. In parallel with that, Nancy has assembled a small tiger team of active echelle users to outline the science requirements that will flow down to instrument performance requirements, and to help develop the science case(s) that will be used to pursue external funding for the instrument. She is seeking 1-2 more echelle users for the tiger team, so Users Committee members were asked to forward this information to their department members and let her know if they have any recommendations or volunteers who would be willing to serve on this team. +Regarding a new echelle spectrograph, a small team from JHU and UVa is working on a conceptual design. In parallel with that, Nancy is assembling a small tiger team of active echelle users to outline the science requirements that will flow down to instrument performance requirements, and to help develop the science case(s) that will be used to pursue external funding for the instrument. She is seeking 1-2 more echelle users for the tiger team, so Users Committee members were asked to forward this information to their department members and let her know if they have any recommendations or volunteers who would be willing to serve on this team. 
  
 +----
  
 === Q1 3.5m scheduling === === Q1 3.5m scheduling ===
  
-There is one unassigned dates remaining in the Q1 schedule (Mar 27B), for which we have already received a request. High priority requests will still be considered; a decision on how to allocate this time will likely be made next week.+There is one unassigned date remaining in the Q1 schedule (Mar 27B), for which we have already received a request. High priority requests will still be considered; a decision on how to allocate this time will likely be made next week.
  
 ---- ----
Line 91: Line 103:
 === Q2 3.5m scheduling === === Q2 3.5m scheduling ===
  
-The Q2 schedule is in draft form and is nearly complete; we expect to be able to publish it before the end of this week. In Q2 we are expecting 3 visiting instrument runs (wit 2 different instruments) along with 4 on-site class groups, not too many programs requesting regular monitoring partial nights but do have a lot of programs requiring specific events on specific dates crossing midnight boundary - lots of partial nights - almost ready to go - waiting for 1-2 questions, some open time but not sure when +The Q2 schedule is in draft form and is nearly complete; we expect to be able to publish it before the end of this week. In Q2 we are expecting 3 visiting instrument runs (with 2 different instruments) along with 4 on-site class groups. There were not too many programs that requested numerous partial nights (e.g. for a monitoring program) but we did receive requests from quite a few programs requiring observing time for specific events on specific dates that cross the midnight (A/B half) boundary, which means there ended up being lots of partial nights in the schedule. We are awaiting answers to a couple of outstanding questions and then the schedule will be published. 
-only have 1 person signed up for remote training + 
-despite our requests to get them in before schedule is made, considering not offering remote training in Q2 +We only have one person signed up for the Q2 remote training opportunity that we offer for postdocs, research faculty, etc. so we may not offer a remote training in Q2. Despite our requests to receive notification about remote training needs well in advance of building the schedule (this information is conveyed every quarter in the allocation emails sent to the institutional schedulers), we generally receive these requests well after the schedule is made, which is problematic. **Users Committee: please poll your department users and if there is a need for a remote training option for Q2, notify Russet ASAP (within the next day or so).**
-poll users, let us know ASAP+
  
 ---- ----
Line 100: Line 111:
 === Q1 ARCSAT scheduling === === Q1 ARCSAT scheduling ===
  
-Notify us if not using entire week +The Q1 ARCSAT schedule has some open slots. **UC reps: please remind your users that they should notify us if their plans change and they will not use their ARCSAT time.** We recognize that sometimes people make last-minute decisions based on weather and that's fine; we're asking that if someone decides to not make use of their entire week of scheduled time, they notify Russet, Nancy, and Ben. This can help us by avoiding unnecessary instrument changes and scheduling ARCSAT engineering time to fill the schedule gaps.
  
 ---- ----
Line 109: Line 119:
 Open action items from previous meetings: Open action items from previous meetings:
  
-  * Nancy: make sure that the APO web site gets updated to address the issues reported by Eric B. in December. Status: OPEN. There were several issue that needed to be addressed:+  * Nancy: make sure that the APO web site gets updated to address the issues reported by Eric B. in December. Status: OPEN. There is one remaining issue that needs to be addressed:
      * the wiki link on the 3.5m page still pointed to the old wiki - //this was fixed.//      * the wiki link on the 3.5m page still pointed to the old wiki - //this was fixed.//
-     * the Search Site function on the APO home page does not work. //Testing is ongoing to solve this;// it appears to be a VPN issue for the site web server (i.e., it works for people at APO but does not work for people accessing the web pages from off-site locations).+     * the Search Site function on the APO home page does not work. //A notice will be added to reflect the fact that this search tool will not work from computers outside of the APO VPN.//
      * the ToO policy is not easily found. //We are working on a document// that we can post on the scheduling page to make this information more easy to locate.      * the ToO policy is not easily found. //We are working on a document// that we can post on the scheduling page to make this information more easy to locate.
-  * Nancy or Russet: get sample KOSMOS data from JHU user who reported scattered light issue. Status: CLOSED. its not slit viewer it is the spectra - concerned - will talk to him (he went back to DIS for Q2 but DIS likely to bad) - Russet +  * Nancy or Russet: get sample KOSMOS data from JHU user who reported scattered light issue. Status: OPEN. Russet will contact the user to troubleshoot this, and will include Sarah and Nancy.
   * Nancy: share communications plan re: new instrumentation with UC at next meeting. Status: CLOSED.   * Nancy: share communications plan re: new instrumentation with UC at next meeting. Status: CLOSED.
   * Nancy: get updated on pyKOSMOS and report to UC next month. Status: OPEN.    * Nancy: get updated on pyKOSMOS and report to UC next month. Status: OPEN. 
Line 120: Line 130:
 New action items from this meeting: New action items from this meeting:
  
-  * xxx+  * UC reps: notify your users about the option of using pyvista (and/or some of the other packages listed above) for data reduction. 
 +  * UC reps: notify your users that Nancy is seeking 1-2 more echelle users to participate in the tiger team charged with firming up the science requirements for a new echelle spectrograph. 
 +  * UC reps: poll your department users and if there is a need for a remote training in option for Q2, notify Russet ASAP (within the next day or so). 
 +  * UC reps: remind your users that they should notify us if their plans change and they wish to forfeit their week of scheduled ARCSAT time.
  
 ---- ----
uc/uc20230307_march_7_2023.1678225908.txt.gz · Last modified: 2023/03/07 21:51 by nchanove

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki