This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
uc:uc20240903_september_3_2024 [2024/09/23 21:26] nchanove |
uc:uc20240903_september_3_2024 [2024/10/01 02:16] (current) nchanove |
||
---|---|---|---|
Line 17: | Line 17: | ||
* Oklahoma - nothing to report | * Oklahoma - nothing to report | ||
* Seattle - nothing to report; Joanne has been talking to Jamey about slit masks for KOSMOS | * Seattle - nothing to report; Joanne has been talking to Jamey about slit masks for KOSMOS | ||
- | * UVa - nothing to report other than a user was searching for info on ARCSAT using the new web site and reported that many of the links are broken | + | * UVa - a user was searching for info on ARCSAT using the new web site and reported that many of the links are broken |
* Washington - nothing to report | * Washington - nothing to report | ||
* Wyoming - nothing to report | * Wyoming - nothing to report | ||
Line 35: | Line 35: | ||
2) Operations | 2) Operations | ||
- | 3.5m Telescope: Telescope has returned from shutdown. | + | 3.5m Telescope: Telescope has returned from shutdown. Last night an issue occured with the tertiary tip/ |
- | 0.5m Telescope: | + | 0.5m Telescope: Telescope is working well. The FlareCam |
KOSMOS: nothing to report. | KOSMOS: nothing to report. | ||
Line 43: | Line 43: | ||
ARCTIC: was vacuum cycled over shutdown, available for use. | ARCTIC: was vacuum cycled over shutdown, available for use. | ||
- | Agile camera failure has been diagnosed to a failed TEC. | + | Agile: the camera failure has been diagnosed to a failed TEC. A purchase |
- | Echelle | + | ARCES: The echelle |
| | ||
- | DIS red camera experienced an intermittent electronics issue that is still not well understood. | + | DIS: The red camera experienced an intermittent electronics issue that is still not well understood. |
- | NICFPS was vacuum cycled over shutdown, system is cooled and back in operations. | + | NICFPS: was vacuum cycled over shutdown, |
- | TripleSpec | + | TripleSpec: Both Tcam and Tspec icc computers have had drives swapped in the raid arrays to replace failing drives. |
---- | ---- | ||
Line 57: | Line 57: | ||
=== Additional site, telescope and instrument discussion === | === Additional site, telescope and instrument discussion === | ||
- | Weather | + | The weather pattern continued to be monsoonal |
- | Tertiary - error message comes through | + | For ARCSAT the FlareCam cooling fans were replaced |
- | FlareCam cooling fans replaced, back on telescope. | + | KOSMOS is behaving as expected. |
- | KOSMOS - behaving as expected. | + | ARCTIC |
- | ARCTIC | + | |
- | Agile failure - TEC failure, working on repair now. No estimate for return date yet. | + | |
- | ARCES - problematic last month. Disk drive failure, software RAID array on 2 disks. Intermittent failure due to power supply in computer - currently desktop temp solution and then new drop-in power supply on order. IOL nominal. Haven' | + | |
- | DIS red experienced electronics issue right before shutdown. Has constant pixel value when it fails. Bill rebooted | + | The Agile failure has been diagnosed as a failure of the thermoelectric cooler (TEC), |
- | NICFPS vacuum cycled over shutdown. | + | ARCES was problematic last month. There was a disk drive failure of the software RAID array on 2 disks. We haven' |
- | Tcam and Tspec operational. | + | The DIS red channel experienced an electronics issue right before shutdown. In this failure mode it has constant pixel values. Bill rebooted it and the issue went away. Vacuum servicing of DIS is likely to happen in Q4. |
- | THANK YOU TO 3.5m STAFF FOR DOING SUCH A GREAT JOB WITH SHUTDOWN ACTIVITIES AND TRAINING! | + | NICFPS was vacuum cycled over shutdown. |
+ | For TripleSpec, both Tcam and Tspec are operational. | ||
+ | |||
+ | **Nancy expressed her sincere thanks to the 3.5m staff for doing such a great job with the summer shutdown and the training activities for the newer staff members. | ||
+ | ** | ||
---- | ---- | ||
=== 2024 Q3 3.5m scheduling === | === 2024 Q3 3.5m scheduling === | ||
- | We have one remaining unassigned half night in Q3 (Sep 14B). 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). | + | We have one remaining unassigned half night in Q3 (Sep 14B). 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 86: | Line 87: | ||
=== 2024 Q4 3.5m scheduling === | === 2024 Q4 3.5m scheduling === | ||
- | The Q4 schedule is being assembled now; it should be out early next week. October A halves are extremely oversubscribed; | + | The Q4 schedule is being assembled now; it should be out early next week. October A halves are extremely oversubscribed; |
---- | ---- | ||
Line 92: | Line 93: | ||
=== 2024 Q3 0.5 scheduling === | === 2024 Q3 0.5 scheduling === | ||
- | The Q3 ARCSAT scheduled is posted; there is no open time available. The call for Q4 proposals will be issued after the Q4 3.5m schedule is finished. | + | The Q3 ARCSAT scheduled is posted; there is no open time available. The call for Q4 proposals will be issued after the Q4 3.5m schedule is finished. |
---- | ---- | ||
Line 98: | Line 99: | ||
=== Website Modernization Effort === | === Website Modernization Effort === | ||
- | xxx | ||
- | 1) Good news: | + | Starting with the good news: All of the content that is regularly used and is relatively |
- | + | ||
- | 2) Next step: Make a development web server to stage the deployment | + | |
- | + | ||
- | 3) In particular, this development server will allow him to test how the new website will work, once the old website is taken down (especially links that go from new to old), including testing swapping the URL, and checking | + | |
- | + | ||
- | 4) The schedule of this depends | + | |
---- | ---- | ||
Line 112: | Line 106: | ||
=== Time Domain Astronomy Opportunity === | === Time Domain Astronomy Opportunity === | ||
- | Adam - 5 replies - transient science priority for decade, open new support for grants (emeritus), new theory person very interested, Has there been use for ToO science over years and how much? Adam - wondering if spectra are of science quality or intended for quick look classification, | + | Nancy collected input from the UC members |
- | + | ||
- | Kevin - 3 users (2 faculty, 1 student), enthusiastic but likely not sure how serious that is. | + | |
- | + | ||
- | Moire - no one volunteered | + | |
- | + | ||
- | OU - 2 responses - both would prefer to use higher res instrument but no one does transient science there | + | |
- | UWy - nothing | + | |
- | Aleksandr - no BYU users | + | |
- | Joanne - generally supportive (vague) | + | |
- | Derek - too low of resolution | + | |
- | Anne - got an email from Mariam Bochaz - expressed great interest in instrument and would like it for Rubin/LSST followup, happy to be involved in working group | + | |
- | + | ||
- | Nancy, Sarah, Ben and Eric Bellm recently had a discussion with Shri Kulkarni about the possibility of putting a robotic spectrograph for fast transient classification on the 3.5m. The first version of this instrument, developed for ZTF as an R ~ 100 spectrograph for supernova | + | |
- | * Bill: who would be doing the observing for this kind of project? Nancy/Eric: that's really up to us to decide, but we don't have an expectation that this would fall on the shoulders of the observing specialists. | + | |
- | * Bill: from a technical standpoint, if the instrument | + | |
- | * Adam: would users be able to propose to use the instrument for their own programs or would it be used only for transient observations? | + | |
- | * Adam: what is its primary advantage over KOSMOS given the wavelength coverage? Nancy: it has lower spectral resolution (which some but not all users would want) and the data are reduced and posted very rapidly (~ 15 minutes from data acquisition to posting online). | + | |
- | * Ben: when the Time Domain Astronomy Working Group (TDAWG) was active several years ago there was interest in the possibility of cross-institutional collaboration to use a portion of the available time for this kind of work. | + | |
- | + | ||
- | **Nancy will draft a synopsis of this discussion and send it to the Users Committee reps. The reps will then send it to their users and solicit their feedback | + | |
- | + | ||
---- | ---- | ||
Line 141: | Line 113: | ||
Open action items from previous meetings: | Open action items from previous meetings: | ||
- | * Nancy: get ROM costs for new KOSMOS grisms. Sarah reported that she is still working with few different vendors due to some weird materials issues. Apparently the KOSMOS gratings were made in an unusual way and now one or two of the glasses | + | * Nancy: get ROM costs for new KOSMOS grisms. Sarah reported that she has a finalized quote from one vendor. These are more expensive than we expected so we need to explore potential funding sources. STATUS: OPEN. |
- | * UC reps: ask your users to review the alpha version of the new web site to determine whether the content they are used to finding on the web site is still there and easy to find. All feedback should be provided through the Google sheet given above. STATUS: | + | * UC reps: ask your users to review the alpha version of the new web site to determine whether the content they are used to finding on the web site is still there and easy to find. All feedback should be provided through the Google sheet (link given in the August Users Committee meeting minutes). STATUS: |
* 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. STATUS: OPEN. Waiting for new web site deployment may not be the best approach. Nancy will get examples of this issue from Anne Verbiscer and get something added to the current web site before the next 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. STATUS: OPEN. Waiting for new web site deployment may not be the best approach. Nancy will get examples of this issue from Anne Verbiscer and get something added to the current web site before the next meeting. | ||
- | * UC reps: remind your users to review the Q3 schedule and request OPEN/DD time if they can make a good case for it. | + | * UC reps: remind your users to review the Q3 schedule and request OPEN/DD time if they can make a good case for it. Status: CLOSED. |
- | * Nancy: send UC reps a summary of the time domain discussion and request to users. | + | * Nancy: send UC reps a summary of the time domain discussion and request to users. Status: CLOSED. |
- | * UC reps: send Nancy' | + | * UC reps: send Nancy' |
Open action items from this meeting: | Open action items from this meeting: | ||
+ | |||
+ | None. | ||
---- | ---- |