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

17:13 UTC GRB -Short E630194 H1 was in Idle.  
ITMX was moved to get better X arm light earlier today. Since then we have been able to Lock PRMI.
Sheila and Gabriele went and took some pictures of inside the HAM1 chamber, so keep an eye out for cool HAM1 pic filled alog.   
We can consistantly get PRMI to lock. The Ryans are currently working on getting mich ACS to work.

LOG:                                                                                                                                                                                                                                                                                        

J. Freed

For the build of SPI, I measured the expected power output from a dual source Keysight 33600A through SPI's 2W amp D2500004. These measurements were taken with a E4418A EPM power meter using the HP 8484A 30dB attenuator attachment. After analyzing the data it is hard to say that the power meter power readings were accurate but the power the AOMs are receiving should be below the damage threshold of 33dBm.

I measured the power at 2 points in the chain from Keysight -> 2W  -> SPI prep, for both channels. (SPI_Build_RF_Diagram.png) The first point is just before the 2W amp, and the second point is just before the SPI prep for both channels. Then I compared that with what the output monitor voltage was showing on SPI prep for both channels.

Power_Before_2W_Amp.png Is the data collected from power measurements just before the 2W amplifier. The limit of 22dBm is the limit of the keysight. From this it can be seen that there is not a 1-1 measurement between what the keysight says it is outputting and what the HP 8484A sensor is measuring. This difference is also changing based on the input power itself. With lower power overestimating what the keysight says its outputting, and higher power underestimating what the keysight says its outputting. This is a problem with the probe as switching out the probe to an E-series gives a relatively consistent error of -0.2dB between what the keysight says its outputting and what is being measured. Unfortunately the HP 8484A sensor is the only probe that can measure up to the 32-32.5dBm needed for SPI. Interpolating the results of the HP 8484A sensor up to 32 dBm gives approximately a 0.4dB underestimation of the power.

Then I took a measurement of the power after the 2W amp at the end of the cable that would plug into SPI prep. Namely I adjusted the power from Keysight, such that the output measured on the probe was 32dBm which is what SPI prep is expecting accounting for any possible underestimation of the power. Note that power past the 2W amp decreases over time (by about 0.5dB total) as the device warms up so I had to wait a couple of hours after start-up to take this measurement. The results were:

AMP 1 (Which goes into the ref path) measured 32dBm when the keysight displayed: -1.7dBm

AMP 2 (Which goes into the Meas path) measured 32dBm when the keysight displayed: -0.3dBm

Be aware that that 32dBm has an error of +/- 0.5dB due to the factors listed above. 

Then using the fact above, I found that the whole AMP 1 chain has a gain of 33.7 dBm from what the keysight displays. And AMP 2 chain has a total gain of 32.3dBm from what the keysight displays. Using this fact I could find the voltage associated with each of the monitor channels of SPI prep.

Monitor_read_AMP1_REF.png and Monitor_read_AMP2_MEAS.png show the monitor reading voltage vs the approximate input RF power into SPI prep. for both channels. Interpolating the results gives a calibration equation between RF power and monitor voltage of: 

AMP 1 (REF):  [V] = -0.0249*[dBm] + 1.5480

AMP 2 (MEAS):  [V] = -0.0246*[dBm] + 1.5387

With both channels reaching 32dBm around 0.75V on the monitor channel this gives an easy target for controling the power.

Betsy, Sheila, Jennie W, 

This morning Betsy and I removed the viewport cover on the -Y, -X upper port of HAM1.  We pointed a laser pointer at REFL WFS A and B, and saw similar DC counts on each of them, with WFS A channels responding when I pointed the laser pointer at the +X diode and WFS B responding to the the -X diode.  We were also able to point the laser pointer at LSC REFL B and LSC POP, and both responded.  We can't reach LSC REFL A, but we know that diode is responding.  POP X is not easily accessible this way, although we might be able to reflect off PM1 to hit that diode.  

Jennie W and I went back with the Nikon D810 from Keita's office.  We expirimented with different settings on the camera, and taking photos with illuminators and table lights on and off.  A few photos are attached, you can see IR light on the barrel of the beamsplitter that splits the beam between WFS A and WFS B.  There is also a glint on the mount of the second lens on the sled. 

Upgraded the main slow controls software to add some calibration features for CHETA. 

I've reworked the CDS Overvew MEDM for the HAM6 changes.

The additional corner station SUS models have increased the SUS column's height (first column). To accomodate I've moved the WATCHDOG section over to the second (SEI) column, below the consolidated SUSAUX section.

The DAQ section has been moved to the 3rd column (ISC).

The new h1sush6 front end, highlighted in WHITE, is not currently in the DAQ, hence the grey'ed DAQ status.

Placeholders for the LO12, LO3 and SUSAUXH6 models are highlighted in ORANGE.

I think this overview contains all the additional parts needed for IR1.

Mon Mar 16 10:10:45 2026 INFO: Fill completed in 10min 42secs

FAMIS 31129

