TITLE: 06/14 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 20mph Gusts, 9mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY:

• We've been observing for almost 2 hours
• Microseism is low and decreasing
• Wind is low/moderate
• Range is OK, we could maybe stand to run a SQZ angle adjust
• I put my settings for ITMX13 into lscparams as they've been working well for multiple locks, FM1+FM4+FM10, G= -0.2
  • VIOLIN_DAMPING could use a reload

I took H1 out of observing for 15 minutes starting at 22:00 UTC when I noticed the range looked low and the SQZ_MANAGER Guardian reported that the SQZ ASC AS42 wasn't on.

Reminding me of the SQZ ASC issues we've been seeing early in lock stretches, I requested SQZ_MANAGER to 'RESET_SQZ_ASC_FDS' and then back to 'FREQ_DEP_SQZ', but the SQZ_LO_LR Guardian reported low OMC_RF3 power.. I then set SQZ_MANAGER to 'DOWN' while I trended ZMs to the last lock when squeezing was good. ZM6 was very far off according to OSEMs (several hundreds of µrad in both pitch and yaw), so I moved it back to where it was at the end of the last lock and requested SQZ_MANAGER again to 'FREQ_DEP_SQZ'. This time, there were no holdups and squeezing was restored, so I promptly returned H1 to observing. BNS range seems to have recovered and SQZ BLRMs look better also.

Lockloss @ 19:35 UTC after 10.5 hrs locked - link to lockloss tool

No obvious cause, but this lockloss was fast (much like others of late).

H1 dropped observing from 18:30 to 19:00 UTC for regularly scheduled calibration measurements, which ran without issue. A screenshot of the calibration monitor medm and the calibration report are attached.

Broadband runtime: 18:30:45 to 11:35:54 UTC

Simulines runtime: 18:36:41 to 18:59:56 UTC

Sat Jun 14 10:09:44 2025 INFO: Fill completed in 9min 40secs

TITLE: 06/14 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 16mph Gusts, 7mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY: H1 has been locked and observing for 5.5 hours. Calibration measurements planned for this morning at 18:30 UTC.

• Fundamental violin modes are elevated (mainly ITMY 5/6), but are coming down slowly
• ETMY roll mode looks to be damped down well
• Will look into why SDF diffs keep waking Corey up
• All other systems nominal

Before going back to bed, wanted to check violins, and noticed that ITMx MODE13 was ringing up again.  I'm guessing the settings RyanC had going were not being used.  So, I put in what RyanC had 2hrs ago for the last lock, and within 2min, it quickly damped out the rung up MODE13.

I have NOT made a change/updated lscparams.

NEW Settings: 

ITMx MODE13:  FM1 + FM4 + FM10 + gain = -0.2

OLD Settings:

ITMx MODE13:  FM1 + FM2 + FM4 + FM10 + gain = 0.0

OK, going back to bed.  Sleep...we'll see.

These ones came up before---I'm hoping I am addressing them correctly this time!  :)

Once these were CONFIRMED, H1 was automatically taken to OBSERVING at 920utc

(RyanC, CoreyG)

Got a Wake Up Call at 1211amPDT, but I was sort of already awake.  RyanC was up after his shift and we were both watching H1 remotely.  He was battling H1 most of his shift and made headway toward the end of his shift and then handed off info for how things were going (the winds started dying down around 9pm-ish).  A few things he did for H1:

• He was concerned with the ETMy Roll Mode.  He ultimately found a typo in ISC lock for the gain.  He fixed that.  
• ITMx Mode 13 was ringing up.  Ryan found a new setting to damp this down & it should be used for next lock.
• For the first time since RyanS's lockloss at the end of his shift, RyanC was able to get H1 back to NLN, but it was too noisy for OMC Whitening to kick in, so we had to wait a while for that to quiet down.  It eventually did, and we were officially at NLN, but we had some SDF diffs.
• SDF Diffs are attached.  I bounced my questions for these SDFs off of RyanC.  
  • For the ETMy Roll, basically did a REVERT to get the gain of 40 (corrected after RyanC found typo)
  • Found the same diffs for IMC MCL threshholds I had last night, so this time, instead of Reverted, I Accepted.  (I thought RyanS was going to do this, or maybe I am too tired to follow this!  Ha)
  • ITMx MOD13 had a phase Diff for FM2, but it was also "not monitored".  I wanted to accept these settings that RyanC found which damped it down, so I ACCEPTED it.
