TITLE: 09/21 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: We did not take the calibration measurement as LLO wasn't locked and we weren't fully thermalized either.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 23:58 | SAF | H1 | LVEA | YES | LVEA is laser HAZARD | 18:24 |
| 17:56 | PEM | Robert | Xarm | N | CEX PEM investigations/tests | 21:00 |
- 12:38 UTC lockloss - FSS oscillation tag, 31:50 hour lock! (Tagging PSL)
- ALS_Y was not locking and was stuck in GREEN arms of IA for 1.5 hours. Things went well after I adjusted ITMY in Yaw
- 16:11 UTC Observing
- 17:40 UTC EQ mode from a 5.3 from Alaska
- 19:49 UTC lockloss
- AS AIR looked very pitched after this LL, ETMX locked at like 10% lower. We couldnt get PRMI, 2x check_mich so I dropped into an IA at 20:20 which started with 30 seconds of EX saturations and EX locking at another 10% lower. The WFS were able to sure it up
- 21:30 UTC Observing
- 21:51 UTC PI 24 started to ring up and eventually saturated the DCPCs
- 22:58 UTC lockloss from PI 24
H1 back to observing at 23:59 UTC. Fully automated relock, no initial alignment needed.
The lockloss this morning at 12:38 UTC which ended a 31+ hr lock had the rarely seen FSS_OSCILLATION tag, so I started looking back at some related signals just to get a better idea of what happened. I've attached a trend which seems to show some IMC signals (mainly splitmon and IMC_F) see the first action before the lockloss, then the FSS fastmon has its first "glitch" about 140ms later. I'll admit I don't have a complete understanding of all the interactions here or what this is indicative of, but I figured it might be useful to take a look at since these FSS_OSCILLATION locklosses are quite rare.
