Differences

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

--- uc:uc20230404_april_4_2023 [2023/04/05 19:42] – nchanove
+++ uc:uc20230404_april_4_2023 [2023/04/06 22:36] (current) – nchanove
@@ Line 12: / Line 12: @@
   * Washington - nothing to report
   * BYU - nothing to report
-  * Colorado - a user reported the IRAF data reduction guides and scripts for ARCTIC are not available through the wiki any more (referring to this page: [[http://astronomy.nmsu.edu/apo-wiki/doku.php?id=arctic]]). **Nancy will track this down and get the wiki updated.**
+  * Colorado - a user reported that the IRAF data reduction guides and scripts for ARCTIC (from Karen Kinemuchi) are not available through the wiki any more (referring to this page: [[http://astronomy.nmsu.edu/apo-wiki/doku.php?id=arctic]]). **Nancy will track this down and get the wiki updated.**
   * JHU - nothing to report
-  * Oklahoma - Muk previously had some questions about the timing information in Agile image headers and Russet and Bill looked into it; Muk thanked them for their efforts. He is looking forward to his OU class visit next week coming (which will include Muk, a TA and 5 students)
+  * Oklahoma - Muk previously had some questions about the timing information in Agile image headers and Russet and Bill looked into it; Muk thanked them for their efforts. He is looking forward to his OU class visit next week (which will include Muk, a TA and 5 students)
   * Georgia State - nothing to report
   * FGCU - nothing to report
@@ Line 62: / Line 62: @@
 === Additional telescope and instrument discussion ===
-March/Apr busy with visitors. BYUCam is ready for community use.
+March and April are busy months with numerous visitors coming to the site. BYUCam on ARCSAT is ready for community use. The Agile image timestamps are accurate but the sync issue is still being investigated. The ARCTIC diffuser rotation issue that was seen during cold temperatures has been fixed. The control software is not giving a valid rotation flag (i.e. when it is rotating at speed the flag is not registering). We recommend that users continue to use the instrument (with the diffuser rotation) as is. It looks like the rotation is still happening at proper speed; it may be slightly below the nominal 2 Hz threshold but until Bill can take it apart and clean it we won't know for sure. For this week, as long as the star's diffraction spikes are being smeared out it should be considered acceptable for science (if not, we recommend defocussing the instrument a bit). There is an issue with a ghost image in the TripleSpec data that Russet is investigating. We are meeting with Lowell Observatory engineers next week to discuss M1 realuminization. Users are urged to upgrade to python3 if they have not already done so, and to use the latest python3 version of TUI. Because python2 is no longer being supported we will not be able to support or troubleshoot the python2-based version of TUI any longer.
-Agile timestamps are accurate but sync issue still being investigated
-ARCTIC diffuser rotation issues w/cold temps fixed - not giving valid rotation flag - at speed flag is not registering - recommend that users use instrument as is - looks like rotation is at proper speed, maybe slightly below 2Hz threshold but until can take it apart and clean it won't know what problem is - for this week, as long as diffraction spikes are being smeared out it is acceptable to science, otherwise recommend defocus
-issue w/ghost image on Tspec that Russet is investigating
-meeting w/Lowell next week
-python3 tui - need to upgrade
-we can't troubleshoot python 2 version any longer
 ----
@@ Line 76: / Line 68: @@
 === KOSMOS update ===
-ST - looked at smear users were seeing in overscan w/bright lines
+When Sarah was at APO a couple of weeks ago she spent some time looking at the smear users were seeing in the overscan with bright lines. She played around with some voltages to check if it is due to a serial readout problem. Of note to all KOSMOS users, the way the detecter controller is currently working, it shows as being saturated at the ADC maximum, not the chip full well depth, meaning it will go up to 2^18 counts before it overflows. Somewhere between 150k-200k is the physical full well. She is still doing tests to quantify this, but **KOSMOS users should be aware that very high count levels (> 150k) are not physical.** Sarah got some help from a CTIO colleague who worked on COSMOS and got the information she needed so now she can test the voltages. The chip is currently optimized for a single amplifier but the goal is to be able to run it using one OR two amplifiers. The instrument is currently in a stable state and we will always leave it in its default state after testing. That said, users should notify their observing specialist and Sarah Tuttle if they have questions or encounter something out of the ordinary.
-serial readout problem? play around with voltages
-the way detecter controller is working, saturated at ADC max not chip full well, will go up to 2^18 counts before overflows. Somewhere between 150k-200k is physical full well - still doing tests to quantify
-but users should be aware that very high count levels are not physical (> 150k)
-contacted CTIO colleague (COSMOS) - got questions answered and now can test voltages
-the way it is is stable
-goal is to have running file - chip optimized for single amplifier, goal is to be able to run one OR two amps, will always leave it in default state
-let ST know if have questions or encounter something exciting
-Joanne - coming down in May, getting sources to have slit masks made by end of week - can test
+Joanne is coming to APO in May and hopes to have the files ready for slit mask production by end of this week. She offered to test other slit masks if users have any additional masks that they would like to get tested.
 ----
@@ Line 92: / Line 77: @@
 === Q2 3.5m scheduling ===
-OPEN time at end of Apr - 3 A halves - ppl can request, esp if recent weather issues
+There is some unassigned time at end of April: 3 A halves, 2 partials and 1 unencumbered. Users are encouraged to request this time if they can make use of it (particularly those who have been weathered out recently). As a reminder, users should include Ben, Russet, Amanda, Nancy and their institutional scheduler on all schedule related emails.
- are partials and 1 is unencumbered
-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 101: / Line 83: @@
 === Q2 ARCSAT scheduling ===
-Working out ARCSAT schedule - will have it figured out by end of this week
+We are working out some final details on the Q2 ARCSAT schedule and will have it finalized and posted by the end of this week.
 ----
@@ Line 113: / Line 95: @@
      * the Search Site function on the APO home page does not work. //A notice was 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.
-  * Nancy or Russet: get sample KOSMOS data from JHU user who reported scattered light issue. Status: CLOSED. This issue has been worked directly with the user.
   * Nancy: get updated on pyKOSMOS and report to UC next month. Status: OPEN.
+  * UC reps: notify your users about the option of using pyvista (and/or some of the other packages listed above) for data reduction. -> CLOSED
+  * 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. -> CLOSED
+  * 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). -> CLOSED
+  * 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. -> CLOSED
 New action items from this meeting:
- * UC reps: notify your users about the option of using pyvista (and/or some of the other packages listed above) for data reduction. Status: CLOSED.
+  * Nancy: track down missing ARCTIC data reduction scripts for wiki.
-  * 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: notify your KOSMOS users that counts > 150k are not physical.
-  * 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 to review the Q2 schedule and request OPEN/DD time if they can make a good case for it.
-  * 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.
 ----
@@ Line 127: / Line 110: @@
 === All Other Business ===
-AAS meeting in Albuquerque June 4-8
+The June 2023 AAS meeting will be held in Albuquerque on June 4-8. Although we are not normally in the habit of having an exhibitor booth at the summer meetings, particularly after just having been at the preceding winter meeting, we (APO) will have a booth at this meeting given its proximity to APO. It represents an excellent opportunity to highlight exciting science results enabled by a New Mexico-based astronomical facility like APO. If anyone from our ARC member institutions or lease partners is planning to attend the June AAS meeting please let Nancy know so we can promote their work!
 ----