camilla.compton@LIGO.ORG - posted 18:14, Thursday 28 November 2019 - last comment - 18:33, Thursday 28 November 2019(53552)
H1 Lockloss
Following on from Jim's alog 53549:
-
22:00 Unlocked
-
00:10 WFS were not catching the ALS Y, tried resetting ETMY and ITMY to before lockloss and got no flashes at all.
-
00:32 Tried initial alignment but it couldn't lock the green arms, took it to DOWN to manually adjust with ETMY and ITMY.
-
Finally got ALS Y flashes to 0.8 and the WFS grabbed
-
-
00:36 INITIAL_ALIGN stuck at OFFLOADING_GRREN_WFS even though signals were steady.
-
Tried DOWN, INIT but INITIAL_ALIGN stuck at OFFLOADING_GRREN_WFS again
-
Manually took ALS_X/YARM to UNLOCKED as this is what INITIAL_ALIGN was waiting for. (Did they ever get offloaded?!)
-
-
00:47 ALIGN_IFO stayed in PRC_ALIGN for 10 whole minutes waiting for PRC1 PIT and YAW to converge to thresh 50. I don't think they did, it just timed out and moved on. A similar thing happened yesterday for Jeff K and I alog 53541 @ 05:21.
-
01:03 Inital Alignment compleate.
-
01:24 Lockloss as CARM_OFFSET_REDUCTION
-
01:30 ALS YARM has fault with message "PHD", "Green input alignment off"
-
This is the same as happened for Jim ( alog 53549) so I took ISC_LOCK to DOWN and changed H1:ALS-Y_PZT2_TRIG_THRESH_ON from 0.5 to 0.3 as Keita had done on the phone with Jim. Is this fixing the Problem? I changed it with caput and it's stayed at 0.3 but with Keita it seemed to go back to 0.5 quickly, maybe I should have changed it back too.
-
Now ALS YARM locking fine with small ETMY tweaks.
-
Currently at INCREASE_POWER with my fingers crossed.
Comments related to this report
- 02:25 NLN. Only SDF I accepted was H1:ALS-Y_PZT2_TRIG_THRESH_ON that I changed (photo attached). I don't understand it well enough to know what it effects it has.
- 02:27 OBSERVING!
Images attached to this comment
