gabriele.vajente@LIGO.ORG - posted 07:49, Thursday 18 October 2018 - last comment - 16:13, Thursday 18 October 2018(44650)
CHECK_MICH_FRINGES > PRMI_LOCKED fails
Today I requested twice the state CHECK_MICH_FRINGES, and then requested PRMI_LOCKED. The guardian went straight to the end of PRMI_LOCKED, reporting the state to be concluded, even if PRMI was NOT locked.
Comments related to this report
jenne.driggers@LIGO.ORG - 16:13, Thursday 18 October 2018 (44664)
This is a result of my adding locking ability to the CHECK_MICH_FRINGES state. To get the MICH length to lock, I had to force the MICH LSC trigger. But, CHECK_MICH_FRINGES to PRMI_LOCKED doesn't force the DRMI guardian to go through PREP_DRMI, so the threshold wasn't getting reset for PRMI acquisition. I have added to the PRMI and DRMI guardian states resetting the MICH LSC trigger, so that guardian (which just looks at the triggers to decide if PRMI is locked) realizes that PRMI isn't actually locked yet and will go through the prep states that it needs to do.
This is a result of my adding locking ability to the CHECK_MICH_FRINGES state. To get the MICH length to lock, I had to force the MICH LSC trigger. But, CHECK_MICH_FRINGES to PRMI_LOCKED doesn't force the DRMI guardian to go through PREP_DRMI, so the threshold wasn't getting reset for PRMI acquisition. I have added to the PRMI and DRMI guardian states resetting the MICH LSC trigger, so that guardian (which just looks at the triggers to decide if PRMI is locked) realizes that PRMI isn't actually locked yet and will go through the prep states that it needs to do.