J. Driggers, J. Kissel I've been noticing that we've had to use this script more often because of our new global alignment position, so I want post an explicit aLOG about it (essentiall a repost of LHO aLOG 45688): To move an arm, or another collection of optics in our angular control system basis to reduce that ASC degree of freedom's error signal (because you're losing lock when you turn on any of the FULL IFO ASC in "PREP_ASC_FOR_FULL_IFO" or "ENGAGE_SOFT_LOOPS"), use the following script (from a command line terminal): /opt/rtcds/userapps/release/asc/h1/scripts/move_ARM_dev.py ${ARMDOF} ${ANGLEDOF} +/-${STEPSIZE} So the arguments are ${ARMDOF} = CH, DH, CS, DS, XH, XS, YH, YS ${ANGLEDOF} = P, Y (you *can* use "PIT" and "YAW") ${STEPSIZE} = slider units of the optics, so urads ish. with "D" differential, "C" for common, "H" for hard, "S" for soft, and if you want to only move an arm, "X" for X arm, "Y" for y-arm. An example that we used tonight to reduce the CHARD Pitch error signal: $ cd /opt/rtcds/userapps/release/asc/h1/scripts/ $ python move_ARM_dev.py CH P +0.03 You're going to want to do the step sizes in small increments (i.e. run the script many times, pausing for 10 seconds in between each run), and as always it's a guess and check as far as the direction (sign) of the step. The goal is to make the error signal go towards zero. Remember to use the "ASC Signals" ndscope template from Jenne's locking screen to quickly pull up all ASC error signals.
Which Guardian State will this be performed from after recovery from the previous lockloss due to this issue. Is it PREP_ASC_FOR_FULL_IFO?