The IMC was left 'DOWN' at the end of last week, so as it naturally flashed through resonance, the FSS was being pushed on a bit, which explains the noisy FSS TPD signal over the weekend. Once the IMC was locked this morning, this behavior stopped. No other events to report this week.

TITLE: 03/16 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: CALM
    Wind: 6mph Gusts, 4mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.30 μm/s 
QUICK SUMMARY:

Seems to me like it's a good day to Lock and IFO.
Beam splitter ISI had a wtchdog tripped when I came in.
There are a few things that seem a bit off with the ISI Like: the ISI_BS_ST1_SC Guardian is white like it can't load something. The CPS  blends have White boxes in them. FF01 & 12 , ST 1 & 2 ISO ,  all contain red boxes.
HWWD stat button is white. Spoke to CDS team Dave Said the ISI_CUST_CHAMBER_OVERVIEW screen needs to be updated to show the ISI_BS_ST1_SC Guardian correctly. As there may be an error on that screen.

Locking Notes:
Took ISC_LOCK to Manual_INTIAL_ALIGNMENT 
Aligning Green arms: 
X arm is only around 0.4 after my best attempts to align it. I may double the H1:ALS-C_TRX_A_LF_OUT16 value. to get past Locking IR.
Y arm however has fantastic flashes. 

Requested ALIGN_IFO to PRC_ALIGN_OFFLOADED & Got Stuck at WFS_CENTERING_PRX.... maybe we are't yet able to use the WFS? 

Took ALIGN_IFO back to init then PRX_ LOCKED, Made it there. then to Down, then to MICH_BRIGHT_OFFLOADED.
 

Sun Mar 15 10:14:56 2026 INFO: Fill completed in 14min 52secs

Sat Mar 14 10:14:30 2026 INFO: Fill completed in 14min 27secs

The JAC heater turned on at 8:00 PM PT. JAC-HEATER_POWER_SET is set to 3.

• TITLE: 03/14 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
  STATE of H1: Planned Engineering
  INCOMING OPERATOR: None
  SHIFT SUMMARY: I touched up DRMI alignment but we're still having issues with DC centering.
  LOG:  

