After the ENGAGE_WFSDC, locked loss frequently detected and lock duration ~100 s or shorter.
So, I checked the signals soon before the locked loss
Lock loss lists and guardian comment:
# 231 2026-01-19 22:57:33.437500 UTC ( 218s) [] ENGAGE_WFSDC 1452898671.4375
2026-01-19_22:57:33.516477Z LSC_LOCK [ENGAGE_WFSDC.run] USERMSG 0: IMC seems to be unlocked
# 232 2026-01-19 23:25:25.187500 UTC ( 92s) [] ENGAGE_WFSDC 1452900343.1875
2026-01-19_23:25:25.280429Z LSC_LOCK [ENGAGE_WFSDC.run] USERMSG 0: IMC seems to be unlocked
# 233 2026-01-19 23:39:56.312500 UTC ( 84s) [] ENGAGE_WFSDC 1452901214.3125
2026-01-19_23:39:56.383435Z LSC_LOCK [ENGAGE_WFSDC.run] USERMSG 0: IMC seems to be unlocked
# 234 2026-01-19 23:49:32.437500 UTC ( 12s) [] ENGAGE_WFSDC 1452901790.4375
026-01-19_23:49:32.521874Z LSC_LOCK [ENGAGE_WFSDC.run] USERMSG 0: PRMI seems to be unlocked
# 235 2026-01-20 00:09:21.937500 UTC ( 416s) [] ENGAGE_WFSDC 1452902979.9375
2026-01-20_00:09:22.018153Z LSC_LOCK [ENGAGE_WFSDC.run] USERMSG 0: IMC seems to be unlocked
# 236 2026-01-20 00:15:15.937500 UTC ( 2s) [] ENGAGE_WFSDC 1452903333.9375
026-01-20_00:15:16.027489Z LSC_LOCK [ENGAGE_WFSDC.run] USERMSG 0: IMC seems to be unlocked
Mostly, IMC or PMC locked loss made the IFO lock loss.
I checked the signal one by one and found that the
MCL controls signals
K1:IMC-DOF4_P_IN1_DQ
had several glitches near the locked loss (Fig.1.)
I checked the IMC ASC DOF4 P signal and I found the saturation of output(Fig.2.) and it happened 21 days ago.
I could not conclude it would be the locked loss reason, but
Could someone offload this PZT control?
