Differences

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

--- uc:uc20230307_march_7_2023 [2023/03/07 22:51]
nchanove
+++ uc:uc20230307_march_7_2023 [2023/03/07 22:59] (current)
nchanove
@@ Line 91: / 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.
-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 ===
-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 102: / Line 103: @@
 === 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. 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 for a couple of questions and then the schedule will be published.
+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.
-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 in option for Q2, notify Russet ASAP (within the next day or so).**
+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).**
 ----
@@ Line 130: / Line 131: @@
   * 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 echelle users to participate in the tiger team charged with firming up the science requirements for a new echelle spectrograph.
+  * 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: please remind your users that they should notify us if their plans change and they will not use their ARCSAT time.
+  * 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.
 ----

apo-wiki

User Tools

Site Tools

Differences

Page Tools