Ryan S, Camilla

Corey 82849, Ryan and I have had some issues with SQZ this morning. Corey adjusted the SHG temp to get enough green power to lock the OPO but after that the SQZ and range was bad. FR3 signal and FC WFS were very noisy.

Ryan tried to take SQZ out, checked OPO temp (fine), reset the SQZ angle from 220deg back to a more sensible 190deg and then put SQZ back in again but he couldn't get the FC to lock. Followed steps in the SQZ wiki to touch up FC1/2 alignment and got  H1:SQZ-FC_TRANS_C_LF_OUTPUT to >120, plot. but we still were loosing the FC at TRANSION_TO_IR_LOCKING. THE FC also seemed unstable when locked on green. While we were troubleshooting, the IFO lost lost. Unsure if this is an ASC issue, FC_ASC trends attached (POS for Y and P were moving much more than usual), SQZ ASC trends (ZM4 PIT changes alot).

After the lock loss, the SQZ_FC seemed to lock stably in green with H1:SQZ-FC_TRANS_C_LF_OUTPUT = 160. Plot. This is higher than usual and it's not clear what changed!

Ryan mentioned that something happened to Oli at the weekend where the range was bad but SQZ unlocked and re-locked and it came back good, plot, but this seemed to the the OPO PZT changing to a better place (we know it likes ot be ~90 rather than 50s).

After relocking, everything was fine but the FC ASC wasn't turning on as the threshold was too low, 2.5. Ryan decreased H1:SQZ-FC_ASC_TRIGGER_THRESH_ON from 3.0 to 2.0, this has been slowly decreasing, maybe as we decreased the OPO trans from 80uW to 60uW last week. Plot. Ryan accepted in sdf and then checked SQZ_MANAGER, SQZ_FC, sqzparams to check this isn't set in GRD.

Mon Feb 17 10:13:43 2025 INFO: Fill completed in 13min 40secs

TCmins [-49, -48C] OAT (+2C, 36F) DeltaTempTime 10:13:43

