apo-wiki

User Tools

Site Tools

Trace: • uc20220503_may_3_2022 • uc20220802_august_2_2022
uc:uc20231003_october_3_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:uc20231003_october_3_2023 [2023/10/13 20:54]
nchanove 		uc:uc20231003_october_3_2023 [2023/10/13 22:53] (current)
nchanove
Line 1: Line 1:
-==== APO 3.5-m Users Committee Meeting, 09/05/2023 ====+==== APO 3.5-m Users Committee Meeting, 10/03/2023 ====
  
 ---- ----
Line 14: Line 14:
   * Seattle - thanks for help with recent site visit; we are still working out bugs related to aligning slit masks   * Seattle - thanks for help with recent site visit; we are still working out bugs related to aligning slit masks
   * Washington - nothing to report   * Washington - nothing to report
-  * Georgia State - - nothing to report+  * Georgia State - nothing to report
   * Colorado - nothing to report   * Colorado - nothing to report
   * Oklahoma - nothing to report   * Oklahoma - nothing to report
Line 61: Line 61:
 === Additional telescope and instrument discussion ===  === Additional telescope and instrument discussion === 
  
-We have had reasonable weather, although it has been very variable lately. In October into November we will be busy with class visits (NMSU followed by UVa followed by BYU). The M3 rotation issue was fixed. Efforts are still underway to improve the telescope balance and motion errors - next month we will tune the position integral derivatives (PID) parameters, We did restore the slew velocity settings and that seems to have improved things.+We have had reasonable weather, although it has been very variable lately. In October into November we will be busy with class visits (NMSU followed by UVa followed by BYU). The M3 rotation issue was fixed. Efforts are still underway to improve the telescope balance and motion errors; next month we will tune the position integral derivatives (PID) parameters. We did restore the slew velocity settings and that seems to have improved things.
  
 We have a used 7-position filter wheel that was donated by Oliver Fraser at UW to replace the broken one on the 0.5m. It is now installed and working, and we thank UW for the donation! We have a used 7-position filter wheel that was donated by Oliver Fraser at UW to replace the broken one on the 0.5m. It is now installed and working, and we thank UW for the donation!
  
-The instruments are generally behaving. The KOSMOS disperser wheel recently had an issue, where the command will sometimes time out when moving from red to blue. We have a plan for fixing it when it gets stuck, and have strategies laid out for how to deal with it if the problem recurs. In short, if it happens we will suggest that long slit users should rotate the slit by 180 degrees, and MOS users should rotate to a different empty position.+The instruments are generally behaving. The KOSMOS disperser wheel recently had an issue where the command will sometimes time out when moving from red to blue. We have a plan for fixing it when it gets stuck, and have strategies laid out for how to deal with it if the problem recurs. If it happens the Observing Specialist will suggest that long slit users should rotate the slit by 180 degrees, and MOS users should rotate to a different empty position.
  
-Regarding our recent cybersecurity efforts, we have been forced to clamp down on the outward facing computers. This has had no affect on operations (so far). We are looking at using Bit Defender, an enterprise-level service to lock down servers and prevent viruses. If anyone has an experience with using Bit Defender, please let Jamey know. Muk asked how frequently the site servers are backed up, noting that it was thanks to the daily backups that allowed Gemini to recover from their cyberattack as quickly as they did. Jamey replied that our machines are backed up daily, and we have several levels of backups using a combination of on-site using a virtual machine as well as in the cloud.+Regarding our recent cybersecurity efforts, we have been forced to clamp down on the outward facing computers. This has had no affect on operations (so far). We are looking at using Bit Defender, an enterprise-level service to lock down servers and prevent viruses. If anyone has an experience with using Bit Defender, please let Jamey know. Muk asked how frequently the site servers are backed up, noting that it was thanks to the daily backups that Gemini was able to recover from their cyberattack as quickly as they did. Jamey replied that our machines are backed up daily, and we have several levels of backups using a combination of on-site virtual machines and a cloud-based backup.
  
 ---- ----
Line 73: Line 73:
 === Feedback request re: high cadence imaging ===  === Feedback request re: high cadence imaging === 
  
-Muk - used Agile regularly +Nancy had sent the Users Committee members an email on 9/28/23 with several questions to discuss with their departmental users, particularly those who used Agile and/or use ARCTIC for high cadence imaging. **Feedback and inputs are requested by October 18:** 
-have to use ARCTIC now to see how it works - larger FOV will help, more sensitive so shorter exposure -  + 
-is ARCTIC GPS sync'ed - no+  * what is your desired time resolution for imaging? 
 +  * how bright are your typical observing targets? 
 +  * what is your desired imaging field of view? (ARCTIC max is ~ 7.8’, Agile was 2.2’) 
 +  * do you anticipate your needs for high cadence imaging to change or increase in light of upcoming discoveries (e.g. with LSST)? 
 + 
 +Muk reported that he regularly used Agile and will have to see how ARCTIC works for him to determine whether it will meet his scientific needs. The larger FOV of ARCTIC will help, and the detector is more sensitive so he could go to shorter exposures. He asked if ARCTIC's timing is sync'ed to a GPS; the answer is no and it would not be straightforward to implement that. So the absolute timing for ARCTIC will not be what it was with Agile.
  
 ---- ----