• 0724 Then H1 automatically went to OBSERVING!!  ....for about 75seconds!!!
• 0725 LOCKLOSS due to most likely a M5.0 earthquake off the Chilean coast.
• Locking
  • DRMI flashes were bad.  PRMI was not locking (after check mich fringes), so went for an alignment:
    • 0754-817utc Manual Initial Alignment Run, and for the most part tweaked up alignment similar to what I did back on Jun1st (alog84695)---PRM moved mainly in Yaw.  SRC was misaligned, so SR2 was moved a bit in both P & Y.  And then SRM was tweaked also in both P& Y to optimize AS_A_DC.
  • Currently at DRMICamera flashes look centered and have flashes at/above 100counts.  May head to bed and hope for automation to take over.

TITLE: 06/14 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Aquisition
INCOMING OPERATOR: Corey
SHIFT SUMMARY: A quaternary of issues, environmental (wind and an earthquake), hardware, and software it seems. The new DAMP_BOUNCE_ROLL seems to be killing it everytime it engages so I've commented it out.
LOG:                                       

• 23:44 UTC After the IA DRMI locked with a very nice looking spot after struggling earlier despite good flashes.
• 00:00 UTC I noticed that the OMC was having trouble locking, it wasn't able to get any data/find any peaks. I reached out to Keita and I tried to manually lock it following Camilla's instructions in alog67897 but I wasn't able to see any peaks stepping through the offset. It looks like the PZT voltage wasn't actually changing to actuate it. Keita went to the mezzanine and the voltage was zero, I set the offset to zero and he reset it which brought the DC voltage back and I was able to relock it with the guardian. alog85030
• 00:57 UTC right after we were able to lock the OMC we unfortunately lost lock at POWER_10Ws
  • The wind started to pick up
  • 01:47 UTC, we lost lock a few seconds into the state for the 2nd time in a row. Both LLs tagged WINDY, and ADS_EXCURSION, 1st LL, 2nd LL
  • 02:50 UTC lockloss at DAMP_BOUNCE_ROLL after I slowly stepped through states starting at PREP_ASC, during TMS_SERVO I got "POP X PZT Railed" notifications
    • The comment above this notification in ISC_LOCK says it may be due to PR3 pointing, so I compared its alignment to when we locked earlier using top mass inmons and I adjusted PR3 and PR2
    • In DRMI I had no flashes and AS AIR looked yawed, so I moved PR2 back in yaw like halfway back to where it was and flashes came back and it locked
    • We lost it at DAMP_BOUNCE again, I don't think its an alignment issue anymore, I reverted the PR2 & 3 moves
  • 03:40 UTC I reduced the gain on the DAMP_BOUNCE_ROLL filter from 40 to 30 and doubled the tramp to 10 seconds
  • 03:52 UTC Earthquake mode
  • 04:35, even with the reduced gain and increased tramp we still lost lock right as it engaged, I've commented it out of ISC_LOCK - line 3937

Ryan had a hard time locking the OMC, and there was no DCPD_SUM spikes as Ryan moved the PZT offset manually. We saw nothing in the OMC trans camera either.

I found that the OMC PZT2 monitor dropped to zero-ish at 14:23 PDT (21:23 UTC). That coincides with vacuum-related activity for HAM1, not sure if they are related.

In the mezzanine I found that the output of the HV driver was zero.

Pressing VSET and ISET, I saw that the driver was set up to 110V 80mA. Pressing RECALL -> ENTER didn't do anything. I also noticed at this point that the unit was somehow in CC (constant current ) mode, which is usually automatically determined by the power supply. It should be in CV mode.

I turned the output off, asked Ryan to turn the PZT offset to zero (which means the middle of 0-100V range, i.e. 50V, so I should have asked -50V offset), power cycled the unit just because, pressed VSET again (it was still 110V), pressed ENTER, turned the output ON, and it started working again.

Ryan moved the PZT offset and the HV monitor responded. Shortly after this the IFO lost lock but I don't think that was related to the HV.

TITLE: 06/13 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 17mph Gusts, 11mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY:

• 21:11 UTC lockloss, I ran a coherence measurement at ~5 hours in
• Windy.com forecasts the wind picking up around 04:00 - 05:00 UTC tonight
• We're currently running an IA as DRMI/PRMI has been having trouble locking

Since we've been seeing the ETMY roll mode consistently ringing up over the start of lock stretches and that it can cause locklosses after long enough, Sheila modified the 'DAMP_BOUNCE' [502] state of ISC_LOCK to now engage damping of this mode with a gain of 40. The state has also been renamed to 'DAMP_BOUNCE_ROLL'. I have accepted the gain of 40 and timeramp of 5 sec in the OBSERVE.snap table of h1susetmy and only the timeramp in the SAFE.snap table (screenshots attached; we had originally set the gain at 30 but then updated it to 40, which I forgot to take a screenshot of).

We are still unsure as to why this roll mode has been ringing up since the vent, but so far Elenna has ruled out the SRCL feedforward and theorizes it could be from ASC, specifically CHARD_P (see alog84982 and comments).