Ops Eve Shift Summary

TITLE: 06/05 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 134Mpc
SHIFT SUMMARY: Busy shift following first lockloss. Discovered and worked around BS ISI stage 2 kick, waited for earthquakes to pass, and adjusted PR3 due to a slight temperature excursion in the LVEA.

Lock #1:

• Lockloss @ 01:44, 5.2 from New Zealand was passing through causing ASC signals to wobble

Lock #2:

• Both arms ran INCREASE_FLASHES, but still had to adjust ETMY to lock ALS
• DRMI caught easily and ASC came on to maximize POP18, but lost lock at TURN_ON_BS_STAGE_2

Lock #3:

• Automated acquisition through DRMI locking; ASC again came on and maximized POP18
• Lost lock at TRANSITION_DRMI_TO_3F; suspiciously similar place

Lock #4:

• Same result as Lock #3, this time PRMI was needed
• Starting initial alignment to see if that helps

Lock #5:

• IA doesn't seem to have helped, still losing lock when fully isolating BS ISI

Lock #6: (where I finally figure out what's happening)

• Decided to wait in the state before the one seemingly causing the issue, ENGAGE_DRMI_ASC, and let all ASC fully converge
• Able to stay in this state for several minutes comfortably
• When moving to TURN_ON_BS_STAGE_2, this time only a DRMI lockloss instead of a full IFO lockloss
• DRMI was able to quickly relock and ASC turned on
• I noticed that the BS ISI had successfully turned on stage 2 and was now FULLY_ISOLATED (since there wasn't a full IFO lockloss, the SEI_BS guardian was requested to go to FULLY_ISOLATED and stayed there)
• Moving to TURN_ON_BS_STAGE_2 did nothing (as SEI_BS was already in FULLY_ISOLATED)
• Able to continue locking successfully

My impressions of this behavior are that the action of turning on the BS ISI's stage 2 high isolated damping was enough movement to cause the DRMI lock to break, but once it was already on, DRMI was able to lock just fine. Tagging SEI for follow-up. It's possible Tony saw this behavior last night too when trying to lock (from alog 70114: "There were 2 Locklosses at TRANSITION_DRMI_TO_3F").

• Lockloss @ 03:56 from 5.8-magnitude earthquake from New Zealand

Locks #7-10:

• Cannot move past LOCKING_ALS

After ground motion calmed down, I noticed that the beatnotes (especially COMM) had been steadily getting worse along with TR{X,Y} signals. Trending the PR3 oplev, I saw that it had moved a fair amount in yaw compared to its normal fluctuation over the past few days. Since I still couldn't move past LOCKING_ALS, I decided to move PR3 in yaw (slider from 153.2 to 153.5) to bring it back closer to its position last lock acquisition, which improved TR{X,Y} and COMM beatnote. I then ran another initial alignment and looked into if there were any temperature changes that could've caused this motion. LVEA zone 1B has had an excursion this evening that appears to line up with PR3 yaw motion (trend attached, tagging OpsInfo and FMCS), which is strange to me because zone 1B is closest to the vertex, not the input arm, but it may have more of an effect than I'm realizing.

Lock #11:

• Lock acquistion was fully automatic
• Again noticed a kick in buildups during TURN_ON_BS_STAGE_2, but did not cause lockloss this time (screenshot attached)
• NLN reached @ 05:54, observing @ 06:07

Handing off to Tony.

LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
23:30	SQZ	Vicky, Guests	Overpass, LExC	-	Tour	01:24