Fairly noisy seismically (useism has been holding at 0.7um/s for last 18hrs & winds are at a steady 9mph).
H1 has been also holding at a steady range of 70Mpc for the last 3hrs (even through some short injections by Robert); Noticeable
.......
Ugh!
4:02: LOCKLOSS: EY Went Crazy!
As I was typing this alog, H1 dropped out of lock. There were no noticeable issues (POP90 had been flat for hours, PI Modes were buried, seismic was noisy, but no changes). However, in addition to the usual HAM6ISI trip, EY's ISI, ETMy, & SUS all tripped.
I reset everyone's Watchdog, but when trying to run ALS, I was getting PDH Alerts (not enough light). Looked further and found that the ETMy DID NOT come back to a normal state:
So I opened ETMx, and then went through everything that looked different with ETMy. After a while, ETMy started to look fine. The ODC even came back green. At around this point, I talked with Betsy and I snapped a photo of ETMy with my phone to her & at this point it looked OK. We looked at the safe.snaps, and the Diffs for ETMy looked known & acceptable.
Additionally, ALS was locking in the Y-arm. So we are hesitantly going to say we are back, but I hope there isn't a switch, gain, filter, etc. which I could have missed.
OK, back at it.
SUS_ETMY Guardian Managmenet [Operator] Errors
As I was fixin' to get back to locking, I had a Guardian error saying SUS_ETMY was Managed by another User (this was me when I tried running an INIT on SUS_ETMY). I had taken it back to AUTO, but apparently, that isn't what I should have done.
With Travis & Betsy talking me through it, we tracked it down to the correct INIT (I had tried ISC_LOCK, with no luck). The error was coming from ALIGN_IFO, so eventually figured out that it needed the INIT to be run. Then we had SUS_ETMY being MANAGED properly.