A plexi security cover was installed over the SPI Laser Chassis. Cover will be locked under normal operating conditions.

While working with Patrick today to deploy an updated IOC packaged in a container we found a problem resolving external hosts in DNS.

After some debugging it was traced down to DNS routing through a container health network that is an internal network.  The health network is an internal network as in not publically accessible, however marking it internal to the container system removed the egress route.  After I reconfigured the network to set internal=false it was able to properly lookup external hosts.

Notes for my future self.  When deploying containers using quadlets on Debian 13, the following is needed to reconfigure a podman network named NET (you must work through podman and systemd, and differing suffix/prefixes are added).

1. stop the systemd service:  systemctl stop NET-network

2. delete the podman network: podman network rm systemd-NET

3. reconfigure the NET.network file (in /etc/containers/systemd for system level networks)

4. systemctl daemon-reload

5. systemctl start systemd-NET

You can also do systemctl cat systemd-NET to verify that its parameters are correct.  Then podman network ls, podman network inspect to check on its full status.

Took some transfer functions of IM1, IM2, IM3, and IM4 now that HAM2 work is basically over. They all look good, even though a couple degrees of freedom (specifically L) don't have the best coherence due to not being able to drive too much in air without saturating

Settings
- ISI Locked
- DAMP OFF
- OPTICALIGN OFF

IM1
Data
/ligo/svncommon/SusSVN/sus/trunk/HAUX/H1/IM1/SAGM1/Data/2026-06-10_2200_H1SUSIM1_M1_WhiteNoise_{L,P,Y}_0p02to50Hz.xml
Results
/ligo/svncommon/SusSVN/sus/trunk/HAUX/H1/IM1/SAGM1/Results/2026-06-10_2200_H1SUSIM1_M1_ALL_TFs.pdf
r13029

IM2
Data
/ligo/svncommon/SusSVN/sus/trunk/HAUX/H1/IM2/SAGM1/Data/2026-06-10_2210_H1SUSIM2_M1_WhiteNoise_{L,P,Y}_0p02to50Hz.xml
Results
/ligo/svncommon/SusSVN/sus/trunk/HAUX/H1/IM2/Results/2026-06-10_2210_H1SUSIM2_M1_ALL_TFs.pdf
r13030

IM3
Data
/ligo/svncommon/SusSVN/sus/trunk/HAUX/H1/IM3/SAGM1/Data/2026-06-10_2210_H1SUSIM3_M1_WhiteNoise_{L,P,Y}_0p02to50Hz.xml
Results
/ligo/svncommon/SusSVN/sus/trunk/HAUX/H1/IM3/Results/2026-06-10_2210_H1SUSIM3_M1_ALL_TFs.pdf
r13031

IM4
Data
/ligo/svncommon/SusSVN/sus/trunk/HAUX/H1/IM4/SAGM1/Data/2026-06-10_2250_H1SUSIM4_M1_WhiteNoise_{L,P,Y}_0p02to50Hz.xml
Results
/ligo/svncommon/SusSVN/sus/trunk/HAUX/H1/IM4/Results/2026-06-10_2250_H1SUSIM4_M1_ALL_TFs.pdf
r13032

This was done on Tuesday, but is being recorded after the fact.

As per WP 13275 h1daqnds3 has been configured as a standalone edc/frame writer/nds1 for the H0:VAC channels.  This is in preperation for CDS upgrades in the next few months.  It will give the vacuum group a view of the H0:VAC channels that should not be interupted by CDS upgrades.

J. Freed, J. Kissel, J. Wright, T. Sadecki, TJ, Shaffer,

Continuing from 90558 (Notes are stored here).Today we completed all of the outside optical fiber install, Feedthrough install, as well as BnK Hammer of ISIK. 

We also had some trouble connecting to the picomotors through CDS but Fil and Co. seems to have fixed the issue.

In order we did:

• BnK Hammered the assembly to confirm secure to ISI and resonances are sufficiently high (~200Hz)
• Finished last PD and Pico bus cable connections to D6 feedthru
• Installed D4 feedthrough pannels
• Installed in chamber fibers but still need to be routed and respooled
• Checked and installed the fiber optic chain from PSL through SPI prep to the HAM 3 D4 feedthrough. This includes
  • SPI Prep mointor channel checks.
  • Optical network power budget (will be added to a separate alog).

