| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
uc:uc20250204_february_4_2025 [2025/02/04 18:25]
nchanove |
uc:uc20250204_february_4_2025 [2025/02/04 18:50] (current)
nchanove |
| === Additional site, telescope and instrument discussion === | === Additional site, telescope and instrument discussion === |
| |
| The site had few power related issues recently. There was fuel contamination in the backup generator; a wiring issue in the generator also corrected. A full servicing of the main generator is complete and it is ready to be put into service for full back-up utility power (as of this morning). There was an issue with the computer room UPS that led to servicing in January; the batteries weren't fully charging but it is fixed now. We are investigating whether we can get that unit back on a service contract so if components fail in the future it's not as expensive for us to repair. | The site had a few power related issues recently. There was fuel contamination in the backup generator; a wiring issue in the generator was also repaired. A full servicing of the main generator is complete and it is ready to be put into service for full back-up utility power (as of this morning). There was an issue with the computer room UPS that led to servicing in January; the batteries weren't fully charging but it is fixed now. We are investigating whether we can get that unit back on a service contract so if components fail in the future it's not as expensive for us to repair. |
| |
| During a recent routine, scheduled power outage, after coming back to main utility power a breaker that controls the building enclosure controller amplifier failed. We didn't have a spare so the telescope was down for a night because we couldn't move the enclosure building. It was brought back up the next day (the technical staff worked out a temporary solution until the spare was received and put into place). Hopefully we will not be switching back and forth between generator and utility for testing/burning off fuel too much more. | During a recent routine, scheduled power outage, after coming back to main utility power a breaker that controls the building enclosure controller amplifier failed. We didn't have a spare so the telescope was down for a night because we couldn't move the enclosure building. It was brought back up the next day (the technical staff worked out a temporary solution until the spare was received and put into place). Hopefully we will not be switching back and forth between generator and utility power for testing/burning off fuel too much more. |
| |
| Both the 3.5m and 0.5m telescopes areworking as expected. The cold weather in January led to some issues with some of the instruments (primarily with shutters). The KOSMOS slit viewer shutter was sticky when temperatures fell below its temperature rating. We replaced it with a spare and are looking to get more spares on hand. The disperser and mask wheels also were struggling in cold weather. The ARCTIC diffuser mechanism is also something that we're hoping to schedule a repair for during next engineering time. Agile is back and we're working with the repair shop on a path forward (reinstall as is or have them try to repair it further; the programmable gain still not functioning). The rest of the instruments have all been behaving nominally. TripleSpec had an issue with the detector reading zeros but a reset of camera controller did the trick. | Both the 3.5m and 0.5m telescopes are working as expected. The cold weather in January led to some issues with some of the instruments (primarily with shutters). The KOSMOS slit viewer shutter was sticky when temperatures fell below its temperature rating. We replaced it with a spare and are looking to get more spares on hand. The disperser and mask wheels also were struggling in cold weather. The ARCTIC diffuser mechanism is also something that we're hoping to schedule a repair for during next engineering time. Agile is back and we're working with the repair shop on a path forward (reinstall as is or have them try to repair it further; the programmable gain still not functioning). The rest of the instruments have all been behaving nominally. TripleSpec had an issue with the detector reading zeros but a reset of the camera controller did the trick. |
| |
| Misty: long-term solution to avoiding cold issues? IN light of extreme weather and future. BK: When install instrumentation or spec new things, try to spec operating temp to -20 C. If we get down to -15C that's our de facto closure limit but there are some parts that we can't get manufactures to give us an extended cold temperature range. Hard to retrofit or find components if they don't have them. The -15C limit is due to telescope itself having issues. Not something that we've spent a lot of additional time to find solutions for more extreme conditions during winter. | Misty asked if we have discussed any long-term solutions to avoiding these instrument cold issues in light of the extreme weather we have been (and likely will continue to be) experiencing. Bill answered that when we install instrumentation or spec new instruments, we try to spec them for an operating temperature of -20C. If we get down to -15C that's our //de facto// closure limit (because that's where the telescope itself starts having issues). However, there are some parts for which we cannot get manufacturers to give us an extended cold temperature range. But this is not something that we've spent a lot of additional time trying to find other solutions for. |
| |
| ---- | ---- |
| === 2025 Q1 3.5m scheduling === | === 2025 Q1 3.5m scheduling === |
| |
| We have some unassigned time in Q1 (mostly B halves). Feb 08, 17, 18 - have some requests already but if there are any urgent requests or high priority (e.g. students) otherwise will allocate the time to ppl who already made requests. More time in March - one fraction A half but the rest is B. | We have some unassigned time in Q1 (mostly B halves) - most urgently Feb 08B, but there are a few others in February and March as well. We have received some requests for this time already but if there are any urgent requests or high priority (e.g. students) programs please let us know ASAP, otherwise we will allocate time (at least the slots in the first few weeks of February) to the people who already made requests. 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). |
| | |
| 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). | |
| |
| ---- | ---- |
| === 2025 Q2 3.5m scheduling === | === 2025 Q2 3.5m scheduling === |
| |
| Allocations sent yesterday - proposals due 2/24. | The allocations were sent to all institutions yesterday; proposals are due on February 24. A few items to note: (1) any users who request to use Agile in Q2 should specify a backup instrument, (2) DIS is offered in shared risk mode only and has not been serviced for several quarters, (3) the allocation emails also contain a breakdown of the split between A halves and B halves. Institutions should try to avoid requesting all of their time in A's (or B's) since we will not be able to accommodate everyone's requests if that happens. |
| |
| ---- | ---- |
| === 2025 Q1 0.5 scheduling === | === 2025 Q1 0.5 scheduling === |
| |
| 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. | The 2025 Q1 ARCSAT scheduled is posted. There is available time that people can request in the next week and a half, and then again in the last week of March. 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. |
| |
| next week and half and last week of March are available. | |
| |
| ---- | ---- |
| === IT Security === | === IT Security === |
| |
| No new announcements. Trying to resolve issues re; TUI logins that cropped up over the weekend, Trying to understand - had an issue - doesn't look like it was an external attack attempt. likely an internal failed script that spun out of control, | No new announcements. We are trying to resolve some recent issues related to TUI logins; lots of work is going on behind the scenes but there is no news or action items for the Users Committee this month. |
| |
| ---- | ---- |
| === Status of new instrument initiatives === | === Status of new instrument initiatives === |
| |
| 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. | We still have heard no news from NSF regarding the pre-proposal that was submitted for ASPEN. The UW Telescope Engineering Group has been working on their response to the Ocotillo Critical Design Review report; they expect to submit it to Nancy next week. There have been some preliminary discussions about the possibility of replacing Agile with a more modern and capable high-speed imaging camera. This is in the very early stages of discussion but if there are users who would want to take advantage of this capability they should contact Nancy so we can make sure that we can advocate for those science cases. |
| |
| ---- | ---- |
| === DIS Decommissioning Plans === | === DIS Decommissioning Plans === |
| |
| 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. | Nancy has drafted an instrument decommissioning document that she and Bill are working on. The hope is to have this general document finalized before the end of the month so that it can be applied to DIS. The first order of business will be to issue a formal notification to all stakeholders about our plans to decommission DIS. |
| |
| ---- | ---- |
| |
| Open action items from previous meetings: | 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 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: get Mt. Cuba Foundation proposal for new KOSMOS grisms submitted. STATUS: OPEN. The proposal is done; Nancy needs to distribute it to the users who requested the grisms to ensure that their science cases are adequately described. She plans to submit it 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. | * 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 Q1 schedule 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. |
| === All Other Business === | === All Other Business === |
| |
| Misty strategic planning meeting - discussion that reserves had enough for 1 instrument. | There was a question about the development of Ocotillo (and other instruments) and whether it is contingent on getting federal funds (e.g. from NSF). This led to the question of how reliant APO is (more broadly) on federal funds. These items were discussed in light of the recent chaos resulting from the suspension of federal grant payments until they can be confirmed to be compliant with the recent Executive Orders. |
| possible to get a sense for ow insulated APO is from federal chair | |
| |
| ---- | ---- |
| === Next meeting === | === Next meeting === |
| |
| The next meeting will be on February 4, 2025 at 10:30 MST. | The next meeting will be on March 4, 2025 at 10:30 MST. |
| |
| ---- | ---- |
| |
