| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
uc:uc20250204_february_4_2025 [2025/02/04 18:46]
nchanove |
uc:uc20250204_february_4_2025 [2025/02/04 18:50] (current)
nchanove |
| 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. | 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 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. | 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 Q2 3.5m scheduling === | === 2025 Q2 3.5m scheduling === |
| |
| The allocations were sent to all institutions yesterday; proposals due on February 24. A few items to note: (a) any users who request to use Agile in Q2 should specify a backup instrument, (b) DIS is offered in shared risk mode only and has not been serviced for several quarters, (c) 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. | 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. |
| |
| ---- | ---- |