Line 81: Line 86:
 === Slides Request for ARC BoG Meeting ===  === Slides Request for ARC BoG Meeting === 
  
-Muk - used Agile regularly +Nancy issued her annual request for science highlights (at least one from every ARC member institution and leasing partner!) for the ARC Board Meeting on November 4. Any file format is fine, but please make sure that each slide contains: researcher’s name and institution, a few bullets describing the science result and instrument used, and a graphic to complement the text. Users can send Nancy the slide directly or (preferably) UC reps can collect them and send them to her in a single packet. **The deadline for submitting slides is Monday October 23.** These are important for conveying to the Board members that their institution's investment in ARC and the 3.5m is worthwhile!
-have to use ARCTIC now to see how it works - larger FOV will help, more sensitive so shorter exposure -  +
-is ARCTIC GPS sync'ed - no+
  
 ---- ----
- 
  
 === Q4 3.5m scheduling === === Q4 3.5m scheduling ===
  
-in progress - have moderate amt of unassigned time (OPEN or DD02) - none until Nov 1, lot of it is bright - open likely bright/short, monitoring programs using different instruments, lots of instrument changes, observers may not know that they were awarded 6 HN as 8 shared lots - users should check the schedule!+We have a moderate amount of unassigned time (OPEN or DD02) starting in early November. A lot of it is bright and or shorter than a full half-night. Users are reminded to check the schedule for their assigned time; if a program is allocated half-nights that are truncated due to sharing with a short monitoring program, they may have been scheduled for more half nights than they were expecting.
  
 ---- ----
Line 96: Line 98:
 === Q4 0.5m scheduling === === Q4 0.5m scheduling ===
  
-schedule almost ready to be published - 4 different programs, 7 position wheel available+The schedule is almost ready to be published, with four different programs that requested time. As a reminder, the 7-position filter wheel is now available.
  
 ---- ----
Line 102: Line 104:
 === Future Meetings === === Future Meetings ===
  
-- AAS - Jan AAS +APO will once again have a booth at the January AAS meeting; in 2024 the meeting will be in New Orleans. We hope that many 3.5m users will present results enabled by observations made at APO, and that we can get some help staffing the booth. More details to come next month. 
-- 30th anniversary - Joanne - Dean came with her and it was all very successful, Misty - at both of last 2 celebrations - fun to do more of a party (like 2014) - if can fenagle admins to come that's a good opportunity - Derek agrees - JHU wouldn't attend (not administrator) - Chip - WIRO bash at 30th anniversary - good event from feel good celebration, helped administrators to see facility . Russet - videos are out of date - + 
 +Nancy reminded everyone that 2024 will mark the 30th anniversary of operations at APO and the 3.5m. In 2014 there was a big bash at the Visitors Center, which included science talks and many of the founding members coming back to visit. In 2019 we held a strategic planning meeting, in conjunction with a 25th anniversary celebration dinner. //Do we want to do anything for the 30th anniversary?// The ARC Board Chair requested that Nancy poll the Users Committee. Joanne reported that her Dean came with her for the 20th anniversary event and it was very successful, enabling her to become a leasing partner. Misty attended both of last two celebrations and thought it would be fun to do more of a party (like in 2014). It would be a great opportunity to show off the facilities, particularly if we could get administrators from the ARC institutions to attend. Derek agreed. Kevin didn't think that JHU would attend such an event. Chip shared UWY's experience of the WIRO 30th anniversary celebration; he thought it was a good celebration event and it helped administrators to see facility. He made a video that he continues to show as needed; Russet thought this would be a good opportunity to update our out-of-date videos.
  
 ---- ----
Line 109: Line 112:
 === ACTION ITEMS ===  === ACTION ITEMS === 
  
-Open action items from previous meetings: +Open action items from previous meetings: None
- +
-  * Nancy: track down missing ARCTIC data reduction scripts for wiki. -> CLOSED.+
  
 New action items from this meeting: New action items from this meeting:
-  * UC reps: please notify your department members that if they wish to join our mailing lists they should submit their requests from their institutional email accounts, or if they wish to use personal email addresses, they should notify us so that their requests are not rejected.+  * UC reps: solicit input from users re: high time resolution imaging needs; feedback due to Nancy on 10/18 
 +  * UC reps: collect science highlight slides from users; send to Nancy by 10/23
  
  
Line 121: Line 123:
 === All Other Business === === All Other Business ===
  
-Muk - possible to get GPS for ARCTIC - RM - have to reprogram ICC, Bill -  not easy+None.
  
 ---- ----
uc/uc20231003_october_3_2023.1697230477.txt.gz · Last modified: 2023/10/13 20:54 by nchanove

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki