J. Kissel, A. Pele (WP #5025)

We are to make the IFO's fast shutter functional within the next week, in order to prepare and protect the OMC DCPDs from the energy leaked from a FULL IFO lock lock. In its current design / implementation, this shutter is fast and loud as it closes and reopens, which sends large impulses to the optical table on which it sits (in this case H1 ISI HAM6). In order to prepare for this "toaster" being activated, I've increased the number of consecutive saturations (computer cycles above the user-predefined threshold) that are acceptable for the H1 ISI HAM6 GS13s and Actuators before its watchdog trips to 4096 [samples] / 4096 [Hz]= 1 [sec] and 8192 [samples] / 4096 [Hz] = 2 [sec], respectively (where it had previously been 10 [samples] / 4096 [Hz] = 0.0024 [sec] for these channels). See attached screenshot of the relevant WD block innards.

This has been done and in place at LLO for a few weeks with no obviously adverse affects, (see 16430 and 15998), we were merely replicating their change. As such, they've seen a drastic reduction in HAM6 ISI trips after lock-losses, and we hope to see the same benefits. 

Note, the change involves *unhooking* (disabling and breaking) the 
/opt/rtcds/userapps/release/isi/h1/models/h1isiham6.mdl 
model link to the generic HAM ISI model library part
/opt/rtcds/userapps/release/isi/common/models/isihammaster.mdl
and replacing the WD_SAFE_COUNT tag input to each GS13 and ACT blocks (inside the HAM6 WD block) with hard-coded constants of 4096 and 8192. 
I've committed the unhooked model to the repository.

For the restart, I
- Brought the OMC suspension to SAFE
- Turned off all output to OMs 1-3
- Asked the SEI_HAM6 manager to take the chamber to DAMPED
- Paused the SEI_HAM6 manager (to make sure ISI_HPI is left alone and happily running)
- Changed the ISI_HAM6 subordinate to exec
- Requested ISI_HAM6 subordinate to READY
- Turned OFF ISIHAM6's master switch 
- Recompiled, Reinstalled, Restarted h1isiham6 front end process on h1seih16 computer
- Requested ISI_HAM6 subordinate to DAMPED, confirmed IOP output
- Changed the ISI_HAM6 subordinate back to managed
- Changed the SEI_HAM6 manager back to exec (who came back, happily fooled that it never left the DAMPED state)
- Requested SEI_HAM6 manager to return to ISOLATED.
- Restored OMC suspension to ALIGNED
- Restored alignment and damping to OMs 1-3 (and a random Y offset of 2000 [ct] on the TEST filterbank).
Note, also, since I merely changed constants in the model, the change did NOT require a DAQ restart.
I also attach trends of the P and Y of the HAM6 suspensions (as measured by their local OSEM sensors), confirming that they've been restored to the same alignment.