TITLE: 06/10 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: MAINTENANCE
    Wind: 11mph Gusts, 5mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.12 μm/s 
QUICK SUMMARY:
SPI Is Shutters and Shutdown, they did not and are not going Laser Haz. So the LVEA remains in LASER SAFE / Bifuircated @ HAM7.
But a lot of work was done for SPI today. 
The cable for the TCS Pico drivers was changed out by fil for the SPI team.

Dave wanted to do a DAQ restart for CRS but ran into Model issues and postponed until tomorrow.
Jonathan is restarting some IOCs for Dave and Patrick's  work.

HAM2 TF were taken after Fil completed Ground Loop checks.
Alignment of Hepi was blocked by potentially metal on metal touching. Jim is contemplating his options.

Fist contact of ITMY completed today. Please see tear off in Control room. 

GRB-Short E64093 @ 23:46 UTC

And all the SUS in HAM2 have been set back to Aligned. 

Ryan, Jason, TJ, Mitch, Jim

Following yesterdays work, Jason and Ryan got new numbers for the alignment of BSC2 this morning, we overshot X by ~.75mm and still needed to rotate RZ by 900mrad. This afternoon, the five of us went to the chamber and made more moves, I think we are very close to done now.

However, I realized when we went back out, that we had collided the -X crossbeam into one of the spring caps on the -X/-Y corner of the chamber. We had just contacted this spring cap, which had already been ground down a tiny bit during the original install. This is on a non-critical part of the spring cap, so I think I will just grind the cap down a little bit more, so we have more like 1mm clearance instead of the .1mm clearance we have now. This will require putting hepi back fully on stops so I can take the load off both springs in this corner and remove the spring cap. This should hopefully be the last major surgery for alignment on the outside. We should be able to start attaching actuators tomorrow, late morning or after lunch.

Mitch, Jim

This morning Mitch and I went to HAM2 and unlocked the table to work on rebalancing the ISI. Table is rebalanced now, RX/RY locked unlocked shifts are around 10urad, RZ was a little bigger at ~15urad. I have not had a chance to do close out tfs.

After that was done, we tried to install the vertical L4Cs but were missing the hardware for the dog clamps. Found some class A stuff in the staging building that works, but when I went to install them to finish, I found one of the helicoils for the V3 L4C was missing. Rahul had some in the triples lab, so I will try to find time to install that tomorrow. The other 2 vertical L4Cs are done though, so the in vac portion of that install is mostly finished. 

Ibrahim, RyanS, Betsy, Corey, Anamaria

Today we pulled the forst contact fabric from ITMY. 

First we de-installed the jig around the cage, leaving only the fabric still attached to the HR of the test mass. We used the top gun to blow away particulate on the sides of the quad, the CP and in between as much as we could before pulling the FC. We note that there are still small, albeit sparse, visible "dot" particulate on these surfaces. These were observed at LLO as well, so nothing too surprising.

The first contact came off nicely, as an even layer. There were two spots at the edge, about 1-1.5 inch from 10 o'clock and 2 o'clock that left some residue so we painted those two little spots to remove it. We did it twice because the first time we left a bit of a line at the edge, but that was more petty than necessary. There was a small hair-like piece, 2mm long, that didn't come off with the top gun so we used a dry cotton swab to swipe it off.

We replaced the face EQ stops and the cage baffles. The quad is locked and the ACB is still wedged up. 

With Jeff in chamber, me outside with the B&K laptop, and Josh taking notes next to me, we did three measurements with three dofs on the ISIK breadboard in its current state without the shroud on. Results have two large peaks at 198Hz and 214Hz. The Y hit looks to have rung up the 214Hz much higher than the other dof hits, so much so that the 198Hz is barely visible. The 198Hz feature was seen in the MC2 scraper baffle B&K results for L1 back in 2017 (alog39750, see the last plot on the attached pdf). That said, I don't really see it for our results back then. 

Setup

