Detector still can't lock and called me again. It looks like it's been getting locklosses from Green Arms, Find IR, and DRMI, and it mostly looks like it's due to ALS dropping out. It's even gotten DRMI but then had multiple MC2 saturations before losing lock at DRMI_LOCKED_CHECK_ASC. I have no idea why it's struggling so much. I can only think that it might be related to the wind. The wind is still coming and going, and it isn't too strong, but maybe the changes in wind speed are still kind of a lot for the lower states right now? I'm putting the detector in DOWN until 14 UTC and at that time I'll try again and call someone if I don't think it's related to anything environmental.

H1 Manager requested assistance after the initial alignment timer ran out. ALSY couldn't lock because the wind has been so strong, especially at EY. The wind was over 40mph and gusting up past 50mph, but when I got called it was below 40mph and still decreasing, so I decided to help it try to lock. I was able to get ALSY to lock and finished Initial alignment with no other issues. We had multiple locklosses during PRMI_ASC, so I went to start another initial alignment, but we were getting a CHECK_CRYSTAL_FREQUENCY error from ALSX, which went back and forth between correcting itself and going into error for about 15 minutes. Now that initial alignment finished, but we keep getting low level locklosses, probably due to the wind gusts. I'm going to let it try and sort itself out and hopefully we can relock. Windy.com says that the wind is supposed to be low the rest of the night, but it said that about the current situation too, so it might just not be predicting gusts very well. I'll check back in in a few hours if it's still having trouble.

TITLE: 02/24 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Wind
INCOMING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 41mph Gusts, 25mph 3min avg
    Primary useism: 0.13 μm/s
    Secondary useism: 0.28 μm/s
SHIFT SUMMARY:
H1 was locked for a few hours, until 03:05 when the wind started gusting over 40 MPH.

Since then I have done an Intilal Alignment, and just let it attempt to lock while doing other work.
Observatory mode is set to wind.
H1 currently unlocked Wind still gusting.

LOG:                                                                                                                                                           

TITLE: 02/24 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 39mph Gusts, 23mph 3min avg
    Primary useism: 0.09 μm/s
    Secondary useism: 0.26 μm/s
QUICK SUMMARY:

3:05 UTC Lockloss very likely due to Wind gusts

https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1424401545

While we were out of lock yesterday, I replaced the viewport covers I had removed, so we are ready to go to laser safe when needed.

Robert Schofield, Richard McCarthy, Tyler Guidry, Genevieve Connolly, Ben Mannix, Jonathan Olson

Last summer, Genevieve identified the 35.4 Hz peak as likely from the office area air handler (80655). Recently, Ben was working a Data Quality Shift and reported that the peak had moved by tenths of a Hz and had increased dramatically in amplitude (82519).  This week I used a speaker to sweep in the region around 35 Hz and found that there was a sharp maximum in vibration coupling that happened to lie just where the HVAC peak has been for the last couple of months (See Figure). This meant that, if we could move it just a little in frequency, we would reduce the amplitude in DARM. We power some of the HVAC equipment with variable frequency drives (VFD), which convert the mains 60 Hz to other frequencies. We set the office area air handler VFD to 69 Hz, instead of the 72 Hz that it had been running at, and greatly reduced the amplitude of the peak in DARM (see Figure, page 2).

TITLE: 02/24 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 21mph Gusts, 14mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.26 μm/s
QUICK SUMMARY:
H1 has been locked and Observing for 4 hours now.

0:23 UTC LIGO Hanford Control room received a call about a ADreq  super event candidate S250223dk that was not announced on verbal alarms and no Stand Down signal was given.

Incoming Earthquake from cayman Islands which we should survive.

All other systems are running well.

TITLE: 02/23 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY:

H1 is currently with a 4+hr lock.  Only 1-lockloss during the shift (from an EQ) and ran an Initial Alighnment because of tough ALS locking.  H1 range for this lock started up at 160Mpc, but has dropped down to around 155Mpc in the last 4hrs.  Also, this lock has the ITMy MODE-5 settings of:  FM6+FM8+FM10 w/ gain of +0.010.

