TITLE: 09/13 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Austin
SHIFT SUMMARY:

IFO is LOCKING and is at LASER_NOISE_SUPPRESSION as of submission (07:21 UTC)

Lock Acquisition (not smooth at all)

While attempting lock acquisition, DRMI would not lock, PRMI woul not lock and none of the POP18 abd POP90 traces were anywgere near where they were supposed to be (both just showing noise about 0 counts). Guardian went to check MICH fringes about 5 times before I decided to do an initial alignment. I attemped to manually request/pause at ACQUIRE_PRMI to play the whole BS beam movement game but I couldn't see a second beam after some movement in both yaw and pitch (and guardian kept beating me to it by going into check MICH fringes). There were some strange interference patterns in the AS AIR camera that I hadn't seen before while I was attempting this.

I was checking the troubleshooting documentation throughout this, but found no relevant details to assist with this problem.

Initial Alignment (6:10 UTC)

I had issues getting guardian to perform an automatic (ish) initial alignment. It kept getting stuck trying to lock ALS when ALS had been locked steadily for a few minutes. I manually offloaded green arms and went into the next stage of initial alignment, where it started behaving and moving automatically. During initial alignment, I saw both beams overlaying in the AS AIR camera for the first time since lockloss so that is a good sign (I think). Initial alignment successfully finished so now onto locking!

Post Initial Alignment Lock (6:38 UTC):

DRMI has finally locked. This was definitely some weird alignment issue that got fixed because this time, we didn't even go through PRMI (or MICH Fringes). I expect guardian to manage locking manually.

What was the issue?

I do not know what the root of the lockloss or the lock acquisition was. As said in alog 72852 the wind had died down and there were no significant earthquakes. This leaves the BLRMs glitch lockloss coindcidence.

LOG: