Jennie W, Keita K, Betsy W, Camilla C

At the end of the day (for the day's activities to get to this point see Sheila's alog #89701) we were in chamber trying to see PRMI flashes in the POP in-vac path on -Y side of HAM1. We tried to lock JAC at 20W input so the flashses would be clearer on the card but it turns out anything over about 5W input puts the trigger PD above its threshold so the shutter in front of the JAC REFL PD and JAC WFS QPDS closes. Keita had Camill and I measure the power and for 2W input we get 5-6mW on this REFL PD and around 3mW on each QPD. This means that we shouldn't try and raise the trigger threshold (currently at 1.2V) as at 20W we will have 50mW on the REFL PD. I thought we had more of a margin than this.

What this means is we want to lock the JAC every time at 2W and then scale the gain in lock so only a low level of power goes to the REFL PD.

I copied some code from the ISC_library to do this. The new function is the state decorator JAC_pwr_adjust_function. It should scale the gain in JAC-L_SERVO by the requested input power as measured at IMC-PWR_IN_OUTMON while the JAC-LOCK guardian is in the 'LOCKED' state. It compiles now but I haven't tested it on the IFO yet as we left IMC and JAC in down, the input power at 100mW and the lightpipe closed at the end of the day.

This morning I noticed that the oil temp for the Kobelco was high at ~150F (nominal is around 110-115F). Looking at the sight glass for the oil level, it was high compared to it's usual level during operation. (see attached, off line is when compressor is off, RUN is the level during operation)

Gerardo and I confirmed the oil pump was running and the oil line pressure was ok through the control panel. We then opened the ball valve for the coolant line which goes to the oil cooler. This very quickly dropped the oil temp back to nominal, and there was some tuning done to keep it at ~115F.

Gerardo then contacted the rep who replaced the oil pump on this unit a couple of weeks ago, and confirmed it was just a matter of adding more coolant flow to the oil cooler. The oil level at the sight glass then returned to it's nominal level. 

No issues since, but we will continue to monitor.

Sheila, Camilla, Sophie

Following Sheila's finding last week that the nominal ZM2 PSAMS settings of 3.15 V is giving us an oval beam, 89675, we set ZM2 PSAMs to 4.5V and immediately got better flashes in green and IR on FCES. Moved ZM2 to increase flashes to be  ~55 on green PD C and occasionally up to 1.2 on IR PD D with CLF injected.

Sheila could lock green FC for ~10 seconds. With the SEED injected it did not seem to be co-resonant and she needed to turn off SUS feedback to help green FC locking. 

We then locked FC servo (wouldn't stay locked for long, but was able to move FC1, FC2 and ZM2 PSAMS to maximize the maximum locked values. Got to 58 on PD FC_TRANS_C for 4.8V or 4.9V. Leaving at 4.85V. Could further increase to 66 on PD FC_TRANS_C iteratively with FC1 and FC2, see attached. Locked for ~20 s max. 

To get light (100e-6) on SQZT7 OPO_IR PD, we needed to move ZM3 +100urad in PIT on the sliders. 

I then thought that we could go to the location we have SQZT7 IR light and light on the HAM7 WFS and movve ZM3 towards the place where we have known FC flashes and bring back the alignment on the HAM7WFS with ZM2 and FC1. I did this but it maybe unsurprisingly didn't;t work. In hindsight maybe I could have used a different combination of mirrors. 

To get light (100e-6) on SQZT7 OPO_IR PD, still needed to move ZM3 +100urad in PIT on the sliders. At which point there is no flashes on FCES green or IR. to get max light on the SQZT7 PD (0.0018) I had to change ZM3 from P,Y (-474, -367) for FC flashes to  (-334, -309) for SQZT7 light OR move ZM2 from P,Y (429,132) for FC flashes to  (-747,1) for SQZT7 light and centered WFs (not inc. WFS A PIT). In going from SQZT7 light to towards FC light, the beam on HAM7 WFS moves positive in PITCH and positive in YAW. This corresponds to 

I changed  H1:SQZ-RLF_QPD_A_SEG_3_VOLTS  from 1.31087 to 10 to stop this broken WFS A QPD segment from effecting the position on the WFs so much.  Didn't make much of a difference though.

TITLE: 03/30 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:

IFO is in IDLE for PLANNED MAINTENANCE

HAM 1 team has been working on JAC from the bifurcated HAM1 area and the control room throughout the day. SPI and BHSS work continued in the optics lab.

IX has been a bit finicky and tripped the SW WDs. They didn't seem like they were untripping and we were seeing the counts get worse with the damping loops. Additionally, the rocker switch death flashed a few times. Jim fixed this by turning off SUS damping, then letting the ISI damp until counts visibly went down before turning on damping everywhere.

BSC2 platform work and HAM3 cabling continued.

LOG:

Jenne Driggers, Sheila, Keita, Camilla, Jennie Wright, Rahul

We are searching for PRX flashes to use for the POP path work in HAM1.  

We are using a DRMI locked time from March 14th (1:30-2 UTC) as a reference.  Since that time HAM2 hepi has been locked, causing a +3.7urad shift in RZ, which means that PR3 and PRM osems need to be -3.7urad yawed compared to how they where before HEPI was locked to reproduce the alignment (this shift is small compared to the misalignments that we are looking for).  

While trying to restore to this reference time, we see that restoring ITMX sliders restults in optical levers similar to the reference time, and PRM sliders results in PRM osems similar to the reference times.  However, restoring PR3 sliders to the reference time gives top mass osem pitch -20 urad in pitch, and PR2 sliders restored gives a +30 urad shift according to the top mass osems.  

HAM2 CPS RY shows a +1.3 urad shift at the same time as the PR3 osem shift show -24urad (these are opposite directions), HEPI shows -1.5urad RY, at 11 am pacific time Friday, there is no change in the DAC drive at this time.  

PR2's shift seems to have happened right after the DACKill from Friday.  Ibrahim and Oli are running top mass to top mass TFs for health checks on both of those.  

Keita walked aligments to get PRX flashes back.  In the end, PRM and ITMX are back to where they were when DRMI was locked March 14th, as well as PR3 yaw.  PR3 pitch osem is back to where it was on the 14th, but the slider is +11urad.  PR2 pitch slider is -47urad, osem says -29 urad, yaw +45 slider, +55 urad osems.  

We dedicded it was time to move on with the in chamber work, because while these alignment shifts are strange, they probably can't explain the misalingment between the in air and the in vacuum pop paths.  

Commissioners wanted health checks run for PR3 and PR2 to check for any suspension issues. I ran TFs for PR3 and Ibrahim ran them for PR2. Results for both suspensions look good. Results for PR3 are below, and then Ibrahim will be commenting on the info for the PR2 measurements.

Settings:
- PR3 in HEALTH_CHECK
- DAMP OFF (including estimator damping)

Data:
/ligo/svncommon/SusSVN/sus/trunk/HLTS/PR3/SAGM1/Data/2026-03-30_2115_H1SUSPR3_M1_WhiteNoise_{L,T,V,R,P,Y}_0p02to50Hz.xml
r12986
Results:
/ligo/svncommon/SusSVN/sus/trunk/HLTS/PR3/SAGM1/Results/2026-03-30_2115_H1SUSPR3_M1_ALL_TFs.pdf
/ligo/svncommon/SusSVN/sus/trunk/HLTS/PR3/SAGM1/Results/2026-03-30_2115_H1SUSPR3_M1.mat
r12987

Sheila, Rahul

This morning I took top mass osem spectra for both PR2 and PR3 suspension and they looks healthy (the noise level for all bosems are similar and the magnitude is to below 10^-4  above 10Hz - un-calibrated) - plot attached below. There is a 15Hz peak seen on PR3, which is also seen (in both PR2 and PR3) if we go back in time (7 days) compare the spectra results. 

I also looked at the medm screen of both the suspensions (input filters, flag position, damping loops and coil driver settings) and trended bosem channels and did not find anything unusual. 

Summary: A thermal lens resulting from using 2 Fused Silica windows as attenuators in the CHETA system should not effect the profiled beamsize. 

We are considering using 2 Fused Silica windows at 45 degrees as absorping attenuators at the outputs of the QCL during beam profiling to stop back reflections which we believe are currently damaging the units. We plan on using 2 windows to prevent a beam displacement so the path doesnt have to be altered. During this process we require atleast 7mW on the thermal profiler to accurately profile the beam.

The attenuation through each 1mm window assuming using a loss factor of -28e6dB/km at 4.6um would be as follows:
Power after first window: 0.398W
Power after second window: 0.158W
Power reflected back through both windows: 0.0251W

This shows there will be non-neglible absorption so some quick modelling has been completed to demonstrate that this thermal lens would not have a significant effect on the system. 

I have used the finesse Hello Vinet implementation to model both the thermo-refrative and thermal expansion induced thermal lenses, assuming 2W of QCL power is absorbed in the substrate. This will be an over estimate as HV assumes that Pin ≈ Pout and that the absorbed power is much smaller than Pin. 
A radius of curvature was found from the HV OPD by completing an overlap interval with 2,0 and 0,2 modes.

Assuming worst case scenario of 2W of absorbed power and an beamsize of 300um (approximately the waist of a nominal QCL unit) there is an induced thermal lens of f =30.5273 m Rc = -0.0451 m. To determine the effect on the q-parameter of the beam I have assumed both glass windows act as a lenses with this focal length and use ABCD matrics determine the change in q.  This change in q is similar to the measurement error of these q factors and when propagated through to the ITM changes the beam size by less than 1%. This calculation for every unit is given in the table below using these yaml files.  

edit: fixed LLO numbers with updated parameters

[Tom, Jeff]

The SPI amplifier chassis' (S2500712, S2500713) were modified to increase their transimpedance gain, based upon testing in the optics lab from Jeff. Resistors R4 were changed to modify the gain, and capacitors C5 were changed to maintain circuit stability and bandwidth. Exact component changes summarised below:

S2500711

CH1: R4 = 1.5kohm, C5 = 2.2nF
CH2: R4 = 1.5kohm, C5 = 2.2nF
CH3: R4 = 1.5kohm, C5 = 2.2nF
CH4: R4 = 1.5kohm, C5 = 2.2nF

S2500712
CH1: R4 = 5kohm, C5 = 560pF
CH2: R4 = 5kohm, C5 = 560pF
CH3: R4 = 3.3kohm, C5 = 1nF
CH4: R4 = 3.3kohm, C5 = 1nF

CH5: R4 = 3.3kohm, C5 = 1nF
CH6: R4 = 3.3kohm, C5 = 1nF
CH7: R4 = 3.3kohm, C5 = 1nF
CH8: R4 = 3.3kohm, C5 = 1nF

S2500713
CH1: R4 = 54kohm, C5 = 56pF
CH2: R4 = 54kohm, C5 = 56pF

Closes FAMIS39860, last checked in alog89375

Everything looks as it did during the last check, except MR_FAN4_170_1 looks noisier than during the last check.

Closes FAMIS38815, last checked in alog89298

BRS_Y looks to be drifting down, over the past two months at least. The aux channels look just as they did before.

Mon Mar 30 10:08:08 2026 INFO: Fill completed in 8min 5secs

Attached to this alog are the Omicron glitch rate compariosns between O4a, O4b, and O4c. I am posting just for the record, but this was also presented at the LVK in Pisa (see here). For the comparisons, I used roughly about ~3240 hours of observing time (denoted by the H1:DMT-ANALYSIS_READY:1 flag). The exact GPS times used for the analysis were:

O4a: 1372611618 - 1389484818

O4b: 1397692818 - 1422118818

O4c: 1422118818 - 1447502418

The first attached plot shows the glitch rate across each observing period, which includes glitches with an SNR > 7.5, and frequency between 10 Hz - 1024 Hz. The rate was the highest in O4a, at around ~38 glitches per hour. The subsequent glitch rates for O4b/c were lower and similar levels, coming in at around ~11 glitcher per hour and ~10 glitches per hour. In O4a, the glitch rate was high due to increased non-stationary noise from ~10 Hz - 50 Hz (see alogs 71005 & 71092). The following two plots show the glitch rates as a function of SNR and frequency. Most glitches had an SNR below 50, and frequency below 50 Hz.

[Tom, Sophie, Ibrahim, Betsy]

Thursday, Friday and Saturday of last week we assembled a batch of 4 QOSEM In-Vac cables (D2500311) for use at LLO on the BBSS. All cables have passed electrical testing.

On Sunday, Betsy cleaned and began an airbake on the cables, and they have now begun there vacuum bake, which should finish Wednesday evening.

I've found that the pico mount for 50:50 BS on the REFL WFS sled in front of ASC REFL_A was loose and rotated counter-clockwise seen from the top by a huge amount (1st attachment, orange arrows show the direction of rotation). Our guess is that the BS mount was bumped when we were leaning into HAM1 from -Y door to work on the JAC output periscope. In general, it's hard to rotate the mount clockwise seen from the top even if the screw is not super tight (because the screw tends to be tightened), but it's easier to go counter-clockwise.

When this was found, the beam was hitting the +X-Y edge of the mirror, there was no clear reflection beam found so no beam on WFSA, but somehow the ugly transmission beam with lots of diffraction patterns was making it to WFSB.

We reverted the RM1 and RM2 bias sliders back to O4 level (RM1 PIT=-180, YAW=-57, RM2 PIT=890, YAW=-530) and I confirmed that the centering on the 2" lens was good. WFSA mount was screwed down tight to the post.

RM1 bias was adjusted further (RM1 PIT=-190, YAW=263) to roughly center the beam on WFSB.

At this point I looked at the beam on WFSA and it was still off mostly in YAW but there was also a large PIT offset. These were taken care of by adjusting the picos I've just screwed down.

I enabled the REFL WFS centering which worked right away. LSC REFL diodes are receiving almost equal amount of light. We'll have to make sure that the beam is not clipped on LSC diodes. Anyway, I relieved the ASC using RM sliders and ended up these numbers: RM1 PIT=-192, YAW=274, RM2 PIT=910, YAW=-532.

We're getting <HIHI, MAJOR> alarm about H1:PEM-CS_DUST_LAB2_300NM_PCF, which I cannot trend using NDSCOPE, but I can plot H1:PEM-CS_DUST_LAB2_300NM_RAW and that number has been 30[V?] for the past 6 days.

I've silenced it but could somebody check?

F. Clara, J. Kissel, S. Koehlenbeck, J. Oberling, M. Pirello
D2400110

Today we picked up where we left off with the install of SPI into H1. 
Where we last left things, we'd installed a new SPI pick-off of ALS/SQZ beam in Apr 2025 (see ECR E2400083 and results in LHO aLOGs 83989, 83996, 83978). Back then, we had ended the work with the input to the fiber collimator within the PSL dumped.

With Jason and Sina in the PSL, we confirmed that the SPI path was still blocked. 

However, we also realized/remembered/confirmed that the entire ALS/SQZ/SPI path had 25% less power -- We've been running the PSL at lower power allocation downstream of the PMC since Sep 2025 to prevent issues we'd found with the currently installed EOM after a power outage triggered a dust monitor to spew out dust into the PSL (see that saga in e.g. LHO:87109 LHO:86966). They found the power at the SPI pick-off was 140 [mW] instead of the 188 [mW] we left in Apr 2025 (see LHO:83996).

(Using labels in the half-up-to-date drawing D1300348)
Jason and Sina rotated ALS-HWP2 upstream of ALSPBS01 to restore the nominal 50 [mW] into the ALS/SQZ pick-off and ~200 [mW] (190 [mW] measured). This means there's ~50 [mW] less out to ALS / ISCT1 than before today.

Then with the SPI pickoff still dumped, we installed a 30 [m] patch cord*** from the PSL optical table, out the mouse hole between the +X wall of the PSL enclosure and HAM1, then up running along the upper racks to waterfall down at SUS-H2. The fiber sits within the typical orange tubing. Per D2400110, this is SPI_PSL_001, and it's labeled as such on both ends.

After install, I connected the SUS-R2 end to a Thorlabs S121C power meter with S120-APC2 fiber adapter. 
With this installed (making the system laser safe at SUS-R2 end), Jason/Sina unblocked the SPI pickoff input. 
With 190 [mW] in, we measure 187 [mW] out on the other end. 98% transmission, pretty excellent. Almost unbelievably excellent but we weren't rigorous with our uncertainty and systematics.

Happy with this result, we then blocked the SPI path again, and re-capped the SUS-R2 end for final dressing in the racks.
We'll unblock again when we're read to connect it to the Laser Prep Chassis.

***Patch cord details:
Manufacturer DIAMOND
DIAMOND Part Number: ENS/1094388
Customer Part Number: 9711228
Patchcord SM L=30 PM
2xFC 2mm APC (i.e. 2mm narrow key FC/APC on both ends)
tran 6,6/125/245 PAND 980nm