Got a notification for H1 assistance. H1 dropped from observing just under 3.5hrs ago. After a couple of PRMI cycles, DRMI did lock within 40min, but immediately lost lock at DRMI LOCKED CHECK ASC. Then an Initial Alignment was immediately run in just under an hour @1024UTC. At this point, H1 attempted lock but had another lockloss at DRMI LOCKED CHECK ASC again, but after this lockloss H1 made it up to CARM 5PicoMeters for the next lockloss. Next attempt made it to a CARM OFFSET Reduction Lockloss. Then after no luck locking PRMI and it being over 3hrs, I got the wake up call.
It's sounding like H1 has been having this Locking ailment as of late.
Going to let it finish a 2nd IA I started at @1253UTC after seeing that PRMI looked fine (flashes looked good on camera and are over 100 counts for POP18/90). Initial Alignment just completed and locking clock is restarting.
(Which is good, because my NoMachine is having the symptom that the mouse pointer does not match it's location in my No Machine session intermittantly (basically I'll have the mouse pointer over a spot, i.e. "X" to close an MEDM window, but when I try to click the "X" with the pointer, the pointer is actually, in the No Machine session, about 10" to the left (or right---basically somewhere else!), so it's hard to operate in my NoMachine session. The mouse would be fine on my laptop's monitor. I've had this issue off and on for a few months. With that said, ....after about 15min, my mouse now works OK in NoMachine!)
H1 is now back to DRMI (after the recent Alignment). Camera flashes look centered and POP18/90 flashes are just under 200. Leaving H1 for automatic operations while I see if I can get return to sleep. At 1325UTC/625amPDT, DRMI locked, btw.
It looks like before Corey was called, there were some locking attempts that got up past DRMI. Before he was called, there were two locklosses from DRMI_LOCKED_CHECK_ASC (which we have figured out was due to some SRC1 offsets being turned on by accident), then one lockloss from CARM_5_PICOMETERS, then two lockloss from CARM_OFFSET_REDUCTION. So that makes a lot more sense as to why it didn't call for three hours!