MIF (General)takaaki.yokozawa - 8:46 Friday 03 October 2025 (35211)
Print this reportLock loss investigation Oct 1st night timeI performed the several investigation for the lock losses at the night time of the 1st October (early morning 2nd October).
IFO state : INCREASEING_LAS_POWER decorator : @check_io IMC-CAV_IS_RESONATING ==1
@check_prmi3f LSC-POP_PDA2_RF90_I_NORM_MON > 0.1
@check_ir_xy K1:LSC-TR_IR{X,Y}_NORM_OUT_DQ > 0.2
- 1443370013 1st Oct 16:06:35 UTC No significant ground motion LSC_LOCK guardian message : 2025-10-02_01:06:36.029711 LSC_LOCK [INCREASING_LAS_POWER.run] USERMSG 0: IMC seems to be unlocked Fig.1. showed the several PMC-IMC related channels with several guardian state. As you can see, the PMC and IMC trans power dropped. IMC-CAV_IS_RESONATING became 0 and LSC-LOCK state 0 So, my conclusion is PMC (or IMC) locked loss.
- 1443380309 1st Oct 18:58:11 UTC No significant ground motion LSC_LOCK guardian message : 2025-10-02_03:58:11.643105 LSC_LOCK [INCREASING_LAS_POWER.run] USERMSG 0: IMC seems to be unlocked Fig.2. showed the several PMC-IMC related channels with several guardian state. As you can see, the LSC_LOCK guardian became 0 with IMC guardian became 0, but no significant decreasing of IR trans, pop90, and IMC trans. After LSC_LOCK guardian became 0, both IMC and PMC trans power became 0, so this lock loss reason is NOT the PMC locked loss. So, we need to investigate why IMC guardian became 0
- 1443384011 1st Oct 19:59:53 UTC No significant ground motion LSC_LOCK guardian message : 2025-10-02_04:59:53.527441 LSC_LOCK [INCREASING_LAS_POWER.run] USERMSG 0: IMC seems to be unlocked Fig.3. showed the several PMC-IMC related channels with several guardian state. Similar situation of lock loss1, so I guess PMC or IMC locked loss
- 1443389797 1st Oct 21:36:19 UTC No significant ground motion LSC_LOCK guardian message : 2025-10-02_06:36:20.024613 LSC_LOCK [INCREASING_LAS_POWER.run] USERMSG 0: IMC seems to be unlocked Similar situation with lock loss 2, but different point is PMC guardian state became 0 at the same timing with LSC_LOCK guardian. We need to investigate more