Reports until 01:10, Sunday 02 November 2025
H1 General
oli.patane@LIGO.ORG - posted 01:10, Sunday 02 November 2025 - last comment - 06:00, Sunday 02 November 2025(87906)
OPS OWL Intervention pt 2: please go down secondary microseism

Got called again because we can't get past OFFLOAD_DRMI_ASC due to excessively high secondary microseism. We've had three DRMI catches in the last hour, all three of which died before finishing offloading DRMI ASC. Locklosses were from TRANSITION_DRMI_TO_3F, TURN_ON_BS_STAGE2, and DRMI_LOCKED_CHECK_ASC. It definitely looks like the issue is the high secondary microseism. The secondary microseism isn't as bad as it was earlier today, but it's still pretty high (nuc5). Looking at the secondary microseism channels in the Z direction (since that's where it's moving us the most), it looks like the level of microseism that we're seeing right now is the level that we last lost lock at (although we didn't lose lock because of the high microseism - there was some weird wiggle).

So since the secondary microseism looks to be heading downward, if this current DRMI can't catch and we lose lock, I'm going to put the detector in DOWN for now and come back in a couple hours to try again. Hopefully by then the secondary microseism will have gone down a bit further and we'll be able to lock.

Images attached to this report
Comments related to this report
oli.patane@LIGO.ORG - 03:23, Sunday 02 November 2025 (87907)

Time to try relocking again. Going to give this a couple hours to try getting past DRMI, and if it can't I'll put the detector in IDLE for the rest of the night.

oli.patane@LIGO.ORG - 06:00, Sunday 02 November 2025 (87908)

Still no luck with getting past DRMI_LOCKED_CHECK_ASC, but secondary microseism levels look to be at a similar level to what we relocked with last time, so I'll let it keep trying. It has been catching multiple times, but it can't stay locked more than a few seconds most times. The length of DRMI locks and places in the code were it loses lock are different every tme, so I don't think it's a different issue?

Going to keep letting the IFO try relocking.