CDS:  Been noticing glitches/color splashes on the cameras on nuc35 (mainly MC1 & PR3 for me) last few shifts.

Environmentally, secondary microseism has dropped below the 95th percentile over the last 8-10hrs.  It's been breezy off/on during the shift as well (and it looks a bit stormy outside!).
LOG:

• 1533 updated ITMy MODE 5 settings.
• 1637 GRB Short
• 1809 Bumped out of Observing due to SQZ (which was nice since our range had been drifting down the last 20+hrs)---I was literally looking at "How To Improve Squeezing" instructions when this happened!
• 1832 EQ notification
  • 1855 SEI EQ Mode Activated 
  • 1856 LOCKLOSS
  • 1915 SEI back to CALM
• 1903-1913 Looking for parts in LVEA (corey)
• 1918-1944 Initial Alignment
• 2032 Back to OBSERVING
• 2330 PCal Measurement in PCal Lab (tony)
• 0023 Superevent S250223dk (but it looks mostly terrestrial)

After the SQZ improved H1 range, about 15min later there was a 1832utc notification of an incoming M6.0 Solomon Island earthquake....this would cause a lockloss at 1856utc.  H1's lock was 14hrs22min.

(V1 & L1 are still observing.)

After almost 24 hrs of H1 drifting down about 10Mpc (from about 156 down to 146Mpc, see attachment #1), and while I was looking at instructions for SQZ Checks and Improve Squeezing, H1 was dropped out of Observing due to the Squeezer at 1809utc (coincidentally around the time of the CP1 overfill).  The CLF_LR, FC, and MANAGER nodes went down and then relocked automatically.

As it was relocking, the SQZ came back with a better OPO Temperature (After the SQZ came back, I tried small OPO TEC Temp slider changes, but it was already optimized), and it looks like the SQZ automatically improved H1 range! (see attachement #2)

Was hoping to see the "H1 Live" trace to be better at high frequency, but it is still higher than the reference above 1500Hz (see attachement #3).

Sun Feb 23 10:06:25 2025 INFO: Fill completed in 6min 22secs

TCs started at lower temps because of the warm up outside, so I reduced the trip temps from -30C to -60C. TCmins [-134C, -130C] OAT (+12C, 53F) DeltaTempTime 10:06:25

TITLE: 02/23 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 16mph Gusts, 11mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.41 μm/s
QUICK SUMMARY:

H1's been locked 11hrs.  There's a slow drift in H1 range for the last 24hrs (through 2-locks).  I put in by hand the latest settings for ITMy MODE-5 a few minutes ago.  Microseism still high, but with slight decrease and it's been breezy (up to 25mph) the last 12hrs.

TITLE: 02/23 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
Lockloss from an earthquake
Took a few tries to get it relocked, did an Initial Alignment and it locked just fine.
Nominal_Low_noise Reached at 04:33 UTC
Observing at 04:35 UTC
The nominal settings for the violins seem to be working well, so I did not change it.
H1 has been locked for 1.5 hour.

LOG:
                                                                                                                                                                                                                                    

Lockloss due to a 5.6 Mag earthquake from the Soloman Islands, or a number of smallish earthquakes from the same region.

https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi/event/1424312644

TITLE: 02/22 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 3mph Gusts, 0mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.45 μm/s
QUICK SUMMARY:

Nice shift for H1 with a lock over 12.5hrs.  Also ran the Saturday calibration.  Microseism is still high.

LOG:

• PSL Dust Alarms have been alarming throughout morning.
• 1847 Changed ITMy MODE-5 to Rahul's newest settings after chatting with him: FM6 + FM8 + FM10 Gain +0.01 (+30deg phase)
  • BUT:  This still is not set in Guardian!  Guardian still uses the older settings (60degphase + a gain of 0.0).  If Rahul is happy with the new settings above, we will need to:
    • update lsc_params &
    • Load guardian(s):  would this be VIOLIN_DAMPING only or also ISC_LOOK as well??
• 1930 Calibration Time (but first---wanted to see if taking VIOLIN DAMPING to SIMPLE bumps out of OBSERVING)
  • Taking VIOLIN DAMPING from DAMP_VIOLINS_FULL_POWER to DAMPING_ON_SIMPLE does in fact take H1 OUT of OBSERVING!
  • Restored nominal gain for IY mode1
• 1947 SEI_ENV transitioned to CALM (had been at USEISM since 447utc)
• 2029 PI31 alert, but only for a few seconds.
• 2130-2151 PCal Lab work (tony)
• 2317-2327 Grabbing an optic & checking terminte status in the optics lab (robert)

TITLE: 02/23 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 5mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.41 μm/s
QUICK SUMMARY:

H1 has been Locked for 12.5 hours.
If Unlocked: 
Violin ITMY Mode 5 settings were changed by the Day Ops  by hand because Rahul had mentioned to Corey that IY m5 should not have a zero gain. 
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=82975

Other than that all systems are running well.

Earlier in the shift, happened to notice IY Mode-1's gain was not at nominal (it was at 0 instead of the nominal -10); this mode was NOT rung up and was decent with an OUTPUT around ~2...it was slightly increasing.  (See attachment#1 for a look at this mode for the last 24hrs.)

I had tried to take the gain to -10 while in Observing, but VIOLIN_DAMPING would immediately take the gain back to 0.  I chatted with Rahul and he mentions that sometimes this happens.  We decided to hold off with this gain for a bit, because Rahul was not sure whether taking the VIOLIN_DAMPING guardian from DAMPING_VIOLINS_FULL_POWER to DAMPING_ON_SIMPLE would take us out of Observing, but.....we were going to drop out of observing for Calibration shortly.

VIOLIN_DAMPING Guardian State Change Takes H1 Out Of OBSERVING

At 1930utc, took took the violins guardian to DAMPING_ON_SIMPLE, and this took us out of OBSERVING.  At this point, I then ran the calibration.  Once the calibration measurement was complete, at 2000utc, I took IY Mode-1's gain from 0 to it's nominal of -10.0.

Then returned the violin guardian to DAMPING_VIOLINS_FULL_POWER.  (See attachment#2 for a look at when the gain was restored.)

Measurement NOTES:

• Following instructions (link)
• H1 at NLN for for over ~7.5hrs
• Calibration_Monitor medm screenshot is attached
• 1930-2001 Out of Observing for CALIBRATION
•  Broadband measurement started at 1424287862
  • Measurement at:  /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250222T193048Z.xml
•  Simullines measurement
  • gps START time:   1424288233.610148
  • gps STOP time:  1424289616.0
  •  File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250222T193656Z.hdf5
  • File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250222T193656Z.hdf5
  • File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250222T193656Z.hdf5
  • File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250222T193656Z.hdf5
  • File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250222T193656Z.hdf5
• Then ISC_LOCK was taken back to NLN for observing

Sat Feb 22 10:08:23 2025 INFO: Fill completed in 8min 19secs

TCmins [-81C, -79C] OAT (+4C,40F) DeltaTempTime 10:08:23

While filling out the Lock Reacquisition Survey, noticed that for the two locks overnight:

• ITMy MODE5 did NOT have the special settings entered by hand (i.e. the standard Guardian settings of FM5+FM6+FM10 + Gain of 0.0 were fine); see 1st attachment.
• H1 did NOT need an Initial Alignment last night for the current lock (although it took about 30min [& 11 LOCKING_ALS locklosses] of locking green arms before finally getting over the hump and making it all the way to NLN).  So perhaps H1 is now good with Sheila's Ring Heater change from yesterday. 
  • Also, since the Ring Heater change yesterday (1934utc/1134amPDT), H1 has been running without the recent glitches it had been ailing with (see 2nd attachment).