TITLE: 01/16 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY: Lots of work got done today. We are leaving the LVEA in LASER SAFE over the weekend
LOG:
To do items for today:
DONE Finish alignment out IOT2L viewport
DONE Move ZM4 to realign onto ZM5
DONE Lift BSC2 platform and remove PEM gold plate
DONE Roll up IOT2L to HAM2
DONE Cable up IOT2L
DONE Install bellows between HAM2 and IOT2L
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 17:16 | SAF | HAZARD | LVEA | n | LVEA is Laser HAZARD | 21:19 |
| 15:46 | FAC | Randy | LVEA | YES | Removing braces from BSC2 | 16:43 |
| 15:54 | FAC | Kim, Nellie | LVEA | YES | Tech clean | 17:03 |
| 16:15 | JAC | Masayuki | LVEA | YES | JAC alignment | 19:54 |
| 16:47 | Corey | LVEA | YES | Looking for bellows | 16:17 | |
| 17:02 | JAC | Jason | LVEA | YES | JAC alignment | 19:54 |
| 17:16 | JAC | Jennie | LVEA | YES | JAC alignment | 19:55 |
| 17:23 | SQZ | KarMeng | LVEA | YES | HAM7 work | 17:32 |
| 17:53 | JAC | Keita | LVEA | YES | JAC alignment | 19:06 |
| 18:37 | CDS | Jeff | LVEA | YES | Moving cables around | 19:16 |
| 18:43 | SQZ | Sheila, Rahul, KarMeng | LVEA | YES | SQZ alignment (Rahul out 20:02) | 21:03 |
| 20:48 | FAC | Randy | LVEA | n | Moving IOT2L | 22:18 |
| 20:49 | FAC | Marc, Corey | LVEA | n | Moving IOT2L (Corey out 22:08) | 22:32 |
| 20:50 | LASER | RyanC | LVEA | Y | Transitioning to LASER SAFE | 21:12 |
| 21:14 | CHETA | Matt, Sophie | JOAT Lab | n | Poking optics | 21:42 |
| 21:18 | SEI | Jim | LVEA | n | Locking BSC2 HEPI | 22:04 |
| 21:23 | FAC | Richard | LVEA | n | Ruining weekends | 21:30 |
| 22:35 | FAC | Tyler | LVEA | n | 23:05 | |
| 22:50 | ISC | Corey | LVEA | n | Installing IOT2L bellows | 23:43 |
| 22:58 | PEM | Robert | LVEA | n | BSC2 investigation | 00:58 |
| 23:23 | SQZ | Sheila, Robert | LVEA | n | Grabbing a cable | 00:08 |
| 23:27 | CHETA | Jennie | JOAT Lab | n | Putting parts away | 23:33 |
| 00:02 | Tyler, tour | LVEA | n | Tour | 01:02 | |
| 00:02 | FIT | Masayuki | YARM | n | Running | 00:30 |
[Jennie, Jason, Rahul, Keita, Masayuki]
We have observed the light coming out from the HAM2 after the MC1 reflection.
This is the summary report for the optics alignment in HAM1 after the JAC.
An iris was placed and centered on the output beam from the JAC before installing the L1 lens. The lens was then installed such that the beam remained centered on the iris.
JM2
This optic will need to be repositioned after the EOM is installed. Therefore, we placed it without fine adjustment for now. The angular alignment was done using an iris located at the position where the HR surface of JM3 will be. Notes for final installation:
The barrel must be cleaned before final installation.
A beam dump must be installed behind the mirror.
JM3
Although JM3 also needs to be swapped to tip-tilt, the beam reflected from JM3 serves as the alignment reference after the EOM. Therefore, we performed careful alignment. An iris was placed at the planned location of JAC_M3, and the beam was centered on it by adjusting JM3.
JAC_L2, JAC_L3
The two lenses were then installed. They were centered using the same iris that had been used for the JM3 alignment.
JAC_M3
The angle of the reflected beam from JAC_M3 is critical, as it determines the polarization mismatch caused by the periscope’s rotation. An iris was placed at the output beam hole, and the beam was aligned parallel to the hole line. Previous measurements confirm that the input beam axis to the IMC in HAM1 is parallel to the hole within ~1 mrad ([link]). Therefore, this alignment ensures that the polarization mismatch remains within acceptable limits.
Periscope (initial alignment attempts)
Initial alignment of the periscope was performed using the first iris (IR1) placed prior to installation.
Since the incoming beam was horizontal and parallel to the hole line, we expected the output beam to be rotated by exactly 90° and remain horizontal through the hole. After centering the beam on the iris by eye, we checked from the HAM2 viewport but did not observe the beam.
We attempted minor adjustments to the periscope, JM2, and JAC_M3. Some scattered light was eventually seen at the output periscope of the HAM2 IMC reflection path. However, IR camera footage from Keita showed that the focus did not match, and the light was deemed irrelevant. The detail can be found in Keita's alog.
Periscope (refined alignment)
On the following day, a second iris (IR2) was introduced to further constrain the horizontal alignment. This iris was placed approximately at the same height as IR1 and roughly aligned parallel to the hole line. The periscope was then re-aligned to pass through both irises.
From the POP septum window, we confirmed that the HAM2 periscope was visible and used it for alignment. Using an IR viewer, the beam was observed to hit the upper-left (10 o’clock) corner of the periscope structure. We switched to aligning JM2 and JAC_M3 using the top periscope mirror and IR1 as references (IR2 was removed at this point).
To identify the beam spot, we intentionally misaligned the pitch to make the beam hit the upper part of the periscope structure. To avoid blocking the beam, the iris was temporarily removed (its location was marked with three dog clamps; one clamp was slightly loose but the offset was minor, ~1 mm).
While keeping the pitch misaligned, yaw centering was performed using JAC_M3. Once centered visually, the iris was replaced, and JM2 was used to center the beam through it.
Fortunately, JM2 and the periscope top mirror are located at similar opical position, so the beam position remained nearly unchanged on the periscope mirror. This beam walking converged in two iterations.
The iris was removed again, and the beam was swept from top to bottom of the top periscope mirror using JAC_M3. The mirror was then centered using the midpoint of this motion. The iris was replaced, and pitch alignment was re-checked using JM2, again requiring just two iterations.
At this stage, some faint beam was observed using the viewer through the viewport. Although it wasn’t visible on a card, adjusting JAC_M3 slightly allowed us to confirm beam output from HAM2.
Final Checks
Finally, the IR1 centering was confirmed, and IR2 was placed near the periscope to act as a reference.
When checking the beam on JAC_L3, we found that it was offset by about 5 mm in the yaw direction. Further alignment is likely needed.
The beam spot on the periscope mirror is not perfectly centered, but it is close enough that no adjustment to the top mirror is deemed necessary.
Locked BSC2 HEPI this afternoon so Randy and I could try to get the PEM accel plates of the south end of the support tubes. Plan was to try to crane the south end of the work platform, but the platform didn't like being picked up from just one end and it looked like it was going to swing into the crossbeam. We set the platform back down and just pulled all of the screws out of the PEM plates. Turned out there was just enough room to get the blocked screws out, if you used pliers or fingers to back them out. Plates are off, platform is moved back into position, I think Randy was going to put the braces back on.
[Sheila, Rahul, Karmeng]
A continuation of yesterday's progress. The additional power observed yesterday was due to the green for FC lock. We measured 0.75mW exiting the OPO, 0.74mW after SFI1 and also on the SQZT7 homodyne detector.
Today we reduced the saturation on ZM4 by clearing the offset and physically rotate the ZM4, we recovered the alignment on OMC QPDs and SQZT7 irises.
We also aligned the beam back to the HAM7 QPD A and B, at ~100nW for both of them, will need to re-centre the beam once we're back to laser hazard.
Sheila, Karmeng, Rahul
This morning we physically moved ZM4 (since the sliders were saturating the DAQ output) in YAW to better align it with ZM5 and ZM6. More details (including health check results) will be posted later.
ZM4 is now dogged down to its new position.
Betsy, RyanC, Rahul
This week we glued prisms (primary - sapphire and secondary - metal) to the HRTS OM0 fused silica Optic (D2100495-V5-OM0-0001). The gluing measurement details are recorded in the DCC - google spreadsheet (T2600012), link given below,
https://caltech-my.sharepoint.com/:x:/g/personal/rmcrouch_caltech_edu/IQBWQ2S3pJX9TZYxfDaXsCvfAcJh-mrpHPS2JGNtku6Srcg
Attachment01 and attachment02 shows the prism-optic in the prism gluing jig.
Attachment03 and attachment04 shows the base for the Bosem magnet/flag glued to the AR side of the optic.
Attachment05 and attachment06 shows the two prisms glued on both the sides of the barrel of the optic. Notice that the arrow points to the HR surface and there is only one scribe line on the optic. While in the jig the arrow should be pointing down and on the right hand side of the gluing fixture (facing down).
The optic is now on its way to LLO and will be suspended in OM0 in HAM6 chamber.
M. Todd, C. Cahillane, K. Kawabe
In the last quarter of 2025, I was running a bunch of injections to the various ASC DOFs of the IMC, and looking at the response in the ISS --- this was all in an effort to explain the various features in the witnessed RIN from the out of loop diodes of the ISS array, or in other words create a noise budget for the ISS. In short, I believe we are IMC ASC limited below 5Hz while acheiving the shot noise limit from 20-1000Hz.
There are some peaks in the witnessed RIN that are not in the in-loop ASD, suggesting it is some noise being imposed by the loop itself. Further measurements will try and explore the source of some of these, particularly the ones around 18 and 24 Hz, with a suspicion of the IMs motion.
I wanted this alog to serve as a reference for where all the data lives for these measurements, as well as the code and noise budget plot. Note, the ISS_OUTER and INNER rin channels are saved with quick_psd, but the gpstimes are recorded in the table below.
For the projections, a transfer function is measured during the excitation of the measured DOF --- looking at the TF from the best witness channel to the ISS OUTER, and then that transfer function is applied to the witness during the quiet time when there is no excitation.
| Measurement | GPS Time | File Location | Notes |
|---|---|---|---|
| ISS OUTER RIN |
1446823543
|
/ligo/home/matthewrichard.todd/Projects/imc_injections/dtt_injections/quiet_data_iss_outer_rin.txt | Taken with quick_psd and then saved |
| ISS INNER RIN | 1446823543 | /ligo/home/matthewrichard.todd/Projects/imc_injections/dtt_injections/quiet_data_iss_inner_rin.txt | Taken with quick_psd and then saved |
| IMC PZT Pitch projection | 1446912665 | /ligo/home/matthewrichard.todd/Projects/imc_injections/dtt_injections/pzt_pit_injection_1_15_Hz.xml |
Injection Band: 1-15Hz Best Witness: WFS_A_PIT |
| IMC PZT Pitch projection | 1445107725 | /ligo/home/matthewrichard.todd/Projects/imc_injections/dtt_injections/pzt_pit_injection_15_1000_Hz.xml |
Injection Band: 15-1000Hz Best Witness: WFS_A_PIT |
| IMC PZT Yaw projection | 1446900349 | /ligo/home/matthewrichard.todd/Projects/imc_injections/dtt_injections/pzt_yaw_injection_1_15_Hz.xml |
Injection Band: 1-15Hz Best Witness: WFS_A_YAW |
| IMC PZT Yaw projection | 1445108720 | /ligo/home/matthewrichard.todd/Projects/imc_injections/dtt_injections/pzt_yaw_injection_15_1000_Hz.xml |
Injection Band: 15-1000Hz Best Witness: WFS_A_YAW |
|
IMC DOF 1 Pitch projection |
1445698453 | /ligo/home/matthewrichard.todd/Projects/imc_injections/dtt_injections/imc_dof_1_pit_injection_1_4_Hz.xml |
Injection Band: 1-4Hz Coherent Band: 0.2-5Hz Best Witness: WFS_B_PIT |
|
IMC DOF 1 Yaw projection |
1445698453 | /ligo/home/matthewrichard.todd/Projects/imc_injections/dtt_injections/imc_dof_1_yaw_injection_1_4_Hz.xml |
Injection Band: 1-4Hz Coherent Band: 0.2-5Hz Best Witness: WFS_B_YAW |
|
IMC DOF 2 Pitch projection |
1445698453 | /ligo/home/matthewrichard.todd/Projects/imc_injections/dtt_injections/imc_dof_2_pit_injection_1_4_Hz.xml |
Injection Band: 1-4Hz Coherent Band: 0.2-4Hz Best Witness: MC2_TRANS_PIT |
|
IMC DOF 2 Yaw projection |
1446303221 | /ligo/home/matthewrichard.todd/Projects/imc_injections/dtt_injections/imc_dof_2_yaw_injection_1_4_Hz.xml |
Injection Band: 1-4Hz Coherent Band: 0.2-5Hz Best Witness: WFS_A_YAW |
Fri Jan 16 10:12:08 2026 INFO: Fill completed in 12min 4secs
Jeff, Oli, Jonathan, EJ, Dave:
h1susaux[b13, b2h34] new models were installed, b13 for cosmetic simulink changes, h2b34 restored missing channels and needed a DAQ restart.
We did two rounds of DAQ restarts.
09:04 both legs restarted for susauxb2h34 changes. No problems.
09:56 GDS1 restart to add the three BS_M1_NOISEMON channels back into GDS. Followed by full 0-leg restart to do the same with GDS0. No problems.
Catching up on the DAC upgrades / CDS work earlier this week I updated some thresholds on the SUS SATMON screen. There were quite a few suspensions and stages to do this time so I decided to generate some code to string match and update the values for me so I don't have to spend the time copy pasting.
The script is called "satmon_update_sats_dac_upgrade.py" and its located in the same directory as SATMON. If you open it in an editor and scroll to the bottom you'll see how to use it. Here's an example line for updating PR2_M3 from a 18 to a 20 bit DAC card.
Jeff, Oli, Jonathan, EJ, Erik, Dave:
On Thursday 15Jan2026 we installed Jeff and Oli's new models for:
h1susmc2, h1suspr2, h1sussr2, h1susbs
h1susitmx, h1susitmy, h1susitmpi
h1susauxb13, h1susauxb2h34
Several DAQ restarts were needed for these installs. The first DAQ restart also had an EDC restart to use updated SDF and CDSMON ini files incorporating the new model names.
The models in h1susb2h34 had two sets of restarts. After the first EJ found some IPC issues which he fixed by editing H1.ipc. All the models were then restarts a second time.
In the first block of restarts h1suspr2 had two starts, the second to fix a 18bit-DAC to 20bit-DAC change.
We had three instances of new models removing channels from the DAQ which were being sent to GDS via the broadcaster. Jonathan removed these from the broadcaster list we are working today on whether they should be added back, perhaps with a different name.
Here are the models and GDS channel lists:
h1susitmx (4):
H1:FEC-29_DAC_OVERFLOW_ACC_2_[4-7]
h1susitmy (4):
H1:FEC-30_DAC_OVERFLOW_ACC_2_[4-7]
h1susauxb2h34 (3):
H1:SUS-BS_M1_NOISEMON_F[1-3]_OUT_DQ
As Jonathan details in his alog, after the restart of h1susauxb2h34 the DAQ was running with duplicate BS-AUX channels which had been added to h1susauxb2h34 and were still running on h1susauxb13 (a temporary model I built on Wed). This was resolved when the new h1susauxb13 was installed.
Restart Log
Thu15Jan2026
LOC TIME HOSTNAME MODEL/REBOOT
12:32:41 h1susb2h34 h1susmc2 <<< First set of h1susb2h34 restarts
12:33:07 h1susb2h34 h1suspr2
12:36:07 h1susb2h34 h1sussr2
12:36:25 h1susb2h34 h1susbs
12:45:57 h1susb2h34 h1suspr2 <<< Fix 18bit-DAC issue
13:07:10 h1susb2h34 h1susmc2 <<< Second set of h1susb2h34 restarts with fixed IPC
13:07:29 h1susb2h34 h1suspr2
13:07:54 h1susb2h34 h1sussr2
13:08:12 h1susb2h34 h1susbs
13:32:14 h1daqdc1 [DAQ] <<< DAQ 1-leg, new models and new EDC
13:32:25 h1daqfw1 [DAQ]
13:32:26 h1daqtw1 [DAQ]
13:32:29 h1daqnds1 [DAQ]
13:32:35 h1daqgds1 [DAQ]
13:32:51 h1susauxh56 h1edc[DAQ] <<< EDC restart
13:34:56 h1daqgds1 [DAQ] <<< GDS1 needed second restart
13:36:31 h1daqgds0 [DAQ] <<< DAQ 0-leg
13:36:39 h1daqfw0 [DAQ]
13:36:39 h1daqtw0 [DAQ]
13:36:40 h1daqnds0 [DAQ]
14:50:28 h1susb13 h1susitmx <<< New h1susb13 models
14:50:52 h1susb13 h1susitmy
14:51:13 h1susb13 h1susitmpi
14:57:31 h1daqdc1 [DAQ] <<< DAQ 1-leg restart for new models
14:57:41 h1daqfw1 [DAQ]
14:57:41 h1daqtw1 [DAQ]
14:57:43 h1daqnds1 [DAQ]
15:04:22 h1daqfw1 [DAQ] <<< FW1 spontaneous restart
15:07:00 h1daqgds1 [DAQ] <<< GDS1 manual start after missing channels removed
15:09:02 h1daqfw1 [DAQ] <<< 2nd FW1 spontaneous restart
15:17:02 h1daqgds0 [DAQ] <<< 0-leg restart
15:17:09 h1daqfw0 [DAQ]
15:17:09 h1daqtw0 [DAQ]
15:17:10 h1daqnds0 [DAQ]
15:50:54 h1susauxb2h34 h1susauxb2h34 <<< new model (unknowingly adding duplicate chans)
15:54:02 h1daqdc1 [DAQ] <<< DAQ restart for model change, 1-leg
15:54:11 h1daqfw1 [DAQ]
15:54:11 h1daqtw1 [DAQ]
15:54:15 h1daqnds1 [DAQ]
15:54:20 h1daqgds1 [DAQ]
16:02:39 h1daqgds0 [DAQ] <<< 0-leg
16:02:45 h1daqfw0 [DAQ]
16:02:46 h1daqnds0 [DAQ]
16:02:46 h1daqtw0 [DAQ] <<< At this point FW2 is unstable due to duplicate channels, not sure why 0-leg & 1-leg are running at this point
17:23:09 h1susauxb13 h1susauxb13 <<< new model (removed duplicate BS chans)
17:23:53 h1daqdc1 [DAQ] <<< 1-leg
17:24:03 h1daqfw1 [DAQ]
17:24:03 h1daqtw1 [DAQ]
17:24:07 h1daqnds1 [DAQ]
17:31:19 h1daqgds1 [DAQ] <<< GDS1 manual restart after removing GDS chans from broadcaster
17:33:22 h1daqgds0 [DAQ] <<< 0-leg restart
17:33:27 h1daqfw0 [DAQ]
17:33:28 h1daqnds0 [DAQ]
17:33:28 h1daqtw0 [DAQ]
17:37:55 h1daqfw0 [DAQ] <<< FW0 spontaneous restart
TITLE: 01/16 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
SEI_ENV state: MAINTENANCE
Wind: 8mph Gusts, 4mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.22 μm/s
QUICK SUMMARY:
More alignment going on today, and going to laser safe in the afternoon
Since nobody seems to have made an alog, here it is.
We've steered the JAC transmission beam into HAM2 and removed the viewport cover on HAM2 on the +Y side to look inside. At first we had a hard time seeing anything. We steered the beam in YAW and PIT and still nothing.
After a while we found that if we position the IR viewer at a specific position and look into the baffle hole of the MC refl periscope (circled in yellow in the 1st attachment), we can see some kind of ugly IR that definitely comes from JAC, but no beam seemed to be coming out of the baffle hole.
2nd attachment shows the picture shot by an IR sensitive camra when we focused on the IR, and the 3rd attachment shows the same picture shot from the same position but focused on the baffle.
The distance from the sensor to the subject according to the lens' indicator was something like 4m for IR and 1.5-2m for the baffle. The indicator is only good for visible light and not for IR, but empirically the scale is not a factor of 2 off for IR, so we're looking at something that is far from the baffle (i.e. we're looking at the image of the source reflected by the periscope mirrors).
Another possibility that Masayuki points out is that it could be some IR beam (probably not the main beam) hitting the vertical metal pillar of the periscope behind the bottom periscope mirror and we're looking at that through the space between the baffle hole and the periscope mirror (see the 4th attachment). I think that unlikely because the pillar is merely inches away from the baffle and the distance indicator of the lens doesn't agree. But we'll see.
Tomorrow we intend to remove the septum window cover for IFO REFL and POP and look into HAM2 from there, that way hopefully it's easier to find where the JAC beam lands in HAM2.
We had some hiccups in our end of day daqd restart.
1. There were duplicate channels between the h1susb13 and h1susb2h34 models. We are not sure how these got through, the daqd should have crashed on startup with an error message. We found this as it caused issues on the test framewriter on h1daqfw2.
2. After Oli removed the old block from h1susb13 we found that there were some GDS broadcaster channels that were dropped that probably shouldn't be. We removed them from the broadcast list in order to get the daqd to run. Listing the channels here so that they can be added back in tommorow:
After looking through the code, this is an old bug. It has been fixed for a while. The daqd had not been updated with the rcg for a long time due to no feature changes.
We should do a daqd package upgrade next week.
[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).
TITLE: 01/15 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:
Update to "Status of Things": HAM1-2 Septum had a viewport cover removed (so, 3 of 4 are covered) for JAC alignment. ~100mW coming from the PSL to HAM1 for JAC (not noted on the white board).
JAC alignment work continued most of the day. Did not roll IOT2 into place (latest plans are to do this tomorrow [Fri] afternoon) with the LVEA being transitioned to SAFE prior to this work (aiming for lunchtime).
SQZ alignment work continued in the afternoon.
SUS model/daq work appears to be nearing completion (Jeff, Oli, RyanS, Dave (remote), EJ (remote)) !
LOG:
FAMIS 31120
Starting last Thursday, the NPRO temperature is a bit more unstable than usual, but I'm not exactly sure why. There was a brief incursion into the anteroom last Friday, which is seen in the usual places, but everything appears to have come back as expected. The RefCav still looks to need some alignment, which I will likely get to next week. Otherwise, the PSL is looking good.
Thu Jan 15 10:08:48 2026 INFO: Fill completed in 8min 45secs
Closes FAMIS#39747, last checked 88725
Laser Status:
NPRO output power is 1.845W
AMP1 output power is 70.39W
AMP2 output power is 139.1W
NPRO watchdog is GREEN
AMP1 watchdog is GREEN
AMP2 watchdog is GREEN
PDWD watchdog is GREEN
PMC:
It has been locked 6 days, 18 hr 2 minutes
Reflected power = 26.47W
Transmitted power = 104.5W
PowerSum = 131.0W
FSS:
It has been locked for 2 days 23 hr and 18 min
TPD[V] = 0.4029V
ISS:
The diffracted power is around 4.0%
Last saturation event was 0 days 0 hours and 0 minutes ago
Possible Issues:
PMC reflected power is high