J. Kissel, H. Radkins 

Hugh and I reconciled the seismic systems SDF systems this morning, with 
- The sdf file set to the safe.snap
- the platforms (both ISI and HPI) offline (i.e. the SEI_{CHAMBER} gaurdians were set to OFFLINE), 
- the site-wide sensor correction OFF (i.e. SEI_CONF manager was in SC_OFF_NOBRSXY), and 
- the SEI_DIFF (aka CPS DIFF)  also off (i.e. SEI_DIFF is in the DOWN state).
This is the "no seismic systems or control loops are functional, but they are ready to be made functional" state that we anticipate we want the platforms to be in upon return from a site-wide (or at least seismic wide) computer failure.

In doing so, we made sure that each front-end model that controls these operations (h1isi{chamber}, h1hpi{chamber}, and h1seiproc) had these channels of their safe.snaps appropriately monitored and settings accepted in the above mentioned configuration.

Note, a lot of the sensor correction channels and CPS diff channels are *unmonitored* in the OBSERVE.snaps (the file against which these models are almost always compared, since we expect the seismic system to always be *fully* ON and functional, i.e. rarely-if-ever in its "safe" state), because (a) we're constantly adding states and configurations to these systems and guardians, and (b) we still regularly explore using these different configurations without wanting to take the IFO out of OBSERVATION READY (because we believe that the changes, while they may cause different IFO behavior when *in* a given configuration, the *switching* of configuration is slow enough compared to g-wave signals that it does not warrant not observing.)

I attach a screenshot of a few examples of the channels I captured for the HAMs (Hugh did the BSCs, but didn't take screenshots).

I'll note that the last attachment shows the h1seiproc model showing diffs for the ON/OFF switch of the CPS diff system, but we've left this as a DIFF because we want the system to be OFF (0.0) when the computer reboots, but we currently have it turned *on* because we want it on, and understand why its on (see LHO aLOG 54322).