This morning the Well water tank located behind the carpenter shop was found to be nearly empty with under 1ft of water. At approximately 7:50am the Well water pump was energized and used to fill the tank back up. For noise and vibration considerations the well pump ran water from approximately 7:50am until 8:18am. The well tank is now full again.
TITLE: 08/11 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Aligning
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 4mph Gusts, 2mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.11 μm/s
QUICK SUMMARY:
H1 was down and trying to do an Initial_Alignment but saturating a number of suspensions, verbals warning about IFO_OUT from 14:17 UTC to 14:28 UTC so over 10 minutes of shaking the IFO OUT of the output arm.
I'm getting a persistent DIAG_MAIN message:
FAST_SHUTTER_HV: Fast Shutter HV not Ready
@ 1309 UTC Fast shutter channels:
H1:SYS-MOTION_C_SHUTTER_G_TRIGGER_VOLTS went to 3.877 V when it should have already dropped down to 0.5V or so.
H1:SYS-MOTION_C_SHUTTER_G_TRIGGER_POWER has increased to 1.9 mW when I'd expect it to go back down to 0
Both increased to levels that seem within the operational bound but not what their trends would suggest they should be operating at.
I cannot Close the fast shutter either.
H1:SYS-MOTION_C_FASTSHUTTER_A_READY says Busy.
Error Fault; Not Ready ; Not Closed.
Only CDS alarm this morning is the ongoing valved out PT343B at MX. I have extended its bypass to Wed.
Bypass will expire:
Wed Aug 13 08:05:06 AM PDT 2025
For channel(s):
H0:VAC-MX_X1_PT343B_PRESS_TORR
Earlier 6:08:34 UTC there was an 18V power supply that had stopped working which supplies power to multiple devices including the Fast Shutter infrastructure. The 18V power supply was reset and turned back on which should have powered back on the PZT driver that also gets power from the 18V supply. But the breaker on the back had been tripped.
It looks like shutter did close in that lockloss, which might have been caused by the power failure.
Attached are comparisons of a normal lockloss with that one.
TITLE: 08/11 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
IFO is in NLN and OBSERVING as of 04:48 UTC
Just got to Nominal Low Noise after a 5.8 EQ from Guatemala (lockloss alog 86288).
Otherwise, just the most uneventful of shifts. Relocking was fully auto and DRMI lock was swift post-earthquake.
LOG:
None
Earthquake caused lockloss. This was a 5.8 EQ in Guatemala.
Recently, I noticed that the mystery beam spot on the spool piece near HAM3 was much dimmer after the break this spring than in was before ( 85079) To see if this change may have been associated with the CP-Y move we made during the break, we swept through nearly the entire range of pitch and yaw (-300 to 300) while taking a video. The linked video (https://www.youtube.com/watch?v=DIwnx13NzEU&ab_channel=RobertSchofieldLIGO) shows the view from the MC2 camera viewport before the break and after the break. The drop in intensity over the break is quite obvious, but I can see no further change in intensity during the sweep. The sweep can be monitored in the video, both before the break and after, by the motion of the ghost beam spots on the ballast baffle below PR2 (on the center left of the image). The CP move during the break was larger than these sweeps, so it is still possible that the move during the break was the source of the drop in intensity.
However, another possibility is that the movement of the PR2 beamspot, and the reduction in clipping on the PR2 scraper baffle was the source of the drop in intensity. The last pictures I took of the mystery beam spot before the break were in January of 2025. After that, there were a series of moves of the PR2 beam spot and associated reductions in the intensity of the beam coming out the HAM3 viewport that were made in February of 2025 (82670, 82722, 82740, 82793), reducing the power in the beam that comes out of the viewport from about 17mW to about 3.5mW. The ”before” clip in the video below was made in December of 2024, when the HAM3 viewport beam was in the 17mW era, while the ”after” clip is at 3.5 mW, if we assume it is the same now as before the break (could be worth checking). If the ”mystery” beam spot comes from the edge of the scraper baffle (see figure), then the PR2 spot moves might have reduced its intensity, by a factor of about 5 if it is proportional to the light at the viewport.
The figure shows that there is a spot on the edge of the scraper baffle (which is only there when laser light is present) that seemed to get dimmer when the mystery spot got dimmer. The diagram shows how the reflection/diffraction would light up the wall of the spool piece as seen in the photographs. The edge of the aperture would be lit by the beam that is clipped and especially by the beam reflected off of the baffle to the viewport and reflecting back to the baffle.
TITLE: 08/10 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 14mph Gusts, 7mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.11 μm/s
QUICK SUMMARY:
IFO is in NLN and OBSERVING as of Aug 9 22:42 UTC (25 hr lock!)
TITLE: 08/10 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY:
H1 has been locked for 25 hours.
No drops out of Observing, locklosses, or issues. Survived a 6.1 Mag earthquake from Turkey.
No Superevent Candiates either.
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
19:33 | SAF | Laser HAZARD | LVEA | YES | LVEA is Laser HAZARD | 11:33 |
21:07 | Tour | Ibrihim & Tour | Overpass | N | Leading a tour | 21:37 |
Sun Aug 10 10:07:12 2025 INFO: Fill completed in 7min 9secs
TITLE: 08/10 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 142Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 8mph Gusts, 5mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY:
H1 has been locked and Observing for just over 16 Hours.
All systems seem to be running smoothly.
Superevent candidate S250810ck was announced right before I walked in to the control room.
An hour ago we had an interested earthquake that was pretty close but small enough that we didn't lose lock.
TITLE: 08/10 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
IFO is in NLN and OBSERVING as of 22:42 UTC
As hoped, a very quiet shift in which we were observing for the whole time. Nothing else of note.
LOG:
None
TITLE: 08/09 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY:
Relocking went Smoothly from this morning's Earthquake & lockloss. I was able to do a quick Initial_Alignment while the earthquake rang down.
Made it back to NLN at 16:30 observing at 16:33 UTC.
At 19:06:24 UTC I started a Calibration meaurement that had enough time to thermalize.
At 20:50:50 UTC an incoming earthquake was announced and at 20:58:01 UTC H1 was unlocked by the 5.9M Earthquake.
H1 Relocked just fine without any intervention from me.
NLN reached at 22:40:23 UTC
Observing Reached at 22:42:36 UTC
Handing off a Locked IFO to the Eve Shifter.
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
19:33 | SAF | Laser HAZARD | LVEA | YES | LVEA is Laser HAZARD | 11:33 |
19:23 | Tour | Janos , Jennie, Elenna, Ryan S, Fred & Tours | Control Rm & Overpass. | N | Giving multiple tours | 21:09 |
TITLE: 08/09 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 8mph Gusts, 3mph 3min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.06 μm/s
QUICK SUMMARY:
IFO is in NLN and OBSERVING as of 22:42 UTC
Last two locklosses were due to earthquakes and H1 has otherwise been stable with good range. Expecting a quiet shift.
Command Ran:
pydarm measure --run-headless bb
2025-08-09 12:06:24,938 config file: /ligo/groups/cal/H1/ifo/pydarm_cmd_H1.yaml
notification: new test result
notification: end of measurement
notification: end of test
diag> save /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250809T190625Z.xml
/ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250809T190625Z.xml saved
diag> quit
EXIT KERNEL
2025-08-09 12:11:35,388 bb measurement complete.
2025-08-09 12:11:35,388 bb output: /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250809T190625Z.xml
2025-08-09 12:11:35,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_20250212.ini;gpstime
Approximate Time ran:
~UTC: 2025-08-09 19:17:38
~GPS: 1438802276
2025-08-09 19:17:38,535 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250809T191738Z.hdf5
2025-08-09 19:17:38,543 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250809T191738Z.hdf5
2025-08-09 19:17:38,548 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250809T191738Z.hdf5
2025-08-09 19:17:38,553 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250809T191738Z.hdf5
2025-08-09 19:17:38,557 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250809T191738Z.hdf5
2025-08-09 19:17:38,557 | INFO | Overall driving parameters:
2025-08-09 19:17:38,557 | INFO | Preparing to scan the following sweeps ['DARM_OLGTF', 'PCALY2DARMTF', 'L1_SUSETMX_iEXC2DARMTF', 'L2_SUSETMX_iEXC2DARMTF', 'L3_SUSETMX_iEXC2DARMTF']
2025-08-09 19:17:38,557 | INFO | With parameters: BW: 0.14; DrivingCycles: 40; MinDriveTime: 3; Averages: 5; Overlap: 0; RampUpTime: 3; RampDownTime: 3; SettleTimePercent: 10; ScanTime: 1229
2025-08-09 19:17:38,558 | INFO | For DARM_OLGTF, prepaing EXC: H1:LSC-DARM1_EXC; A: ['H1:LSC-DARM1_IN2', 'H1:LSC-DARM1_EXC']; B: ['H1:LSC-DARM1_IN1', 'H1:LSC-DARM1_IN2']
2025-08-09 19:17:38,560 | INFO | For PCALY2DARMTF, prepaing EXC: H1:CAL-PCALY_SWEPT_SINE_EXC; A: ['H1:CAL-PCALY_RX_PD_OUT_DQ', 'H1:CAL-PCALY_RX_PD_OUT_DQ', 'H1:CAL-PCALY_TX_PD_OUT_DQ']; B: ['H1:CAL-DELTAL_EXTERNAL_DQ', 'H1:LSC-DARM_IN1_DQ', 'H1:LSC-DARM_IN1_DQ']
2025-08-09 19:17:38,562 | INFO | For L1_SUSETMX_iEXC2DARMTF, prepaing EXC: H1:SUS-ETMX_L1_CAL_EXC; A: ['H1:SUS-ETMX_L1_CAL_EXC']; B: ['H1:LSC-DARM_IN1_DQ']
2025-08-09 19:17:38,563 | INFO | For L2_SUSETMX_iEXC2DARMTF, prepaing EXC: H1:SUS-ETMX_L2_CAL_EXC; A: ['H1:SUS-ETMX_L2_CAL_EXC']; B: ['H1:LSC-DARM_IN1_DQ']
2025-08-09 19:17:38,565 | INFO | For L3_SUSETMX_iEXC2DARMTF, prepaing EXC: H1:SUS-ETMX_L3_CAL_EXC; A: ['H1:SUS-ETMX_L3_CAL_EXC']; B: ['H1:LSC-DARM_IN1_DQ']
2025-08-09 19:17:38,579 | INFO | Start data collection while monitoring 5 processes
2025-08-09 19:17:49,583 | INFO | Scanning frequency 7.97 in Scan : PCALY2DARMTF on PID: 2113968
2025-08-09 19:17:49,583 | INFO | Scanning frequency 12.86 in Scan : L1_SUSETMX_iEXC2DARMTF on PID: 2113971
...
...
...
2025-08-09 19:40:11,968 | INFO | Drive, on L1_SUSETMX_iEXC2DARMTF, at frequency: 12.33, and amplitude 15.362, is finished. GPS start and end time stamps: 1438803608, 1438803625
2025-08-09 19:40:12,277 | INFO | 0 still running.
2025-08-09 19:40:12,277 | INFO | gathering data for a few more seconds
2025-08-09 19:40:18,285 | INFO | Finished gathering data. Data ends at 1438803635.0
2025-08-09 19:40:18,396 | INFO | It is SAFE TO RETURN TO OBSERVING now, whilst data is processed.
2025-08-09 19:40:18,396 | INFO | Commencing data processing.
2025-08-09 19:40:18,396 | INFO | Ending lockloss monitor. This is either due to having completed the measurement, and this functionality being terminated; or because the whole process was aborted.
2025-08-09 19:41:00,607 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250809T191738Z.hdf5
2025-08-09 19:41:00,615 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250809T191738Z.hdf5
2025-08-09 19:41:00,620 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250809T191738Z.hdf5
2025-08-09 19:41:00,625 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250809T191738Z.hdf5
2025-08-09 19:41:00,630 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250809T191738Z.hdf5
PDT: 2025-08-09 12:41:00.802402 PDT
UTC: 2025-08-09 19:41:00.802402 UTC
GPS: 1438803678.802402
Sat Aug 09 10:06:22 2025 INFO: Fill completed in 6min 18secs
TITLE: 08/09 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
SEI_ENV state: EARTHQUAKE
Wind: 0mph Gusts, 0mph 3min avg
Primary useism: 0.25 μm/s
Secondary useism: 0.12 μm/s
QUICK SUMMARY:
When I walked in H1 was locked and Observing but there was an Incoming 6.0 Mag Earthquake from Severo-Kuril’sk, Russia that caused a lockloss at 14:36 UTC.
TITLE: 08/09 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
IFO is LOCKING at PREP_FOR_LOCKING
IFO was locked for the majority of the shift with one lockloss 04:07 UTC killing a near 9hr lock. Cause still unknown but seems like a glitch from looking at the saturation plots on the H1 lockloss tool.
H1 had poor flashes in DRMI and even worse flashes in PRMI so after letting it try for a bit, I started an initial alignment, which just completed fully auto. We're now locking hopefully also fully automatically with H1 in managed (for the OWL shift).
LOG:
None
Unknown Cause Lockloss. H1 Lockloss tool doesn't flag it as an ETM Glitch though EX L3 seems to have glitched before the other suspensions (attached).
Closes FAMIS 28463. Last checked in alog 85690.
CO2 Trends:
HWS FAMIS:
Plots attached
TITLE: 08/08 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY:
Failrly quick shift due to all the Tours coming through.
Lockloss at 17:26:00 UTC alog 86264
GRB-Short E588408 at 18:26:03 UTC
Nominal_Low_Noise Reached at 19:21:18 UTC
Observing reached at 19:32:18 UTC
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
19:33 | SAF | Laser HAZARD | LVEA | YES | LVEA is Laser HAZARD | 11:33 |
17:04 | Tour | Jennie & Tour | Overpass | N | Running a tour | 17:34 |
17:29 | PEM | Sam | LVEA | Yes | Removing tape from accelerometers | 17:40 |
17:45 | Tour | Cassidy & Tour | Overpass | N | Running a tour | 18:45 |
19:53 | Tour | Cassidy & Tour | Control room & over pass | N | Running a tour | 20:53 |
22:32 | ISS | Jennie | Optics Lab | N | ISS Array Work | 23:32 |