Accelorometer axis lined up with IFO axis, hooray! The acc was placed between the M_M2 and R_B3 (photos - attachment 4, attachment 5).

Results

Jennie W. called to let me know that they need the Pico Motor Drivers turned back on.

We're checking the grounding of things in HAM2. IM4_TRANS QPD, ISS array QPD and all 8 ISS array PDs are fine.

IM4_TRANS and ISS array QPD:

Disconnected the DB25 cable from the transimpedance amp (ISC R4 slot 31) and measured the resistance between the pins and the chamber ground. (Ground potential for the chamber and the racks are significantly different, so we connected one cable directly to the chamber and measured the resistance between that cable and the pins.) 

All pins are isolated from the chamber. pin13 is tied to the shielding.

ISS array PDs:

Disconnected two DB25 cables from the second loop chassis (D1600229) in the PSL rack and measured the resistance between the pins and the chamber ground. Same caveat about chamber VS rack ground.

All pins are isolated from the chamber. Pin 13 is not connected to the shielding. This is fine, as this is a special cable made to convert four pairs of coax cables (total 8 coax) into DB25. Shielding of 8 coax is connected to pin14 through pin21 which are tied to the ground inside the second loop chassis. Pin13 is also connected to the ground inside the chassis. See D1600321.

Fil is done with SUS, some issues were found and he'll work with Rahul to try to fix them. He will also test picomotor grounding later.

[Begum, Camilla, Ryan S., Madi, Sheila]

Measurements taken on 2026-06-08 and 2026-06-09:
After the new OPO installation, beam profiles measured on HAM7 table (Sheila 90345) indicated that the OPO mode is different for the new OPO. This of course would both affect OMC mode matching as well as FC mode matching. The following measurements are beam q-parameter measurements measured on the FC path (green path in attached diagram), for beam upstream of ZM2 (p6,p7,p8,p11,p12) and downstream of ZM2 (p9,p10). The camera/profiler used is Phasics SID4 (MIT unit). 

Phasics camera is capable of giving us a beam waist and how far away that waist is from the camera position (- upstream of cam, + downstream of cam), however the fidelity of these values are dependent on where the camera is placed with respect to the waist: if it is too close to the focal plane (where the beam divergence is small), or if the beam is too large for the sensor the extracted values don't make sense. So, we have measured at least two positions with known distance from each other evaluate the fidelity q parameters obtained. 

Multiple measurements were taken at p10 point, varying ZM2 curvature. The strain gauge values are given in the table, 1.2 V and 6 V strain gauge correspond to 0 and 200 V pzt supply voltage to ZM2 psam. For points p6,7,8,9,10 the A:L2 lens was sitting in the "middle" position, both edges of the stage is lines up with its rail (will add photo here). Below table is from measurements taken on 06-08. The camera reports three numbers for each parameter, major, minor, radial. Major and minor do not necessarily line up with horizontal and vertical axes. The screenshots for each case report what the angle is. The .txt file for each data point also reports wx and wy for the near field beam, so we can potentially infer from there.

There are two readily available beam parameter tuning options we have for the FC path: the ZM2 curvature via psam, and the A:L2 lens via the translation stage it lives on. In the afternoon, we parked the Phasics camera on p11 and p12 positions (between p7 and p8) and recorded beam parameters for A:L2 lens on three positions (middle:0mm, -13mm: lens closer to ZM1 by 13mm, +17mm: lens further away from ZM1 by 17mm). Below table is from measurements taken on 06-09.

Raw data is in the attached .zip 

Summary

Whatever happened to IM1, Rahul did make it better again. Reasons for improvement is unknown but we proceeded with the alignment and we're mostly done.

There is a mystery scattering or maybe clipping somewhere close to the IFI output but not on the output baffle nor DKDP baffle. It could be a scatter from the CWP surface, or a ghost beam somewhere, or something else. It will take a LONG time to diagnose this, and quite likely this existed for a long time. I'm tempted to leave it at this time. But I'll try to take some more pictures.

There's also something weird about the 1st pico mirror PIT actuator for ISS array.

We'd still like to take pictures/measurements here and there on Tuesday.

Done: ASC REFL centering

