ibrahim.abouelfettouh@LIGO.ORG - posted 16:05, Sunday 19 October 2025 (87571)
Lockloss 20:28 UTC
Lockloss due to 1Hz Ringup.
Lockloss due to 1Hz Ringup.
Closes FAMIS 27399. Last checked in alog 87406
Laser Status:
NPRO output power is 1.856W
AMP1 output power is 70.51W
AMP2 output power is 139.5W
NPRO watchdog is GREEN
AMP1 watchdog is GREEN
AMP2 watchdog is GREEN
PDWD watchdog is GREEN
PMC:
It has been locked 26 days, 4 hr 48 minutes
Reflected power = 24.74W
Transmitted power = 106.7W
PowerSum = 131.4W
FSS:
It has been locked for 0 days 0 hr and 55 min
TPD[V] = 0.5245V
ISS:
The diffracted power is around 3.4%
Last saturation event was 0 days 1 hours and 5 minutes ago
Possible Issues:
PMC reflected power is high
Wind is still high. Microseism is rising now.
Managed a 2-minute DRMI lock and that's the highest we've gotten today. If we continue failing and the wind/microseism stays high, I will go into IDLE again until I see any improvements.
Sun Oct 19 10:08:45 2025 INFO: Fill completed in 8min 41secs
TITLE: 10/19 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 31mph Gusts, 16mph 3min avg
Primary useism: 0.05 μm/s
Secondary useism: 0.37 μm/s
QUICK SUMMARY:
IFO is LOCKING at ENGAGE_SOFT_LOOPS
IFO was in the middle of an automatic relock when I arrived. Wind was very high last night but looks to be coming down.
Should be able to go into OBSERVING soon.
Wind did not end up going down - we lost lock at TRANISTION_ETMX and now are unable to lock ALS (it locks for a few minutes before losing lock). I think it's a combination of 90th% microseism and 35+mph gusts. According to forecasts, thewind will only begin dying down at ~2PM.
Had a lull in wind, managed to do a fully auto initial alignment - then wind went back up over 35mph and continued losing lock. After over 15 pre-DRMI locklosses where alignment itself looks great, I've put H1 in IDLE for 30 minutes as wind comes down (though it's currently trending up).
TITLE: 10/19 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Overall a fairly quiet shift. After an unknown lockloss earlier this evening, I ran H1 through an alignment and it was able to relock fully on its own. H1 has been locked since, now for 3.5 hours.
LOG:
Lockloss @ 00:06 UTC after almost 9 hours locked - link to lockloss tool
No obvious cause.
Back to observing at 01:37 UTC. Ran an alignment, then locking went fully automatically.
No sign of the CSOFT_P ringup after reaching NLN. Also the range is better this lock at around 160Mpc.
Ibrahim and Sheila saw yesterday a lockloss after just 9 minutes in Nominal Low Noise from CSOFT_P ringing up at 1 Hz, and we again had one overnight at 05:21 UTC (can't link to online lockloss tool since it was down at the time). In both cases, the IFO had been down for several hours beforehand. After the ASC lockloss last night, the IFO relocked within an hour on its own and this CSOFT ringup did not; see first ndscope screenshot of the comparison between these two times. At the start of the third lock stretch overnight, after the IFO was only down for just under 3 hours, CSOFT_P did ring up the same amount of time into Nominal Low Noise, but this time it did not cause a lockloss and eventually calmed back down; see second screenshot. At the start of this lock stretch, after the IFO was down for under 2 hours, CSOFT_P did not seem to ring up at all; see third screenshot. This suggests to me that with a warmer IFO, CSOFT_P doesn't seem to ring up as much at low noise.
The history of this ringup and the last time we changed the CSOFT_P gain can be seen in alog85649. Sheila suggests if we see this ringing up again, we can try bumping the CSOFT_P gain up from 25 to 30.
TITLE: 10/18 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:
IFO is in NLN and OBSERVING
We have been observing for the whole day.
Acquired lock at 19:10 UTC and H1 was thermalized by the time we had to run the weekly calibration sweep, which ran successfully. Alog 87553.
Range has been consistent and comparable with last few days but seems low in the low frequency range compared to 2 weeks ago. Ryan S is investigating this.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 21:15 | EPO | Mike Landry + 50 | Overpass | N | Teacher Conference Overpass Visit | 21:35 |
TITLE: 10/18 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 10mph Gusts, 6mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.47 μm/s
QUICK SUMMARY: H1 has been locked for 7.5 hours. Range is a bit lower than usual; I'll run a range comparison in a bit.
Comparing to a time almost 2 weeks ago, DARM appears noisier broadband; report attached.
Saturday standard coordinated calibration sweep
BB Start: 1444847709
BB End: 1444848020
Simulines Start: 1444848233
Simulines End: 1444849630
2025-10-18 19:06:16,282 | INFO | Finished gathering data. Data ends at 1444849593.0
2025-10-18 19:06:16,498 | INFO | It is SAFE TO RETURN TO OBSERVING now, whilst data is processed.
2025-10-18 19:06:16,498 | INFO | Commencing data processing.
2025-10-18 19:06:16,498 | 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-10-18 19:06:52,301 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20251018T184336Z.hdf5
2025-10-18 19:06:52,309 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20251018T184336Z.hdf5
2025-10-18 19:06:52,314 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20251018T184336Z.hdf5
2025-10-18 19:06:52,319 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20251018T184336Z.hdf5
2025-10-18 19:06:52,324 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20251018T184336Z.hdf5
PDT: 2025-10-18 12:06:52.452839 PDT
UTC: 2025-10-18 19:06:52.452839 UTC
CALIBMONITOR attached (took screenshot after requesting NLN_CAL_MEAS - might be a mistake but do not know)
I generated the pydarm report from this measurement. I ended up changing "pro-spring" to False and regenerating.
Sat Oct 18 10:10:10 2025 INFO: Fill completed in 10min 6secs
TITLE: 10/18 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 3mph Gusts, 0mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.54 μm/s
QUICK SUMMARY:
IFO is in ENGAGE_ASC_FOR_FULL_IFO
Got in, H1 was locking after an auto initial alignment.
It seems that the wind has died down but that the microseism is still high without signs of coming down. POP and PWR signals look unstable due to microseism. Hoping to get locked today.
Just reached NLN - but worried that we will lose lock in the next 9 minutes due to the 1Hz ringup.
If Ryan S is correct about the lock acquisition time/thermalizing correlation with the lockloss-causing ringups, this lock definitely falls into the category for LL - we shall see. alog 87557
Yep - Lockloss after 4 minutes due to the ringup.
Still unable to get past DRMI despite good looking alignment. Made the decision to sit in IDLE. Wind is high but is lowered to around 30+ gusts though microseism is now over the 90th percentile and rising.
Wind is forecasted to come down this evening.