Displaying report 1-1 of 1.
Reports until 02:40, Saturday 16 November 2019
H1 ISC
jim.warner@LIGO.ORG - posted 02:40, Saturday 16 November 2019 - last comment - 09:41, Saturday 16 November 2019(53289)
DRMI locking being hindered by bogus IMC guardian message?

Still trying to get locked after Niko left, but being stopped by some weird issues. First was an OM1 trip at during I think DRMI asc offload, IFO stayed locked for a bit while I tried to figure out where to clear histories because all of the OMs were railed.

After that, I couldn't move past DRMI at all. The buildups were gradually degrading through several attempts to get DRMI, and each time ISC_LOCK would get stuck after DRMI or PRMI initial acquisition, then refuse to move on simply reporting "IMC_LOCK has notification". When I looked at IMC_LOCK, it didn't seem to have any such notification.

After multiple rounds of that, I'm trying to run initial alignment, but that is starting to look equally fruitless. The input alignment state seems to be hanging, saying ALIGN_IFO has notification. But ALIGN_IFO seems to be waiting for the input to a DC YAW loop to come on. This has continued through a number of steps in initial alignment, and the only way I've been able to move on is by manually selecting the the next offload state. This is probably all wrong. 

Initial alignment is "done", so back to locking. With an incoming earthquake. Oy.

Comments related to this report
jim.warner@LIGO.ORG - 04:07, Saturday 16 November 2019 (53290)

ISC_LOCK continues to move on from DRMI acquisition. The only clue I have are some alogs ending with Jeff's comment here, some related alogs it points to and FRS 5109. It's called alternately a red herring and occasional issue, but other than some wfs system that doesn't seem to be implemented, I don't see a solution. Seems like the IMC WFS need to be better centered, but I can't figure out how. Can't proceed past DRMI and can't seem to find a solution. 

sheila.dwyer@LIGO.ORG - 09:41, Saturday 16 November 2019 (53294)

The IMC WFS message is a red herring, the gaurdian is just giving that as a warning occasionally that we are off center, but it doesn't wait for the IMC WFS.  It looks like in a couple of the cases, ISC_LOCK was waiting in ACQUIRE_DRMI_1F for the DRMI guardian, ISC_DRMI was stuck in the DC centering state.  This is trying to center the AS + REFL WFS before turning on the DRMI ASC, which it couldn't do because the outputs of those filters were off.  With those off center the DRMI ASC won't work, which would cause locklosses if we moved on to DRMI_ASC.  So the guardian was doing the right thing, the problem was that the outputs were off.  

Displaying report 1-1 of 1.