D. Barker, S. Dwyer, J. Kissel, E. Merilh, C. Vorvick

While resuming alignment of the IMC this morning, we were confused and surprised to see the IMC mirrors and PZTs being driven around without our doing. The problem was that the MC WFS servos had triggered at around 19:10 UTC after we opened the light pipe and began shooting light down to MC2 TRANS, the SUM of which serves as the trigger PD**. Because the P and Y path from these servos' output -- all the way to each MC1, MC2, and MC3 mirrors -- is, by default, always on, this non-sense drive was driving around the suspensions and PZTs. 

Because we don't want anything but humans driving the suspensions for the foreseeable future (until chamber doors start to go back on) I've taken the following disabling measures:
- Turned of the input to the MC1, MC2, and MC3 top mass (M1 LOCK) P and Y filter banks, 
    - Accepted this change in each suspensions safe.snap SDF file.
- Turned up the trigger on/off thresholds for the MC WFS (H1:IMC-IMC_TRIGGER_THRESH_ON / H1:IMC-IMC_TRIGGER_THRESH_OFF) from 40 / 20 to 5000 / 500.
    - Accepted into the safe.snap file of h1ascimc 
- Un-managed MC2 from the IMC_LOCK guardian.
- Moved the IMC_LOCK guardian to PAUSED so that it's no longer running (just a precaution, really, the MC WFS are all triggered via front-end logic).
- Cleared the history on all MC WFS servos.
- Restored all alignment offsets (PSL PZTs, MC1, MC2, and MC3) to there values reported at the close of business yesterday (see LHO aLOG 39299)

An as-of-yet unsolved mystery is why we're getting so much more sum counts on the MC2 trans (during yesterday's flashing we hit 2 or 3 [ct] max, now we've hit 25 - 30 [ct]).

**The trigger is not just MC TRANS SUM, but H1:IMC-MC2_TRANS_SUM_OUT / H1:IMC-PWR_IN_NORM_MON. The demoninator, H1:IMC-PWR_IN_NORM_MON, is set to 0.1. So with a sum of 25-30 [ct], the triggered value becomes 250-300, and surpasses the (former) threshold of 40 [ct].