J. Kissel

Once we felt comfortably recovered enough (early this afternoon) to head toward initial alignment, Jenne noticed that ISI ITMX ST2 was moving MUCH more than ITMY. 
After poking around  -- (because of item (2) in my previous recovery aLOG from earlier this morning I was accutely aware that there should be NO sensocr correction in Z going to the ISI; LHO aLOG 45938) -- thus I found that the sensor correction path (which, again, is revamped and quite new) had all paths for ALL ground motion degrees of freedom being pumped into correcting the ST1 CPS without any filtering. That will definitely create some excess motion!

This is a result of a bit more SDF confusion --
(1) On a normal day, the seismic platforms (both HEPI and ISIs) SDF systems are run comparing against the OBSERVE.snap (because there should be no change in the platform state between with the IFO is locked vs. unlocked). However, when a model gets restarted it restores to a safe.snap. 
(2) Further, any time you add new filter banks and channels to a model, you have to *initialize* them in the SDF system (go to the "CHANS_NOT_INIT" menu page, and hit the MON ALL button to not only accept the new values but accept them as monitored.) 

Jim had done a great job at initializing and capturing all the SDF changes in the OBSERVE.snaps before we lost the world this morning, and got *almost* all of the safe.snaps updated, but he missed ISI ITMX. C'est la vie, we're only human.

Thus, when ISI ITMX got restarted this morning the all newly revamped and renamed sensor correction filter banks, came up as they had when originally installed: with all filters OFF, the input and outputs ON, and a gain of 1.0. This is a standard of RCG that has been plaguing us for years. Dave agrees and will file bugzilla request.

I've since restored the sensor correction paths to match ITMY, and made sure to capture those settings in both the OBSERVE.snap and safe.snaps.