Differences

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

--- uc:uc20250107_january_7_2025 [2025/01/24 19:44] – nchanove
+++ uc:uc20250107_january_7_2025 [2025/01/24 20:04] (current) – nchanove
@@ Line 63: / Line 63: @@
 === 2025 Q1 3.5m scheduling ===
-We have some unassigned time in Q1. Most are B halves as well as in Feb (8 is next one). Time is listed as OPEN. Users should look at the schedule and follow the usual channels for requesting this time (i.e. email Russet, Amanda, Ben, Nancy and their institutional scheduler when submitting requests, and provide a proposal cover page if you don't already have a program scheduled for the current quarter). Users can request time listed as OPEN or DD.
+We have some unassigned time in Q1 (mostly B halves). This time is listed as OPEN on the Q1 schedule. Users should look at the schedule and follow the usual channels for requesting this time (i.e. email Russet, Amanda, Ben, Nancy and their institutional scheduler when submitting requests, and provide a proposal cover page if you don't already have a program scheduled for the current quarter).
 ----
@@ Line 69: / Line 69: @@
 === 2025 Q1 0.5 scheduling ===
-The 2025 Q1 ARCSAT scheduled is posted. Only had 2 requests this quarter. Continuing to struggle with frequent failure in communication with camera ("support library error") - camera is getting old. Temporary fix is fairly quick so if observers can keep an eye on it and report errors it can be recovered pretty quickly. Early March - onsite class and other stuff going on so not available for ARCSAT.
+The 2025 Q1 ARCSAT scheduled is posted. We only had 2 requests this quarter (note added in proof: we received a third request, so there are now 3 programs scheduled to use ARCSAT in Q1). We are continuing to struggle with frequent failures in communication with the camera (which manifests as a "support library error"); FlareCam is getting old. The temporary fix is fairly quick so if observers can keep an eye on it and report errors it can be recovered pretty quickly. In early March we will have an onsite class and other stuff going on so ARCSAT is not available during weeks when the schedule is marked BUSY.
 ----
@@ Line 75: / Line 75: @@
 === Website Modernization Effort ===
-Test tomorrow on converting site to new servers - just heard from Shane that may be rescheduled due to illness.
+There is a plan to run a test tomorrow for converting the site to new servers (but this may be postponed due to illness).
 ----
@@ Line 81: / Line 81: @@
 === IT Security ===
-Still researching applications to improve password handling but it's coming.
+The IT team at APO is still researching applications to improve password handling; all we know right now is that the switching of the TUI password is coming.
 ----
@@ Line 88: / Line 88: @@
 === Status of new instrument initiatives ===
-No news on ASPEN pre-proposal from NSF. Hope to hear soon.
+We have heard no news from NSF regarding the pre-proposal that was submitted for ASPEN; we hope to hear soon. Sarah reported that since having received the Ocotillo CDR report on December 2 her team has been evaluating the comments and preparing a response. They also applied for some funding and are waiting to hear back. It is clear that the instrument will come together in a phased approach, bringing the three channels online one at a time. They will start with the IFU and follow up with MOS component, which is more costly and mechanically complicated. The hope is that this would enable supported data reduction development along the way and troubleshooting as we go. It also spaces out the cost, which reduces impact on the overall observatory budget. Their goal is to have their response report back to the CDR review panel by the end of the month.
-Ocotillo CDR - evaluate subsequent report. Also applying for funding. Will come together in phased approach, bring channels on line one at a time. Start with IFU, follow up with MOS component - more costly and mechanically complicated. Hoping that this would enable supported data reduction development, troubleshooting as we go. Spaces out the cost, reduces impact on budget. End of month have report back to CDR review panel.
 ----
@@ Line 95: / Line 94: @@
 === DIS Decommissioning Plans ===
-In the works.
+Nancy is working on developing a document that lays out the decommissioning plan for DIS. The instrument has not been serviced and will only be available in Q1 (and Q2) in a shared risk mode.
 ----
@@ Line 103: / Line 102: @@
 Open action items from previous meetings:
-  * Nancy: get ROM costs for new KOSMOS grisms. Sarah reported that she has a finalized quote from one vendor. The grism design turns out to be a little complicated, but also, costs have gone up, so these are more expensive than we expected (ballpark $20k apiece). Therefore, we need to explore potential funding sources. We have reached an impasse in terms of prioritizing the desired grism; Nancy will amass all previous emails with grism requests and send to UC reps to query users about whether there is broad interest in a particular grism. This could help identify funding sources, either individually or collaboratively. STATUS: OPEN.
+  * Nancy: get ROM costs for new KOSMOS grisms. Sarah reported that she has a finalized quote from one vendor. The grism design turns out to be a little complicated, but also, costs have gone up, so these are more expensive than we expected (ballpark $20k apiece). Therefore, we need to explore potential funding sources. We have reached an impasse in terms of prioritizing the desired grism; Nancy will amass all previous emails with grism requests and send to UC reps to query users about whether there is broad interest in a particular grism. This could help identify funding sources, either individually or collaboratively. STATUS: OPEN. Nancy has started a proposal to the Mt. Cuba Foundation for several grisms and hopes to have it submitted before the next Users Committee meeting.
   * Nancy: Ensure that a short description of the impact of satellites be posted on the APO website somewhere and updated every 6 months or so. Nancy received examples of this issue from Anne Verbiscer and will get something added to the current (and new) web site. STATUS: OPEN.
-  * UC reps: remind your users to review the Q4 and Q1 schedules and request OPEN/DD time if they can make a good case for it. STATUS: OPEN.
+  * UC reps: remind your users to review the Q1 schedule and request OPEN/DD time if they can make a good case for it. STATUS: OPEN.
-  * UC reps: remind your users that they can propose to use Agile in Q1 2025 (but must include a backup instrument). STATUS: CLOSED.
 Open action items from this meeting:
-  * UC reps: poll your Agile users concerning whether or not they adjust the camera gain setting - there are 3 selectable gains - software electability is what has changed and can't get it to work. From last feedback with repair facility that can still be adjusted manually. That IS working. If they are unable to make further progress on software changes we will get camera back and gain can be sleeted at beginning of run by observing specialist. Will likely have to remeasure those gains because the main readout board was changed out during previous camera repair. Previous choices were ~ 1, 2, 4 e/DN.
+  * None.
-  * UC reps: alert your users to the fact that plans are being formulated for decommissioning DIS (see below).
 ----
@@ Line 118: / Line 114: @@
 === All Other Business ===
-xxx
+None
 ----