TITLE: 02/09 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 4mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.22 μm/s
QUICK SUMMARY:

• Currently relocking and ALS_X keeps getting dropping out
• Wind is low, 2ndary microseism is just above the 50th percentile

TITLE: 02/09 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Aligning
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Start of shift the IFO was relocking, it made it up without issues. It held for a 6 hour lock, then another lock loss recently. Each reacquisition has needed an initial alignment.
LOG:

• Relock was an automated initial alignment and automated relock.
• 1635 Observing
• 2229 Lock loss
  • Green wouldn't hold initially so I requested an initial alignment. Alignment was auto.

1423175398

The quad L2 outs seem to see it first?

Sun Feb 09 10:07:09 2025 INFO: Fill completed in 7min 5secs

TC temps were high, just cleared the -30C trip. TCmins [-36C, -34C] OAT (-1C, 29F) DeltaTempTime 10:07:08

TITLE: 02/09 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 3mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.26 μm/s
QUICK SUMMARY: Recent lock loss with the IFO struggling to lock green, though it seems like one arm is just dropping lock with great arm power repeatedly. I'm going to start an initial alignment.

TITLE: 02/09 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: I had a _small struggle to align XARM_IR, but I managed to get everything aligned enough. We're relocking at DC_READOUT.
LOG: No log.

• 23:31 UTC lockloss from a 7.6 earthquake from Cayman islands
  • Held in down for ~3 hours until the ground motion has reduced enough to try to lock
  • 03:54 UTC I started an IA after "IR was not found"
  • Couldn't aquire XARM_IR, probably since HAM2 tripped so the INPUT pointing isn't good.
    • Tried setting PR2 and IM4 back their top mass osems positions from the earlier IA ( I probably should have done the rest of the IMs here as well)
    • Tried reverting alignments to the same point during the last IA (20:18 UTC 02/08) then restarted with GREEN_ARMs again
    • I couldn't lock XARM IR again so I treneded back all the IMs top mass osems and moved them back to where they were during XARM_IR in the last IA earlier today
      • I started with IM4 and when I got to IM1_P I saw us finally center on the ASC_TR_B QPD that I had been watching and getting concerned that it wasntt getting any better until I hit IM1, once I got it close the automation took over and finished the IA.
        • I had to move each the IMs dozens of microradians

TITLE: 02/09 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:
A day full of Tours. 

I tried to do a calibration and Lost lock during the Simulines, alog 82699. 
Relocking went very smothly after an Initial alignment.

Every thing was going well until a very sudden 7.6 Magnitude Earthquake struck which almost Immidiately unlocked us tripped multiple ISI's.


LOG:

TITLE: 02/09 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Earthquake
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: LARGE_EQ
    Wind: 3mph Gusts, 1mph 3min avg
    Primary useism: 107.61 μm/s
    Secondary useism: 16.20 μm/s
QUICK SUMMARY:

• We lost lock to a large earthquake (7.6) off the gulf of Honduras recently
  • It'll probably be a few hours till I can start relocking (3?)

When verbals announced an earthquake I checked the SEI screen the earthquake was listed as an 8.0 Mag!

I then quickly checked USGS and they also had listed it as an 8.0 Mag but it seems like it has since been demoted to a 7.6?
https://earthquake.usgs.gov/earthquakes/eventpage/us7000pcdl/executive

When it struck all the ISI's trip before verbals could finish announcing the earthquake.
I immidiately called Jim and ask him if I should hit the very large Earthquake button, but he said if things were already tripped then it doesn't really matter.




 

Dropped from Observing at 19:32:21 UTC
running calibration at 19:33 UTC

Command Ran:
pydarm measure --run-headless bb

notification: end of measurement
notification: end of test
diag> save /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250208T193344Z.xml
/ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250208T193344Z.xml saved
diag> quit
EXIT KERNEL