Following the morning work (alog 90525), REFL ASC censors were centered using RM1 and RM2. About ~30% of DAC range was used for RM2 (RMs_happy_again.png). FYI, using flash peak, [P,Y]=[-0.003, 0.015] for REFL_A and [-0.020, 0.001] for REFL_B. (Doesn't matter how close these are to zero as far as they're within +-0.1 or so and the SUM is decent, but it feels better to be able to get close to zero.)

Done: ISS array centering

Then we looked at the ISS array and the QPD was not centered. A quick adjustment of the second pico that is closer to the array was all it needed (keita_ISS_happy1.png). [P, Y]=[-0.03, 0.05].

Done: IFO REFL baffle (HA13) adjustment

We looked at the IFO REFL baffle (HA13) in front of the HAM2-HAM3 septum window and it was too high even though it was not clipping, so we lowered it by a couple mm. Before: lower edge height = 105.5mm; upper edge = 206.8mm. After: lower edge = 103.6mm; upper edge = 204.5mm.

This baffle was already moved by a couple mm in +Y direction last week (because the beam was closer to +Y edge). See  IFOREFL_baffle_before_relocation.jpg and IFOREFL_baffle_after_relocation.jpg though it might be difficult to see the difference from this picture.

IFO REFL beam looked like IFOREFL_HA13_baffle_after.mov after the height adjustment.

Mystery flashes seen inside IFI output baffle aperture

We proceeded to check the IFI output baffle and I was bothered to find that something that looked like clipping was visible close to the left edge of the baffle using the IR camera. See IFI_OUT_clipped_720p.mov, this is a view from +Y door. But this was less frequent than the flashing itself. In a retrospect, this was probably the reflection from the PRM when the beam was swinging to the left of the video, but anyway we did various things:   

