Displaying report 1-1 of 1.
Reports until 17:33, Tuesday 03 December 2019
H1 GRD (OpsInfo)
thomas.shaffer@LIGO.ORG - posted 17:33, Tuesday 03 December 2019 - last comment - 06:26, Wednesday 04 December 2019(53667)
Green arm locking automation Round 2

First round last week can be seen in alog53499

Today I tried the Increase_Flashes state on the Y arm. I pushed it out a few urads in both pitch and yaw until we were only getting flashes to around 0.3, and then waited to see if the state could recover an alignment that was good enough for the WFS to catch it. After it had adjusted both P & Y, it was able to get to an alignment that was giving flashes >0.9. This is the threshold set for this arm, so once it found flashes that were this high, it stopped trying to find a better alignment. I changed it so ISC_LOCK will ask it to run a second time if it cannot lock for some time after the first try. For this case, a second try was quickly helpful.

I didn't have time to add the TMS into the code. This is for anther time.

Operators: The ops intervention sheet was been temporarily updated, asking to allow this code to try for 2 attempts. If there are any problems, you can maneuver around this state and align by hand, or give me a call.

Comments related to this report
patrick.thomas@LIGO.ORG - 23:46, Tuesday 03 December 2019 (53671)
Is this supposed to run automatically at LOCKING_ARMS_GREEN? I had to manually request it.
thomas.shaffer@LIGO.ORG - 06:26, Wednesday 04 December 2019 (53675)

After a waiting period it will run automatically. I think its 5min? Perhaps too long, but I was keeping consistent with the intervention sheet.

Displaying report 1-1 of 1.