Reports until 19:48, Monday 08 October 2018
H1 GRD
sheila.dwyer@LIGO.ORG - posted 19:48, Monday 08 October 2018 (44421)
guardian not running down after a lockloss when power request was 5W

Craig, Sheila

We were testing a change to the increase_power state, and set the requested power in lsc_params to 5W.  We normally manually go to the ADJUST_POWER state if we want to manually change the requested power, but this time we accidentally adjusted the power from LASER_PWR while ISC_LOCK was still in increase power. We lost lock, but the ISC_LOCK guardian went into error and didn't run down, saturating a variety of suspensions until we manually turned things off. This is a risky situation for the interferometer.

It seems like the cause of the problem was that we set the requested power to 5W, which the log of ISC_LOCK says was an invalid request for LASER_PWR, although it is a state.  I don't understand why this happened.

Update:

The INCREASE_POWER state in ISC_LOCK had a couple of errors (we were relying on nodes.arrived when we really wanted node.done and node.arrived and a mistake with the counter) that caused it to continuously make same sate redirect requests of LASER_PWR.  I edited the guardian in order to avoid this in the future.  I don't know if this will fix the problem we had, but we've had strange behavior in the past with same state redirects 43599

Non-image files attached to this report