2025-02-08 11:38:55,388 bb measurement complete.
2025-02-08 11:38:55,389 bb output: /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250208T193344Z.xml
2025-02-08 11:38:55,389 all measurements complete.

Command ran:
gpstime;python /ligo/groups/cal/src/simulines/simulines/simuLines.py -i /ligo/groups/cal/H1/simulines_settings/newDARM_20231221/settings_h1_20241005_lowerPcal_higherPUM.ini;gpstime
PST: 2025-02-08 11:42:39.733837 PST
UTC: 2025-02-08 19:42:39.733837 UTC
GPS: 1423078977.733837
2025-02-08 19:42:40,790 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250208T194240Z.hdf5
2025-02-08 19:42:40,798 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250208T194240Z.hdf5
2025-02-08 19:42:40,802 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250208T194240Z.hdf5
2025-02-08 19:42:40,807 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250208T194240Z.hdf5
2025-02-08 19:42:40,811 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250208T194240Z.hdf5
2025-02-08 19:42:40,811 | INFO | Overall driving parameters:

Lockloss 20:04 UTC During the simulines

Output:

2025-02-08 20:04:44,126 | INFO | Scanning frequency 1200.0 in Scan : DARM_OLGTF on PID: 2461496
2025-02-08 20:04:44,127 | INFO | Drive, on DARM_OLGTF, at frequency: 1200.0, is now running for 23 seconds.
2025-02-08 20:04:47,234 | INFO | Drive, on L1_SUSETMX_iEXC2DARMTF, at frequency: 11.13, and amplitude 13.856, is finished. GPS start and end time stamps: 1423080282, 1423080300
2025-02-08 20:04:47,234 | INFO | Scanning frequency 12.33 in Scan : L1_SUSETMX_iEXC2DARMTF on PID: 2461503
2025-02-08 20:04:47,235 | INFO | Drive, on L1_SUSETMX_iEXC2DARMTF, at frequency: 12.33, is now running for 25 seconds.
2025-02-08 20:04:49,049 | ERROR | IFO not in Low Noise state, Sending Interrupts to excitations and main thread.
2025-02-08 20:04:49,049 | ERROR | Ramping Down Excitation on channel H1:SUS-ETMX_L1_CAL_EXC
2025-02-08 20:04:49,049 | ERROR | Ramping Down Excitation on channel H1:LSC-DARM1_EXC
2025-02-08 20:04:49,049 | ERROR | Ramping Down Excitation on channel H1:CAL-PCALY_SWEPT_SINE_EXC
2025-02-08 20:04:49,049 | ERROR | Ramping Down Excitation on channel H1:SUS-ETMX_L3_CAL_EXC
2025-02-08 20:04:49,049 | ERROR | Ramping Down Excitation on channel H1:SUS-ETMX_L2_CAL_EXC
2025-02-08 20:04:49,049 | ERROR | Aborting main thread and Data recording, if any. Cleaning up temporary file structure.
ICE default IO error handler doing an exit(), pid = 2461462, errno = 32
PST: 2025-02-08 12:04:53.378517 PST
UTC: 2025-02-08 20:04:53.378517 UTC
GPS: 1423080311.378517


I just finished an Initial Alignment.

Sat Feb 08 10:06:41 2025 INFO: Fill completed in 6min 37secs

TCmins [-49C, -47C] OAT (-2C, 28F) DeltaTempTime 10:06:40

On Thursday Erik extended FMCSSTAT to monitor the FCES and End Station VEA temperatures ALOG82673

I have added the new channels to the FMCS STAT overview MEDM, which is generated by the script generate_fmcs_stat_medm.py

TITLE: 02/08 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 2mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.15 μm/s
QUICK SUMMARY:

H1 has been locked for almost 5 Hours.
All systems look great, at first glance.

LHO plans to drop from Observing for caibration from 19:30- 20:00 UTC.
 

TITLE: 02/08 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 51Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