• 01:20 UTC Oli and Jennie report that one of the light bollards in staging upper (the one closest to the stairs) shorted out, gave off a flash of light, a noise and started to lightly smoke. I informed Tyler who took a look using the remote cameras and determined its probably ok for the weekend, but he'll check up on it again.
• While we were locked in DRMI I maximized the power with BS, PRM, and SRM. I was only really to make any gains with PRM_P.
• "WFS DC centering railed" ISC_DRMI, I couldn't get the DC centering loops to turn on and stay on, PM1 was just railing constantly. I found an alog from Elenna with a possibly similar situation alog84782. The codes says its only checking DC1,2,3,4 at this stage and none of those are showing OUTPUTs greater than their LIMITS, only DC6 was showing OUTPUTs > LIMITS and the  section of ISC_DRMI wfs_centering for REFL_AS should only check DC1,2,3,4, I'm not sure why its trying for DC6 (PM1?). I tried greatly reducing the gain, even setting it to zero for DC6 to no avail. 
• 02:12 UTC I went DOWN and tried to come back up, it went quite quickly, ALS locked quickly on its own ( I reupped the gain on the TRX), IR went great then we locked DRMI within 3 minutes of entering the state ( I didn't raise any of the POPAIR or REFL RF gains) to get stuck by the WFS DC centering railed again. I now tried to reduce all the gains of the DC loops, turning DC6 to 0. After a few minutes  ISC_DRMI was able to complete its DRMI_WFS_centering state that it had been stuck in, ISC_LOCK went into up to ENGAGE_ASC but we were constantly saturating RM1 with verbal calling out HTTS
• 02:35 UTC DRMI locked instantly this acquisition (without increasing the LSC gains again), I played with the gains on the DC loops, increasing DC2_Y from -3.5 to -4.0 allowing us to get past the centering, the RM1 HTTS sats started again after we entered ENGAGE_ASC until we lost lock when PRC1 started.
• 02:47 UTC DRMI unlocked, and I put us into IDLE for the weekend

Pumpdown continues on HAM1 and it is progressing.  The chamber is currently being pumpdown with the SS500 cart aiding the turbo pump up on top of the chamber.  We are very close to opening the ion pump for this chamber.  Vacuum pressure is currently at 8.95x10^-07 torr.  The aux carts to pumpdown the annulus for both chamber HAM1/2 were disconnected Monday, see aLOG entry 89440.

I used a power meter to measure the power consumption of a Gamma ion pump controller (Digitel MPCq type) to power the 1200 l/s ion pumps (this one located at Y2-8), I concentrated on startup of the controller, then on startup of the high voltage (7kV) for the ion pump..

During the initial startup of the ion pump controller the consumption goes up slow, it creeps up to 12.04 Watts max, then it drops a bit after.  The second part of the test was to see the consumption spike when turning on the high voltage for the ion pump, for this test the meter immediately goes up to 40.69 Watts, then after a few seconds the power drops slowly.

A side effect of running this test can be appreciated on the attached trend data, because we powered off the ion pump the vacuum pressure internal to the main volume went up, it can be appreciated by the gauges along the Y-End station as well as Y2-8 gauge.

To do the test I powered the unit off and back on 3 times.

Sheila, Oli, Jennie, Tony, Ryan Crouch

Summary: Today we found that the 9MHz modulation depth was low because of a wrong setting, and that the beam was misaligned on the LSC REFLAIR A diode. After these changes and some gain adjustments we were able to lock DRMI.  

Details:

After restoring the 9MHz modulation depth this morning (89497), we went on to locking PRMI, using the notes from 89491, but scaling for the increased modulation depth.   Once it was locked, Oli and I went to ISCT1 to double check the alignment onto the POPAIR diodes, we slightly improved the alignment onto POPAIR A, but POPAIR B was already well aligned.  We measured 0.55mW in the POPair path before the splitter using a power meter. 

Oli phased POP18 + POP90 to maximize the I ERR signal with PRMI locked, and we put a 132 Hz, 3000 count exitation into PRM LOCK L to phase REFLAIR 9 and 45 to minimize the PRM signal in Q.  (userapps/lsc/h1/templates/phase_REFLAIR.xml)  We then adjusted the gain in REFLAIR 9 to match the ugf to the PRMI reference (screenshot).  In O4, we used a whitening gain of 12dB and then a digital gain of 0.25 before the phase rotation, and LSC input matrix of 1.75 .  Now we are using 30dB of whitening gain and a digitial gain of 4.4 to reproduce the same ugf (input matrix unchanged 1.75), so we are missing a factor of 140 signal strength compared to O4.  For MICH the ugf is also right on the reference, screenshot.  This is with 30dB of whitening gain and a digital gain of 4 before the phase rotation, compared with 0dB of whitening gain an a digital gain of 1 in O4, so this signal is too small by a factor of about 126.  So this is pretty similar to the signal loss for REFLAIR 9.  

Oli and I went back to ISCT1, removed the ND filter, and realigned reflair A.  This gave us 2.5 counts on REFLAIR A LF, and we were able to relock PRMI with the whitening gains for REFLAIR back to normal.  We adjusted the phase of reflair, and added some digital gains to set the ugfs to what they used to be.  

A comparison time with PRMI locked in November 14th 2025, 22:23:00 UTC

We ran SRY alignment manually, (the WFS don't work since we have not rephased them).  

This screenshot shows the gains I had manually adjusted when we got a 3 second DRMI lock, March 13th at 23:28:21 UTC.  

DRMI locking references: trigger levels: 44348  filter states and loop measurements: 87768   When DRMI grabs for a few seconds, it looses lock due to a 20Hz oscillation (screenshot), which suggests the MICH gain is too high.  I tried a few changes to MICH gains.  In this grabbing attempt, it seems that the MICH filter changes are what is making things unstable.  

Edited to add: We have locked DRMI, with three manual changes, to the POP18 digital gain (set to 3 as in screenshot), RF9 gain set to 0.31, and RF45 gain set to 2.17.  We think that this was too high for RF45, and instead it should be left as SDF will set it at 1.  We stepped through the DRMI_locked guardian state manually which was fine.  

I added a check for the JAC shutter to the 'LOCKING' state to its guardian. This was because it was closed when the guardian was trying to lock JAC this morning and it took us a while to figure out.

We haven't had a chance to check this today due to efforts to lock DRMI but I will check it on Monday.

Its on lines 207-209 of the script.

 if ezca['SYS-MOTION_C_SHUTTER_M_STATE'] != 0:#added to notify if shutter closed. J Wright 2026-03-13.
            notify('Shutter closed. Check shutter trigger values.')
            self.timer['waiting'] = 5

Thanks to Tony for helping me debug gedit.

Control room

RM2 SWWD has been bypassed temporarily until we offload some of it since we're near the end of the ADC range for one of the channels.

The ADC reaching the end of its range isn't what actually caused the trips though . The HAM1 ISI SW watchdog tripped after being triggered by RM2's LP SWWD. It looks like the LOCK filter bank integrators had started raking up counts, eventually causing large oscillations in the suspension that surpassed the LP SWWD threshold. The integrators for RM1, RM2, and PM1 all started building up at the same time, but for whatever reason the build ups on RM2 were much larger.

Jim says that he doesn't care for the HAM1 ISI whether any of the little tip tilts on there trip, so we're bypassing RM2 for now since its the closest to tripping.

Took a picture of the pumpout port for each of the cryopumps.

The attached pictures below are from CP1 to CP8 from left to right.

[Tom R, Ibrahim]

We glued 6x of the QOSEM flags, attaching the lens (D2500277) to the aluminium body (D2500253). This was done using a jig (D2600054) to ensure the lenses were aligned to the body of the flag. We used EP30.

Only a tiny drop of glue is required, and was applied directly to the lip of the body using a thin wire. The flags will be left to dry overnight before another batch of 6 will be glued.