While bringing things back up on ITMY, we noticed rather large motions around the BSC8 chamber, as noted in Thomas' LHO aLOG 3634. We were concerned that it had to do with the restart of the model (a la March 2012), but as Thomas shows the large motions had started to occur prior to our model restarts. Bram also reports that the cavity had been behaving poorly for an hour or so prior to this computer work. Finally, because we were scared, we manually triggered the entire chambers IOP watchdogs, so we were confident it was not any excitations from any DAC. We further confirmed this by checking both the SUS coil-driver monitor signals, and noted that the ISI's "rogue excitation" monitor also remained green. 

The large motion dissipated after ~ 5 minutes of just waiting (we would have turned everything back on, with damping loops running -- which is more safe that with everything turned off, if we trust CDS infrastructure to be functional -- but the the GS-13s were saturating, which would not allow ISI watchdogs to be reset). It should be noted that though these motions were large, they were not extreme. The QUAD's top-stage OSEMs were visibly wobbling, but only by a few thousand counts. ISI GS13s were railing, but they're extrememly sensitive, and ISI position sensors on both stages indicated that were not hitting the locker-limiter mechanical range of motion.

Also worthy of note -- the recompile, reinstall, restart, and restore of H2 SUS ETMY went smoothly, without trouble. Because adding the channels to the DAQ list is part of the QUAD_MASTER library part, the change was literally identical in both models.