After a hard fought battle with wind and computer crashes, their efforts paid off and we are Observing! Range is slightly below nominal at ~114Mpc.
There were some SDF diffs for ISIITMX that I accepted since the model was recently brought back up, but perhaps the SEI team can look into why these are different.
LOCKLOSS_SHUTTER_CHECK node was in the SHUTTER_FAIL when I got here, and we were already at high power by the time I noticed. It looks like the check that it makes on the HAM6 GS13 didn't register a kick. I trended this and found that the GS13 channel was just noise during the time that the h1seib3 computer was down. ISC_LOCK was in NLN the entire time as well. I wrote off the shutter test failure to be related to the computer crash, though I'm a bit confused why this channel would be affected by the h1seib3 computer.
I then confirmed that our other fast shutter checking node, FAST_SHUTTER, had a successful test before going to high power. This is a check that it does every lock attempt, so it was reassuring to see that it passed the test for this lock try. With the fast shutter confirmed working, I took the LOCKLOSS_SHUTTER_CHECK node manually to HIGH_ARM_POWER, and then went to Observing.
Some of the differences that were accepted here turned off the CPS differential control for ITMX. Not sure what to do about this, but I think that all of the ISI controls guardians are written in such a way that they won't properly recover the CPS differential controls, blends or sensor correction if an ISI is restarted. The only way to fix this is to init all of those guardians for the chamber. It took until today to find this, because this log was not marked in anyway that got my attention. Unclear if there is anyway to tell if this affected our stability over the weekend, but likely it would have affected our robustness during earthquakes, probably wind, too. Also unsure of the interaction with the microseism focused seismic configurations, but none of those transitions were broadcast either.