Last week, Sheila recommeded that we switch the LASER_PWR guardian node to use the IM4 trans power channel to do the power scaling for the IMC (alog87545). After speaking with her today, we decided to make this change, but wait on the associated ASC/LSC gain changes. So, our kappa c will be off by 2 or 3 % until we update these gains. The plan would be to updated them tomorrow during maintenance recovery.
Following the success of Ryan Short's lock with these new gains (alog87573), we updated lscparams.py with CSOFT P = 30 and INP P = -2.
We reloaded all nodes that use lscparams.py, and checked Dave's GRD CFC screen to see the affected nodes.
Mon Oct 20 10:09:15 2025 INFO: Fill completed in 9min 11secs
Lockloss after 16 hrs locked. Looks to be microseism caused.
TITLE: 10/20 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 4mph Gusts, 3mph 3min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.45 μm/s
QUICK SUMMARY:
IFO is in NLN and OBSERVING as of 00:58 UTC (14 hours)
After wind finally calmed down last night, IFO was able to lock and is still locked!
Plan for today is commissioning from 8:30 to 11:30 AM PT.
TITLE: 10/20 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: After H1 relocked at the start of my shift, I dealt with a brief ASC issue, then started observing. Been a quiet evening otherwise and the range has steadily been coming up over the past few hours. H1 has now been locked for 4.5 hours.
LOG:
H1 is back to observing as of 00:58 UTC after a long day of tussling with the environment, which still isn't great, but the wind has calmed down a bit.
After assisting DRMI locking by adjusting PRM, locking went automatically. Once we reached NLN, I noticed the 1 Hz ASC ringup starting. The most significant culprits I saw were CSOFT_P and INP1_P, so I adjusted their gains from 25 to 30 and -1 to -2, respectively. This seemed to stave off the rising ringup, and after about 15 minutes, I noted these loops and the PRG finally start to calm down. I returned the loop gains to their nominal and started observing. I can't say for sure if this works as a long-term fix for this ringup, but at least we didn't lose lock this time. I still see DHARD_P oscillating slightly at 1 Hz 10 minutes later, but it seems small at this point.
TITLE: 10/19 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Wind
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:
IFO is LOCKING at ACQUIRE_DRMI_1F
Bad day for the IFO due to the environment.
To start, the wind has not gone under 30Mph for the entire day, and has been over 35mph for the majority. It looks to be dying down now and will continue to do so this evening. Midshift report (alog 87565)
The microseism was sitting just at the 90th percentile point until 3 hrs ago when it started increasing.
We did get to NLN once but due to the known 1Hz CSOFT_P ringup (which previously was managed by increasing gain) but 4 minutes later, we had a Lockloss. (Lockloss alog 87571) This is an ongoing issue where it appears that long lock acquisitions experience the 1Hz ringup more violently than short acquisitions. Due to the microseism and wind, this has been the case for many of the recent locks. Ryan S has an alog about this correlation with a hunch that it is related to IFO thermalization (alog 87557)
In the next lock, since this is bound to happen again, we can either sit at MAX_POWER or increase the gain further (from 25 to 30) and see if either works. The former would test out the hypothesis in Ryan S's alog and the latter would just up the fix from before.
14:30 UTC - shift start
14:54 UTC - TRANSITION_FROM_ETMX Lockloss
16:42 UTC - Initial Alignment - Fully Auto
17:12 UTC - IFO in IDLE due to WIND
18:36 - Lock Acquisition Attempt
19:35 - Succesful Lock Start
20:24 - NLN Reached (under 1 hr, fully auto)
20:28 - Lockloss due to 1Hz Ringup
22:07 UTC - IFO in IDLE due to MICROSEISM
22:54 UTC - Lock Acquisition Attempt
23:30 UTC - in DRMI, end of shift
LOG:
None
TITLE: 10/19 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Wind
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 27mph Gusts, 16mph 3min avg
Primary useism: 0.06 μm/s
Secondary useism: 0.52 μm/s
QUICK SUMMARY: H1 has been down most of the day due to high winds and microseism. I think the forecast says it'll calm down a bit this evening, but that remains to be seen. I'll have H1 keep trying for a bit, but may move it back to IDLE if unsuccessful.
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.
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.
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).
Got called at 3:30AM due to DRMI lock unable to lock. Flashes seem bad since the earthquake and there hasn't been an initial alignment for some reason. Set IFO to initially align then turned the manager back on.
Looking further into this, it did run initial alignment before it called Ibrahim, but there were two DRMI lock losses and one regular lock loss before it called. Looks like there was a large nearby earthquake that caused the lock loss and also perhaps didn't help the initial alignment, causing Ibrahim to have to run a second one. I'll need to look further into that.
[Joan-Rene Merou, Alicia Calafat, Anamaria Effler, Sheila Dwyer, Robert Schofield, Jenne Driggers] We have looked at the near-30 Hz and near-100 Hz combs (Detchar issue 340) in all of LHO Fscan channels (Full 148 channels list can be found in O4_H1_Fscan_ch_info.yml) to find witnesses and also channels where the amplitude and coherence change at the same dates as DARM. The list of combs is the following one:
| spacing (Hz) | offset (Hz) |
|---|---|
| 29.9695138888 | 0 |
| 99.99845486125 | 70.02888889 |
| 99.99845679 | 0 |
| 99.99846 | 29.9694 |
| 99.9984722225 | 89.90847222 |
| 99.99865 | 0 |
| 99.99845 | 10.08992 |
| 29.96952 | 520.17208 |
| 29.9695211 | 589.9007589 |
| 29.96951374 | 760.22840625 |
We list here the channels that do show most of these Combs. These same channels do show changes in coherence between July 1st and July 7th 2024, but do not show changes in the amplitude of the combs.
- H1_IMC-F_OUT_DQ
- H1_LSC-MCL_IN1_DQ
- H1_LSC-MICH_IN1_DQ
- H1_LSC-SRCL_IN1_DQ
- H1_PEM-CS_MAG_EBAY_LSCRACK_X_DQ
- H1_PEM-CS_MAG_EBAY_LSCRACK_Y_DQ
- H1_PEM-CS_MAG_EBAY_LSCRACK_Z_DQ
- H1_PEM-CS_MAG_LVEA_INPUTOPTICS_X_DQ
- H1_PEM-CS_MAG_LVEA_INPUTOPTICS_Y_DQ
- H1_PEM-CS_MAG_LVEA_INPUTOPTICS_Z_DQ
In most channels, the comb amplitude tends to get quite low after ~1500 Hz. The following sets of channels show differences between X, Y and Z:
- H1_PEM-CS_MAG_EBAY_SUSRACK_X_DQ (Higher amplitudes and towards higher frequencies)
- H1_PEM-CS_MAG_EBAY_SUSRACK_Y_DQ (Lower comb amplitudes)
- H1_PEM-CS_MAG_EBAY_SUSRACK_Y_DQ (Lower comb amplitudes)
Regarding CS_MAG_LVEA_OUTPUTOPTICS, these combs can be seen best in X, weaker in Y and almost non-existent in Z. (In CS_MAG_LVEA_INPUTOPTICS they look roughly the same height)
- H1_PEM-CS_MAG_LVEA_OUTPUTOPTICS_X_DQ (Strongest)
- H1_PEM-CS_MAG_LVEA_OUTPUTOPTICS_Y_DQ (Weaker lines)
- H1_PEM-CS_MAG_LVEA_OUTPUTOPTICS_Z_DQ (Almost no lines)
Same behavior at:
- H1_PEM-CS_MAG_LVEA_VERTEX_X_DQ (Strongest lines)
- H1_PEM-CS_MAG_LVEA_VERTEX_Y_DQ (Weaker lines)
- H1_PEM-CS_MAG_LVEA_VERTEX_Z_DQ (Almost no lines)
We can see that these combs mostly appear in the corner station. The combs do not appear in neither EX nor EY channels. However, comb 99.99865 Hz offset 0.000 appears in many EX, EY channels and does become more coherent after July 7th. However, it is very close to 100 Hz so it may be influenced by other round-number combs (?)
Looking at the 52 additional channels listed in LHO ADC channels list, we have found the following information: The combs appear in the following channels with high peaks and high coherence: - H1:PEM-CS_ADC_5_18_2K_OUT_DQ - H1:PEM-CS_ADC_5_21_2K_OUT_DQ - H1:PEM-CS_ADC_5_26_2K_OUT_DQ ! All combs appear here and with high peaks Some combs appear in the following channels with low peaks and low coherence: - H1:PEM-CS_ADC_5_22_2K_OUT_DQ - H1:PEM-CS_ADC_5_23_2K_OUT_DQ - H1:PEM-CS_ADC_5_24_2K_OUT_DQ The following channels do not show the peaks but show an increase in coherence from July 1st to July 7th 2024: - H1:PEM-CS_ADC_5_25_2K_OUT_DQ - H1:PEM-CS_ADC_5_27_2K_OUT_DQ - H1:PEM-CS_ADC_5_30_2K_OUT_DQ Only the 99.99 Hz offset 0 combs appear in the following channels: - H1:PEM-CS_ADC_4_27_2K_OUT_DQ - H1:PEM-CS_ADC_4_28_2K_OUT_DQ - H1:PEM-CS_ADC_5_19_2K_OUT_DQ - H1:PEM-CS_ADC_5_20_2K_OUT_DQ - H1:PEM-CS_ADC_5_31_2K_OUT_DQ In the arms, the following channels show coherence with only the 99.99 Hz offset 0 combs: - H1:PEM-EX_ADC_0_09_OUT_DQ - H1:PEM-EX_ADC_0_13_OUT_DQ - H1:PEM-EY_ADC_0_11_OUT_DQ - H1:PEM-EY_ADC_0_12_OUT_DQ - H1:PEM-EY_ADC_0_13_OUT_DQ - H1:PEM-EY_ADC_0_14_OUT_DQ The following channels show the unexpected behavior of showing the 99.99 Hz peak in July 1st with coherence, but it disappears on July 7th: - H1:PEM-EX_ADC_0_12_OUT_DQ In summary, after investigating the Fscan channel list and the additional channels. The ones that seem more promising as showing most of the lines with high coherence and high amplitude peaks are: - H1:PEM-CS_ADC_5_18_2K_OUT_DQ - H1:PEM-CS_ADC_5_21_2K_OUT_DQ - H1:PEM-CS_ADC_5_26_2K_OUT_DQ - H1:IMC-F_OUT_DQ - H1:LSC-MCL_IN1_DQ - H1:LSC-MICH_IN1_DQ - H1:PEM-CS_MAG_EBAY_LSCRACK_X_DQ - H1:PEM-CS_MAG_EBAY_LSCRACK_Y_DQ - H1:PEM-CS_MAG_EBAY_LSCRACK_Z_DQ - H1:PEM-CS_MAG_LVEA_INPUTOPTICS_X_DQ - H1:PEM-CS_MAG_LVEA_INPUTOPTICS_Y_DQ - H1:PEM-CS_MAG_LVEA_INPUTOPTICS_Z_DQ - H1:PEM-CS_MAG_EBAY_SUSRACK_X_DQ - H1:PEM-CS_MAG_LVEA_OUTPUTOPTICS_X_DQ Of these, channel H1:PEM-CS_ADC_5_26_2K_OUT_DQ appears to be the one with the highest amplitudes. The following figure illustrates its ASD and Coherence with DARM on the date of July 7, 2024, showing the peaks for the harmonics of the combs in this study. As can be seen in the ASD, the highest peaks are those in the list of the near-30 and near-100 Hz plots. The only peaks higher than these are the power mains at powers of 60 Hz. This channel shows all the combs listed. Most of these combs also show very high coherence with DARM.![]()
After determining in which channels the peaks appear present, we have studied the coincidence of changes in the comb heights versus the bias in the H1:SUS-ITMY_L3_ESDAMON_DC_OUT16. The following figure shows the coincidences between the changes in the relative amplitude of the first harmonic of each comb (sort of SNR) in DARM and the mean counts in H1:SUS-ITMY_L3_ESDAMON_DC_OUT16 across time. It can be seen that previously to May 2nd, the channel count was set to 60. Once it changed to around -223 after that date, the SNR of the peaks overall increased in a sudden way. Afterwards in June 13th when the count was reduced to 0, most peaks got a much lower SNR at the same time.
Tuesday Aug 19th I moved the dust monitor #10 from the bier garten area to up on the work platform on BSC2 (alog86444). Attached are some various plots of DM10 and DM6, the monitor next to HAM6 in the mega clean room (turned off atm).
Attached a zoomed-in plot of the DM10 channels just around the maintenance period on Tuesday, Aug 26th while craning was happening overhead. Dust counts certainly spiked mid-morning, which is likely when craning was happening as seen by ITMY STS BLRMs.
INP P gain accepted in SDF. CSOFT doesn't look to be monitored.