Got called at 11:15 PM (PT) due to IFO unable to lock DRMI. Ryan C had warned me before the end of his shift. The issue doesn't seem to be alignment since Initial Alignment was run 3 times over the course of the EVE shift and flashes look sufficient (if not great) to lock. I touched up the BS and PRM in PRMI to no avail. Requested MICH_FRINGES and we'll see if that helps the PRMI lock.
SEI_CONF is not in its nominal position but that seems intentional since the EY sensor correction was turned off today (alog 87634) due to an unrelated issue that happened during maintenance.
In terms of microseism, it's high but it's not that high and we've locked at this level with higher winds in the past week.
I will continue monitoring to see what happens but will resort to the call list if I'm not getting anywhere. I believe we've been unlocked for over 24 hrs now.
Called Jenne (first on call list) after managing to accomplish nothing.
Flashes are good. Alignment is fine. DRMI is locking for 10s before unlocking due to what looks like environmental instability. It seems that 90th percentile+ microseism is just too high to lock - which doesn't make a lot of sense because we've locked with it at a similar level before. Since there aren't any glaring alignment or locking issues other than instability, we assumed it to be due to the environment.
Since microseism seems to be maybe going down slowly, advice given was to set IFO to lock automatically, and if it calls again, then I try again. If this becomes a cycle, then ~4/5 I was given the ok to put IFO in IDLE to avoid violin mode ringups (just like yesterday night). Be back soon (hopefully not).
Well, it seems that as soon as I was writing this, DRMI was conspiring against my statement and actually locked. We're now at PREP_DC_READOUT_TRANSITION.
Getting "Low Recycling Gain" flashing during CARM but it (so far) has not caused a lockloss.
DHARD_P and Y look to be the noisiest signals currently. Let's see what happens.
Lockloss at MOVE_SPOTS with ASC signals oscillating wildly (warning of "waiting for ADS to converge"), same signal as the 4.5Hz MICH oscillation Ryan C reported during his shift. Confused what could be causing this. It seems like oscillating ASC and non-converging ASC were there throughout the lock acquisition. Querying the alog and wiki now. I've attached a screenshot of the oscillating signal, loudest in MICH during powerup ~25W to MAX_POWER