The good news is that it looks like someone must have set our seismic system to the Large EQ mode before this morning's EQ hit, and none of the seismic systems are tripped now, the ISIs are set to damped with feedforward off and sensor correction seems to be off.
ITMY suspension was unfortunately set to safe, I assume this is left over from the fix earlier in the week. The attachment shows a comparison of ITMX and ITMY top mass osems (ITMY oplev beam is not on the QPD in safe mode) during the EQ, ITMY was swinging by more than 60 urad peak to peak while ITMX which had suspension damping loops engaged was swinging by about 20 urad at most.
I've turned on the damping on ITMY now. I also hit the button RECOVER EQ on the ISI_CONFIG screen, I got some errors from the script but it did take the ISIs to the windy state (screenshot attached).
It might be good to add to the operator tasks a check that suspensions and ISIs are in a good state before leaving for the night or weekend. (ie, if suspensions are not damped, operators could make sure they know that it is intentional and there is a good reason for it). Leaving our suspensions damped as much as possible will help us avoid some problems similar to what we had after the Montana EQ last summer. (For reference, while the suspensions were undamped during that EQ they were moving by 10,000 urad peak to peak, so this EQ is not really comparable.)
The original script I wrote for recovering the seismic platforms seemed to have been deleted in the svn update, so I had to write a new one and never got a chance to test it. I've fixed the recovery script, tested it and added it to the svn. With the laser down and not much going on in the way of commissioning right now, I would suggest it is safest to leave the seismic configuration in the state that the red button puts everything. The script doesn't touch the suspensions though.
This is probably my fault. I set ITMY SUS to safe on Feb. 21 before Filiberto started disconnecting cables and didn't think to set it back.
Remember that no files were deleted during the SVN 1.6 to 1.8 upgrade. The original userapps working directory was renamed userapps_1.6. If a file is needed in the new userapps area but it is not under SVN control and it should be, please add it to the repository (using userapps_1.6) and then do an svn update in userapps (please do not just copy the file across). I am happy to help.
Details in alog Link
Changes to the suspension state should be explicit in the WP and it should not be closed until all those steps are completed, I should think.
Patrick, I don't think this is anyone in particular's fault, it is just something that is not anyone's responsibility at the moment. We just need to figure out how to make it routine to check that suspensions are damped, which we hadn't had as a part of any checklist before.