Lockloss @ 03:22 UTC - link to lockloss tool
I originally thought this lockloss was from a M5.4 EQ from Chile that was predicted to hit at this time, but now that the USGS site has updated and looking at how sudden and hard-hitting the lockloss was, I now suspect this was from a M3.2 EQ from Desert Aire, WA, a mere 20 miles northwest of the site.
Since this quake was so close, ground motion calmed down quickly and I've started the relocking process.
Lockloss @ 00:18 UTC - link to lockloss tool
PI mode 24 rung up 90 minutes into the lock stretch and caused this lockloss. I tried manually damping after seeing Guardian be unsuccessful, but I also wasn't able to find a phase which brought this mode down at all before losing lock (I did not get to trying different gains).
H1 back to observing at 01:18 UTC. Fully automated relock.
TITLE: 09/22 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 136Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: The range has peaked at 164 Mpc in the first 2 locks of the day. 2 locklosses this shift, the range isn't so great this current lock, high freq SQZing looks bad.
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
23:58 | SAF | H1 | LVEA | YES | LVEA is laser HAZARD | 18:24 |
19:36 | PE | Robert | EndY | N | CEX PEM investigations | 23:08 |
TITLE: 09/22 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 15mph Gusts, 9mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.13 μm/s
QUICK SUMMARY: H1 just got back to observing about 15 minutes ago. High frequency noise looks particularly bad this lock, so once H1 is thermalized I may try some SQZ alignment to improve it.
20:53 UTC lockloss
There were HAM3 CPS glitches on verbal before the LL, and PRM was the first saturating suspension from the LL tool.
Another CPS glitch tripped the HAM3 ISI
All of the glitches are on the H2 & V2 sensor, which I believe have their own rack, corner 1 & 3 are on the other rack. I've asked Ryan to go and power cycle the CPS electronics are the rack in the CER. We'll see if that fixes the issue.
I called Jim who advised I go to the CER and power cycle the HAM3 ISI interace chassic CPS power as we were seeing the glitches in H2 and V2, I did this which has fixed the issue (for now at least).
22:46 UTC Observing
Lockloss at 15:22 UTC
16:35 UTC Observing
Sun Sep 22 08:12:37 2024 INFO: Fill completed in 12min 32secs
TITLE: 09/22 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 8mph Gusts, 5mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.14 μm/s
QUICK SUMMARY:
TITLE: 09/22 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Quiet shift after relocking following a PI-caused lockloss.
H1 has now been locked and observing for 5 hours.
LOG:
No log for this shift.
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 |
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.
TITLE: 09/21 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 13mph Gusts, 7mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.16 μm/s
QUICK SUMMARY: H1 just lost lock from PI mode 24 ringing up after being locked for 90 minutes. Starting lock acquisition.
H1 back to observing at 04:45 UTC. Fully automated relock after waiting for ground motion to calm.