TITLE: 02/17 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 130Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 2mph Gusts, 0mph 3min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.64 μm/s
QUICK SUMMARY: H1 has been locked for just over an hour but only observing for about half that as SQZ was having issues locking (see Corey's alog).

• Wind is low, microseism still just above 95th percentile

1452utc (652ampdt):  Wake up call due to No Squeezing.

SQZ Symptoms & Solution:

• SQZ Manager not able to get to FDS.
  • Taken to DOWN
• SQZ_OPO_LR node not able to get through ENGAGE PUMP ISS
  • USERMSG 0: No pump ISS means injecting bad squeezing. Going DOWN.
  • Then goes down and repeats.
• Following the SQZ wiki instructions, focused on OPO_LR.
  • OPO_TRANS_LF_OUT_DQ is just under 40counts and is LOWER than "opo_grTrans_setpoint_uW" (which is currently 60).
  • adjusted SHG TEC SETTEMP (started at 35.12 counts with a SHG GR_DC POWERMON OF 92).
  • Eventually took Set Temp down to 33.70 counts for a GR_DC_POWERMON OF 124 (see attached).
  • Took OPO_LR to LOCKED CLF_DUAL, then SQZ MANAGER to FDS, accepted the new SHG temperature set point (see attached), and...
• 1538utc Back to OBSERVING

TITLE: 02/17 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Currently relocking and in ENGAGE_DRMI_ASC. After we lost lock right at the end of Ryan's shift, we were able to get back up relatively easily after I ran an initial alignment. We got knocked out by an earthquake though, and we just finished running another initial alignment. The only difficulty in getting relocked for me has been ALSX and Y - they've still been liking to drop out every once in a while, even right after an initial alignment.

After trying and failing to improve squeezing earlier today (two locks ago) with Ryan, squeezing (and subsequently range) also wasn't great when we got relocked this last lock. However, an hour in, we dropped out due to the SQZ filter cavity unlocking, and when it relocked, squeezing was back to being around -4db. Not sure what was changed there, but it got us back to around 155Mpc, which was very appreciated, even if it's not an amazing range.
LOG:

00:49 Lockloss
    - Started an initial alignment since ALS flashes didnt look good and I knew there would be issues with ALSY dropping out
02:08 NOMINAL_LOW_NOISE
02:11 Observing
    02:57 Out of Observing due to SQZ FC unlocking
03:01 Back into Observing

05:16 Lockloss
    - Ran an IA

I was looking at the lockloss sheet and noticed that this weekend, there were three locklosses that were similar to each other. Ryan Short noted one in an alog a couple days ago: 82809.

The locklosses look similar to what we sometimes see when we lose lock due to ground motion from an earthquake or wind, but in all three cases there was no earthquake motion, and the wind was below 20mph. There will be an 11 Hz oscillation starting about 1 second before the lockloss, and it can be seen in DARM, all QUADs, MICH, PRCL, and SRCL.

Lockloss times:

2025-02-14 07:15 UTC

2025-02-14 21:15 UTC

2025-02-16 09:48 UTC

There was another instance of a lockloss that looked just like these on February 7th 2025 at 05:47UTC as well.

Lockloss @ 02/17 05:16 UTC  after 3 hours locked due to an earthquake. Earthquake didn't shake the ground too hard, but we still lost lock becuase secondary microseism is also really high.

TITLE: 02/17 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Aligning
INCOMING OPERATOR: Oli
SHIFT SUMMARY: H1 has been locked for 3 hours. As I'm posting this, H1 is unlocked and running an alignment. One lockloss this morning, then much of the shift was spent attempting to relock H1 with several failed attempts. After relocking, we noticed the range was noticeably lower than recent locks and that DARM in higher frequencies looked poor, pointing to SQZ not being optimized.

SQZ Troubleshooting: I started by just trying to take SQZ_MANAGER to 'DOWN' then back up to 'FREQ_DEP_SQZ' to see if that would fix the range issue, but the FC ASC was not turning on after the FC locked. The SQZ-FC_ASC_TRIGGER_INMON was not reaching its threshold of 3 to turn ASC on, so I thought improving FC alignment by adjusting FC2 might help. Ultimately, after following the FC alignment instructions from the SQZ troubleshooting wiki, the FC would not lock at all in IR, so I reverted my FC2 move and then attempted to adjust the OPO temperature. Again following the instructions on the wiki, with SQZ_MANAGER in 'LOCK_CF,' I was able to improve SQZ-CLF_REFL_RF6_ABS_OUPUT and the FC was able to lock successfully with ASC on. After then taking SQZ_MANAGER all the way up to 'FREQ_DEP_SQZ,' I again adjusted the OPO temperature (in the other direction) as both the inspiral range and SQZ BLRMS looked worse than when we had started. I was able to bring these back to about where they were when I dropped observing, so ultimately this adventure didn't provide much improvement. H1 then returned to observing.

 LOG:

• 17:03 - Lockloss - alog82837
  • Many locklosses during ALS and DRMI
  • 18:48 - Lockloss in TRANSITION_FROM_ETMX
  • 19:36 - Lockloss in TRANSITION_FROM_ETMX
  • 20:27 - Starting initial alignment
• 21:35 - Observing
• 23:29 - Dropped observing to try and improve range (see above)
• 00:30 - Observing
• 00:49 - Lockloss - alog82842

Lockloss @ 02/17 00:49 UTC after over 3 hours locked

TITLE: 02/17 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 140 Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 9mph Gusts, 5mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.53 μm/s
QUICK SUMMARY:

Currently Observing and have been Locked for 3 hours. Our range was bad, which we figured was due to squeezing being way worse than last lock and not getting better with thermalization. We popped out of Observing to adjust squeezing but it was giving us issues and we had trouble getting IR to lock (see Ryan's alog). Finally were able to get the filter cavity locked by adjusting the OPO temp, but our squeezing was still bad, so Ryan adjusted the OPO temperature again and got a tiny bit of squeezing out (-1db), but not much. Range is basically back to where it was before all this.

Lockloss @ 17:03 UTC - link to lockloss tool

ETMX glitch lockloss, no other obvious cause.

Sun Feb 16 10:11:43 2025 INFO: Fill completed in 11min 40secs

TCmins [-54C, -53C] OAT (+1C, 34F) DeltaTempTime 10:11:46

Lockloss @ 21:15 UTC - link to lockloss tool

The lockloss tool tags this as WINDY (although wind speeds were only up to around 20mph) and there seems to be an 11Hz oscillation that starts about a second before the lockloss seen by all quads, PRCL, MICH, SRCL, and DARM.

BS Camera stopped updating just like in alogs:

• 79685 My alog noting the issue for me back in Aug 2024.
• 79648 Dave's Solution

This takes the Camera Sevo guardian into a neverending loop (and takes ISC LOCK out of Nominal and H1 out of Observe).  See attached screenshot.

So, I had to wake up Dave so he could restart the computer & process for the BS Camera.  (Dave mentioned there is a new computer for this camera to be installed soon and it should help with this problem.)

As soon as Dave got the BS camera back, the CAMERA SERVO node got back to nominal, but I had accepted the SDF diffs for ASC which happened when this issue started, so I had to go back and ACCEPT the correct settings.  Then we automatically went back to Observing.

OK, back to trying to go back to sleep again!  LOL