• We got suspicious about PRM somehow misaligned, checked it on the retroreflection check iris but it was fine in YAW (it was off in PIT so changed PIT offset from -1185 to -1115, not sure if it was PRM that changed or something else, but the important thing was that it wasn't off in YAW and that this is not something that I worry about now that we have a decent headroom for RM2 DAC).
• We closed the HAM3 door cover (which did quiet down the beam motion a lot) as well as the HAM2 -Y door cover. I used IR viewer and thought that nothing changed at the time. The bright thing didn't disappear after blocking the beam between PRM and IM4, again using the IR viewer, I thought.
• However, revieweing videos shot later, I haven't found anything to the left of the output baffle after the beam motion was reduced by closing unnecessary open door covers. But that revealed the next issue.

See IFI_out_another_view.mov, this is after the beam quieted down enough and after PRM PIT was changed. The bright thing at the left side of the baffle hole is not visible any more, but you can still see bright-ish scattering of some sort inside the baffle aperture which was there even when Rahul blocked the beam between PRM and IM4. IFI_out_another_view.jpg shows the same thing but with more useful exposure. This is concerning.

DKDP baffle behind the IFI output cwp baffle looked OK (IFI_DKDP_baffle.mp4). BTW, as was reported before, it looked to us that the IFI output baffle has an offset in -X+Y direction relative to DKDP. In the video, the beam on DKDP is slightly biased to the right on average because we tried to split the difference between two baffles.

We moved IM1 in YAW by +-200urad while observing the IFI output by IR viewer to see if there is a better beam position on IFI output. It seemed to me that actually we don't have much space here.

Look at IFI.png to see how the beam is routed through DKDP, output CWP and then passes by the parking beam dump pick-off.   

• If we give negative 200urad for IM1 YAW, the forward-going beam starts to interfere with the parking beam dump pick-off once in a while and the frosted barrel of that pick-off becomes bright. This is despite that the beam looks perfectly fine when IM1 is at the now-nominal position (see parkingBD_pickoff.mov, negative 200urad IM1 rotation would mean that the beam will be like 1mm to the right in this video).
• If we give positive 200urad for IM1 YAW, I thought that +X side of the IFI output cwp baffle starts to get brighter once in a while (my theory is that this is the same thing as shown in IFI_OUT_clipped_720p.mov where the edge of the baffle clips the back-propagating beam when the beam moves too much).

We'll be better once we're in vacuum because things will be quieter and the MC alignment will be better, so no beam motion and no HOM transmission, but I have to say that the clearance here looks to be unnecessarily narrow. I will NOT touch IFI itself so the only option for mitigation will be to move the parking BD pickoff, but it will be tedious to align that pickoff to steer the beam into the beam dump on top of HAM2. Given the limited time available I'll leave it as is.

We don't know what this scattering is, maybe it's the AR reflection of CWP or DKDP hitting something, maybe it's the surface scatter of CWP. I'll try to take the video from the back of the IFI output beamdump/CWP using a big inspection mirror.

Done: IM4 TRANS centering.

Rahul used pico mirror to roughly center IM4 TRANS while I was monitoring individual segments. IM4TRANS_ROUGHLY_BALANCED.png

Done: IM4 baffle (HA12) moved

As planned. The beam originally was offset in +X direction (IM4_HA12_before.jpeg shows the original location, IM4_baffle_HA12_before.mov shows the beam position), IM4 baffle was moved a bit in -X direction (IM4_HA12_after.jpg, IM4_baffle_HA12_after.mov).

Done but not really: Picturing the picos, one concern for the first ISS pico actuator.

We tried to diagnose the scattering or clipping or whatever that is visible inside the IFI output baffle aperture (alog 90536, especiall this video from that alog). It's not subtle, is always there even when the beam is blocked between PRM and IM4, and it's not just once in a while, it looks to be as frequent as strong flashes from IMC.

This is not the clipping of the forward propagating beam on the baffle as the beam height is pretty good (beamheight_dkdp_baffle.mp4) and YAW is also OK on dkdp baffle as well as IFI output baffle (dkdp_baffle_yaw.mp4, IFI_output_yaw.mp4).

We took a video of the back (i.e. -Y) side of the IFI output baffle through the output CWP by inserting a big dentist mirror between DKDP baffle and CWP and shooting from the +Y side. Video will be posted later (the raw video from IR sensitive camera exceeds 15Mb limit of alog and I don't have a good editor on my laptop).

Anyway, it seems like something is maybe hitting the bottom edge of the baffle from the back, Disha and Rahul think that there's something at the top too but I'm not sure.

We don't know what it is but we've done everything that could be done in situ without resorting to drastic measures (like temporarily removing all suspension baffles that block our view, which takes time despite that we don't know if that helps or not, or moving IFI to the lab which I won't do at this point in time). Since I'm pretty sure that this is NOT the clipping of the main beam as was noted above, my recommendation is to give it up at this point and move on, knowing that this thing does exist.

Together with alog 90536, we're done with HAM1/2/3 alignment today. Let's hope that the IM1 mystery motion won't return.

Fil already started ground check of suspensions, we'll do the ISS unit and the QPDs in HAM2/3 tomorrow.

The EndX BRS was stuck in a damping loop (I'm assuming caused by the power outage). Usually when this happens increasing the damping thresholds temperately fixes the issue, so we went ahead and did that.
It seems to only be effecting the ETMX BRS, so we left the ETMY one alone
Jim and I increased the damping thresholds from:
H1:ISI-GND_BRS_ETMX_HIGHTHRESHOLD: 2000-->4000
H1:ISI-GND_BRS_ETMX_LOWTHRESHOLD: 800-->2000

It also looks like the ETMX BRS drifted out of range (maybe due to the heater losing power and not returning to the original level?) so I've increased the voltage going to the heating plates and will check back in tomorrow to see if it's been restored

[Sheila, Karmeng]

Today we checked and managed to reduce some of the saturation on ZM4, and offload it onto ZM6. The changes were undone for now.

We briefly did the power budget check, but the power measured at the output of the SFI1 is fluctuating (between 0.79mW to 1.6mW) when the input to SFI1 is at 0.79mW. The power is stable down the propagation (after AP1 and SFI2), unsure what causes the fluctuation. Will continue to look into this tomorrow.

We also did an OMC scan, the pink trace is the scan when ZM4 is in its original setting (YAW: 1779.5), and the red trace is correspond to ZM4 misalignment (YAW: 1769.5).