At 17:26 Thursday 19feb2026 h1iopiscex had a timing glitch causing a TIM+ADC error in its state word.
At 20:00 I restarted all the models which cleared the error.
Beam dump for HAM1-HAM2 septum window AR reflection.
This was installed.
Beam dump for the -Y door viewport reflection.
Jason and Betsy installed it. There seems to be a discussion as to whether or not something else needs to be done.
EOM and JAC power budget again.
We measured the power at various places. While Jason held the power meter head still, I ran the statistics function of the power meter for a few seconds. I only list the mean and the standard deviation.
Wrong pol is king of large, ~0.2% of the main beam power coming out of EOM. That's 200mW when 100W goes through the EOM.
JAC throughput of 92% is not great, but Jason says the alignment and the matching are not really optimised.
| JAC input | 112mW+-462uW | |
| EOM input = JAC output | 103mW+-6.3mW |
JAC OUT/IN = 0.92+-0.06 |
| EOM front AR reflection | 57uW+-4.4uW |
EOM AR/IN = (5.5+0.5)*1e-4 |
| EOM output (including the wrong pol beam) | 96.9mW+-1.4mW | |
| EOM wrong pol beam | 226uW+-17uW |
EOM wrong pol/IN = (2.2+-0.2)*1e-3 |
| EOM main pol (= out total - wrong pol) | 96.7mW +-1.4mW |
EOM main pol/IN = .9978+-2e-4 |
Afternoon work, REFL path aligned, RF lock works (Jennie, Jason, Betsy, Daniel, Keita)
It seemed as if what was supposed to be TFP after HWP was not really TFP, it was temporarily set aside.
REFL path to the JAC REFL RFPD was aligned without TFP. 100mW into JAC was enough to see the REFL beam there.
DC responded as expected.
There was a confusion about which demod chassis was used for JAC, which was sorted out by Daniel who subsequently set the demod phase. I zero-ed the dark offset.
I copied the JAC lock filter from dither path to JAC-L_SERVO path, locked JAC with dither, disabled the input to the dither servo and enabled RF locking in parallel, which worked just fine. I made rough changes to the RF servo to bump up the UGF to ~400Hz without too much gain peaking, I haven't tried anything aggressive to squash the residual motion below 200Hz, you might want to tweak it further.
I didn't disable the dither itself for the JAC PZT so we can compare the spectrum of RF and dither side by side. See attached, this was measured with 100mW into JAC, note that the dither error signal is scaled. References are with the purge air on and current traces are with the purge air completely turned down.
Guardian needs to be changed to allow smooth locking with RF.
Rahul, Jeff, Oli
In December 2025 when we needed to compensate for the HAM1 DACs moving from 16- to 28-bit, we had decided to have FM10 in the COILOUTF bank be gain(1024), and put the remaining gain(4) upstream in multiple other places (88553). This led to our confusion today when we realized that when taking transfer functions for PM1 and JM3, the TEST banks had gone back to gains of 1 a couple weeks ago, and since we had damping off, the extra gain wasn't going through to the excitation. This might at least partially be why PM1 had dropped in magnitude, and why the JMs are so low in magnitude too.
To solve confusion, I've gone through PM1, RM1, RM2, JM1, and JM3 and removed the extra gain(4) that's in:
- DAMP bank FM4
- TEST bank gains (if still there)
- OPTICALIGN gains
- LOCK filter bank gains
Then I updated the gains in COILOUTF FM10 from gain(1024) to gain(4096).
I've sdf'd the values and loaded in the changed filter modules. I also committed the filter file.
*To remove future confusion about the difference in value of the "28BitDAC" filter module in COILOUTF FM10, I am going to go through all the suspensions and change the name of that filter from "28BitDAC" to be something like "16to28Bit" or "18to28Bit" depending on the previously used DAC bits
TITLE: 02/20 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY: More HAM1 alignment work today
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 22:49 | SAF | LVEA is Laser SAFE | LVEA | NO* | LVEA is Laser SAFE *Bifurcated HAM1/2* | 16:49 |
| 15:00 | FAC | Nellie | LVEA | YES | Tech clean | 15:04 |
| 15:00 | FAC | Kim | LVEA | YES | Tech clean | 15:38 |
| 15:30 | FAC | Randy | LVEA | n | Working on test stand | 19:58 |
| 16:17 | VAC | Jordan | LVEA | YES | Turning down HAM1 purge air, HAM7 continuing leak checks | 16:24 |
| 16:30 | EE | Fil | MER | n | Electronics work | 18:32 |
| 16:36 | FAC | Kim | LVEA | YES | Tech clean | 17:23 |
| 17:13 | JAC | Keita | LVEA | YES | JAC alignment | 20:11 |
| 17:13 | VAC | Gerardo | LVEA | YES | Turning up HAM1 purge air | 17:17 |
| 17:20 | EE | Marc | MER | n | Joining Fil for electronics rack work | 18:32 |
| 17:22 | JAC | Jason | LVEA | YES | JAC alignment | 20:23 |
| 17:59 | VAC | Jordan, Travis | LVEA | n | HAM7 leak checks | 18:23 |
| 18:21 | SPI | RyanS | OpticsLab | y(local) | SPI setup | 21:42 |
| 18:24 | JAC | Jennie | LVEA | YES | JAC alignment | 20:11 |
| 18:39 | Betsy | LVEA | YES | JAC work | 20:23 | |
| 18:50 | JAC | Rahul | LVEA | YES | Checking on JAC team | 19:02 |
| 18:51 | SUS | Ibrahim | LVEA | n | Helping Randy at test stand | 19:58 |
| 19:10 | VAC | Gerardo, Jordan, Travis | LVEA | n | CP1 pump | 20:11 |
| 19:14 | SPI | Jeff | OpticsLab | y(local) | SPI work | 21:42 |
| 20:07 | PEM | Robert | EX | n | Grounding himself | 21:23 |
| 20:49 | FAC | Randy | LVEA | n | Test stand work | 23:01 |
| 21:21 | TCS | Sophie | JOAT Lab | n | Taking photos | 21:39 |
| 21:55 | Betsy | LVEA | YES | Opening light pipe | 21:57 | |
| 21:56 | TCS | Sophie | JOAT Lab | n | Taking more pictures | 22:03 |
| 22:03 | FAC | Ibrahim | LVEA | n | Test stand work | 23:01 |
| 22:43 | JAC | Jason, Keita | LVEA | YES | JAC alignment | 00:43 |
| 22:48 | EE | Marc | LVEA | n | Cable intel | 23:44 |
| 22:55 | TCS | Sophie, Shreyan | JOAT Lab | n | Populating tables | ongoing |
| 23:01 | SPI | RyanS | OptLab | n | Setting up SPI | 00:23 |
| 23:03 | JAC | Jennie | LVEA | YES | JAC alignment | ongoing |
| 23:11 | FAC | Tyler, 2 contractors | LVEA | n | Checking out HVAC equipment | 23:36 |
| 23:25 | JAC | Betsy | LVEA | YES | JAC allignment | 00:06 |
| 23:26 | SPI | Jeff | OptLab | n | SPI work | 00:18 |
| 23:35 | EE | Tony, Fil | LVEA | N | Grabbing Ladder | 23:57 |
RyanC, Rahul
We glued prisms (primary - sapphire and secondary - metal) to the HRTS OM0 fused silica Optic, meant for LHO (D2100495-V5-OM0-02).
Attaching two pictures below for reference - they show the two prism glued to the barrel and the four magnet bases on the AR side of the optic.
I will post the details about its metrology later on.
---
OM0 optic meant for LLO has already been processed (i.e. prim glued) and shipped in Jan2026 - see alog 88786 for details.
S. Muusse, C. Compton, S. Goswami
We started populating and aligning optics on the second table. Most optics are now mounted and the beam is aligned upto M3 as per the fintrace model. We have aligned with the PD pick off in to save realignment later.
Construction begun on the camera can (D1300703) but did not get far as the screws which are fixed into the side panels (D2500165) are not long enough to reach the nuts attached to the other face of the box. Pictures of these components are attached.
We attached the viewport housing on the table which fits as expected. (photos attached)
Closes FAMIS#39752, last checked 89164
Laser Status:
NPRO output power is 1.841W
AMP1 output power is 70.47W
AMP2 output power is 138.8W
NPRO watchdog is GREEN
AMP1 watchdog is GREEN
AMP2 watchdog is GREEN
PDWD watchdog is GREEN
PMC:
It has been locked 0 days, 2 hr 51 minutes
Reflected power = 26.95W
Transmitted power = 104.0W
PowerSum = 131.0W
FSS:
It has been locked for 0 days 0 hr and 0 min
TPD[V] = 0.4856V
ISS:
The diffracted power is around 3.8%
Last saturation event was 0 days 2 hours and 9 minutes ago
Possible Issues:
PMC reflected power is high
Closes FAMIS#39855, last checked 89138
Corner Station Fans (attachment1)
- All fans are looking normal and within range.
Outbuilding Fans (attachment2)
- All fans are looking normal and are within range.
Now that HAM7 is at sufficient pressure (6.4E-7 Torr as of this post) we helium leak checked the two re-installed 12" CF blanks removed for table locking and the entire relay tube assembly which had been removed for the viewport adapter on HAM5.
The Helium background was unstable, so we turned on the HAM7 cleanroom (on 2/18 afternoon) to help flush the area of helium overnight.
Today the background stabilized around 1.5E-10 Torr-l/s, so we were able to continue leak checking. No significant helium signal observed above the leak detector background which hovered between 1.5&2E-10 Torr-l/s during leak checking.
HAM7 continues to pump down with the turbopump, next steps are chamber RGA scans.
DAQ was restarted around 12:02 PM PST after restarting h1ascimc.
Thu Feb 19 10:12:02 2026 INFO: Fill completed in 11min 58secs
Yesterday afternoon Rahul centered the OSEM flags on JM3 (89187). This morning I took another set of transfer functions to check that they're looking good. Flags are well centered (pic), and transfer functions are looking good (TFs).
Settings:
- ISI Locked
- OFFSETs OFF
- DAMP OFF
Data:
/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/JM3/SAGM1/Data/2026-02-19_1645_H1SUSJM3_M1_WhiteNoise_{L,P,Y}_0p02to50Hz.xml
r12913
Results:
/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/JM3/Results/2026-02-19_1645_H1SUSJM3_M1_ALL_TFs.pdf
r12914
Rahul, Fil, Oli
We still don't know why PM1 looks different now than it did when we installed it back in May 2025. Currently, we've nailed it down to two possibillities: (1) there's an issue with PM1 somewhere between the satamp and the in-chamber stuff, or (2) the December 2025 satamp swap to a modified satamp changed the magnitude of PM1 (we are not sure if this makes sense).
Here are some measurements we took yesterday and the things we've looked at so far.
Satamp
We were worried about the satamp, which is a dual satamp, swapped in in December 2025 (88590), with JM3 taking up the other half, so I took some transfer functions yesterday morning for both PM1 and JM3. I compared JM3 now to how it looked when we first installed it in December 2025, and it looks exactly the same, no drop in magnitude for JM (JM3 Dec2025 vs Feb 2026), and no increase in magnitude for PM1 (PM1 May 2025 vs Feb 2026).
Fil then swapped all the PM1 cables on the satamp with all the JM3 cables on the satamp. This made it so the only difference between the previous and these measurements is the part of the satamp used. These measurements for PM1 and JM3 still looked the same as the earlier measurement, so it's not the satamp (PM1 JM3 comparison). These comparison plots really show how much PM1 changed compared to JM3.
All other in-air electronics
The only other difference from the measurements last May for PM1 should be the coil driver, since the other one failed (88998). The new coil driver is modified, just like the old one, and is being correctly compensated for in the coil drive filter banks. To check this, as well as the rest of the in-air electronics, Fil swapped everything back to nominal EXCEPT for the cables that run from the sat amp out to the chamber. This way, JM3 is using the in-air electronics from PM1, and PM1 is using the in-air electronics from JM3. I did a few transfer functions looking for any difference but both suspensions and electronics chains still look the same(PM1 L, PM1 P, JM3 P). This could mean that the issue with PM1 is due to something in the satamp-to-chamber cable or in vacuum.
OSEMs
We checked the spectra for the PM1 BOSEMs but we did it while the purge air was up, so they're very noisy and not very useful.
Satamp question
The only other thing we can think of that could've changed the magnitude of PM1 but not affect what we're seeing in JM3 would be due to the satamp swap in December. The new modified satamp was hooked up to PM1 and JM3 on December 18, 2025 (88588). JM3 was first tested the next day, and obviously we never got a measurement of JM3 with an unmodified satamp, so if it's possible for the satamp to change the magnitude of PM1, that might be what is happening. I haven't had time yet to check whether other suspensions show anything like that.
Measurement info
PM1
2026-02-18 1600
- ISI Locked
- alignment offsets OFF
- DAMP OFF for measured DOF, ON for other DOFs
Data:
/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/PM1/SAGM1/Data/2026-02-18_1600_H1SUSPM1_M1_WhiteNoise_{L,P,Y}_0p02to50Hz.xml
12905
Results:
/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/PM1/SAGM1/Results/2026-02-18_1600_H1SUSPM1_M1_ALL_TFs.pdf
12909
2026-02-18 1715
- satamp inputs swapped with JM3 (tfs look the same)
- ISI Locked
- alignment offsets OFF
- DAMP OFF
Data:
/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/PM1/SAGM1/Data/2026-02-18_1715_H1SUSPM1_M1_WhiteNoise_{L,P,Y}_0p02to50Hz.xml
12906
Results:
/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/PM1/SAGM1/Results/2026-02-18_1715_H1SUSPM1_M1_ALL_TFs.pdf
12909
JM3
2026-02-18 1600
- ISI Locked
- DAMP OFF
- alignment offsets OFF
- DAMP OFF for measured DOF, ON for other DOFs
Data:
/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/JM3/SAGM1/Data/2026-02-18_1600_H1SUSJM3_M1_WhiteNoise_{L,P,Y}_0p02to50Hz.xml
r12904
Results:
/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/JM3/SAGM1/Results/2026-02-18_1600_H1SUSJM3_M1_ALL_TFs.pdf
r12908
2026-02-18 1730
- satamp inputs swapped with PM1 (tfs look the same)
- ISI Locked
- alignment offsets OFF
- DAMP OFF
Data:
/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/JM3/SAGM1/Data/2026-02-18_1730_H1SUSJM3_M1_WhiteNoise_{L,P,Y}_0p02to50Hz.xml
12907
Results:
/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/JM3/SAGM1/Results/2026-02-18_1730_H1SUSJM3_M1_ALL_TFs.pdf
r12908
Comparisons
PM1 May 2025 vs PM1 Feb 18 2026
/ligo/svncommon/SusSVN/sus/trunk/HTTS/Common/Data/allhttss_2026-02-18_PM1_May2025vsFeb182026_ALL_TFs.pdf
r12911
JM3 Dec 2025 vs JM3 Feb 18 2026
/ligo/svncommon/SusSVN/sus/trunk/HTTS/Common/Data/allhttss_2026-02-18_JM3_Dec2025vsFeb182026_ALL_TFs.pdf
r12912
JM3 Dec 2025 vs JM3 Feb 18 2026 vs PM1 May 2025 vs PM1 Feb 18 2026
/ligo/svncommon/SusSVN/sus/trunk/HTTS/Common/Data/allhttss_2026-02-18_PM1_JM3_PM1looksdifferent_ALL_TFs.pdf
r12910
Is this a difference of the coils or sensors? One thing that changed was the LIGO DAC. Could there be a factor of 4 difference in gain due to a confusion between 18-bit, 20-bit, and LIGO DACs?
TITLE: 02/19 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: 17mph Gusts, 10mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.36 μm/s
QUICK SUMMARY:
More HAM1 work today
I added this shutter (shutter H1:SYS-MOTION_C_SHUTTER_M) to the main shutters screen at sitemap->LSC->Shutters. I also added a menu button that takes you to the control screen to the sitemap->IOO->JAC Overview screen, see pic.
We locked JAC with 1W input to find ghost beams. Details will come after we're done with the septum window reflection, but anyway here is the list:
None of the new beam dumps are interfering with the main beam and JAC refl/trans.
Jennie W, Ryan S
Summary: Ryan and I updated the JAC and IMC ASC models. We installed JM3 yesterday and so now the IMC cannot use the PSL PZT mirror as an alignment actuator. I have committed the changes to the svn but erik and dave will do some checks tomorrow before they commit to the revision locked version of the model and restart the DAQ. So changes are not 'live' yet.
The edits were made to h1ascimc.mdl which has top level blocks for IMC and JAC.
The JAC top level model sends signals directly to the PSL PZT mirror and these degrees of freedom are swapped as the PSL PZT basis P and Y are switched before input to the JAC due to the HAM1 input periscope.
I took out the feedback paths for PZT_P and PZT_Y that come out of the IMC block. The picture shows the old config and I have highlighted what I removed.
At the top level, IMC no longer sends signals to the PZT but instead to JM3. On the top level diagram, the signal JM3_P is sent via PCI cards to the channel "H1ASC-JM3_YAW_SUSHTTS" as pitch in the JAC basis is yaw in the IMC basis due to the HAM1 output periscope. The picture shows the old config and I have highlighted what I swapped.
The signal JM3_Y is sent via PCI cards to the channel "H1ASC-JM3_PIT_SUSHTTS" as yaw in the JAC basis is pitch in the IMC basis due to the HAM1 output periscope.
Within the IMC top names block I removed the output channels for the PZT from the WFS feedback path, we already had paths to feedback to JM3 within this path. The picture shows the new config.
I removed the PZT locking path from the LCKIN block and replaced it with one for JM3. The picture shows the new config. I am not sure we ever use this path (which is for dither asc control of the IMC) in the first place so maybe this was unneccessary.
I also removed the channels H1:IMC-PZT_YAW_OUT and H1:IMC-PZT_PIT_OUT from the DAQ channel list for the IMC model.
Jennie W, Dave B, EJ D, Erik V, Keita K, Daniel S, Jeff K, Olli P,
This morning I rebuilt the model again before it was restarted to add back in the IMC-PZT_PIT_OUT_DQ and H1:IMC-PZT_YAW_OUT_DQ channels in the top level of h1ascimc so as to avoid removing these channels from the GDS broadcast channel list.
Unfortunately this change did not get propagated to the live model today (it was not built with the rev-locked tag). This caused some confusion when the model + DAQ restart happened ( alog #89196). I had forgotten to SDF the PZT sliders for IMC-PZT_OUT and so this mis-aligned the beam to the JAC. Keita brought this back by altering the IMC sliders and we were able to continue with optics work in HAM1.
On the CDS side, none of my changes from today or yesterday have been uploaded to the 'rev-locked version of the model so everything was restarted with the old model config from yesterday morning. We will aim to restart with model changes to h1ascimc (that I made last night and this morning) at sometime Monday morning.