H1 lockloss after 14+hr lock.  During locking, took opportunity to (1) LOAD Violin_Damping & (2)Address POP_A p/y offsets.  Within 2-3min of getting to OBSERVING, S250208ad GW Candidate rolled through.

There have been elevated PSL Dust counts throughout the shift.
LOG:

• 0040--0120 Visits to EX, MX, Mechanical Room (mike, janos)
• 0119 implemented ITMy M5 new violin damping settings (from RyanC)--need to LOAD VIOLIN_DAMPING to have guardian use these settings.
• 0210 Locklos
  • 0210 VIOLIN DAMPING LOADed & took GRD IFO to MANAGED
  • 0214 INITIAL ALIGNMENT
    • 0235 ISC LOCK restarts another alignment!!  (we were in MICH BRIGHT when this happened!)
    • Had noticed that ISC LOCK was MANAGED (by H1_Manager....but why?)
    • 0235 H1 Manager's log notes "waiting for green"  timer was DONE.....AND then it selected to do an Alignment----but I was already running one!  :-/
    • I took H1 Manager to IDLE and ISC LOCK to AUTO
  • 0235-0251 Initial Alignment (Round 2! started by H1 manager)
  • Locking to NLN was pretty straightforward. 
  • Took opportunity to add offsets to POP_A's pit & yaw with Sheila's instructions and her over the phone.  This included another LOAD of ISC_DRMI (see alog).
• 0348 OBSERVING
• 0351 GW Candidate Event S250208ad
• 0418-0423 out of observing due to PI24

After the ETMx Glitch Lockloss, had the opportunity to address the POP_A Offsets via Sheila's alog (but she also phoned in to walk me through it!)  :) 

• Held ISC_LOCK at PREP_DC_READOUT_TRANSITION
• Took lines 1030 & 1031 of ISC_DRMI.py to TRUE (from false):
  • self.usePRC1 = True  #returned to TRUE after adding new POP_A Pit OFFSET on feb7, 2025
  • self.usePRC2 = True  #returned to TRUE after adding new POP_A Pit OFFSET on feb7, 2025
  • ISC_DRMI.py LOADed
• Entered new OFFSETs for POP_A pit/yaw (which had been 0).  Now they are:
  • H1:ASC-POP_A_PIT_OFFSET = -0.465
  • H1:ASC-POP_A_YAW_OFFSET = -0.557
• ACCEPTED the new POP_A OFFSETs in the ASC safe.snap (attached)
• Continued on to Nominal Low Noise
• ACCEPTED the new POP_A OFFSETs in the ASC observe.snap (attached)
• Back to Observing at 0348utc.  Also took a screenshot of all the windows I had up for this change (attached)

H1 just had an ETMx Glitch lockloss (after 14.25hr lock).

H1 MANAGER Ended An Alignment To Start Another Initial Alignment!

Some weirdness was that I proactively ran an Initial Alignment, but while in MICH BRIGHT, ISC_LOCK took over and restarted an Initial Alignment at 0235utc!! (I had GRD IFO in MANAGED...but noticed that ISC LOCK was also still MANAGED [by H1 MANAGER]).  H1 Manager's log had a note about a timer "waiting for green" was done, so h1 manager thought we needed to run an alignment.   :-/

At any rate, let this 2nd Alignment run through, and now back to locking.

See that h1's violin is still high, and then noticed that ITMy Mode5 is currently running with:  0.0 gain + FM8 ON.  To damp this down since the big ring-up on Tuesday, Ryan C found some settings which had been working (and after a few days of seeing them help, he updated lsc_params to with these new settings, BUT we need to run a LOAD of VIOLIN_DAMPING to implement these settings next time we are out of OBSERVING (this LOAD slipped my mind after my lockloss a few minutes before the end of my shift).

In the meantime, I made the change by hand (~13.5hrs into our current lock):

• 0119utc I took the gain to -0.01 + turned FM8 OFF  (all of this done while in OBSERVING)