(Travis S., Jordan V., Gerardo M.)

First, the good news, we managed to helium leak check all of the conflats that were added or "touched" related to HAM1 volume, and no leak was detected above the background of 1.9x10^-10 torr*l/sec of He.  All electrical feedthroughs, all five way crosses, new gauge tree, and a new turbo flange were leak tested. 

Now for the puzzling part, after all items were leak checked, we valved in the ion pump to HAM1, as soon as that was done, since we still had the leak detector backing the turbo pump the background went up to 2.5x10^-09 torr*l/sec of He, a little sick ion pump??

HAM1 annulus system is lagging behind, its ion pump controller is railed at 10 mA.  HAM1 and HAM2 share the same annulus volume, both systems are currently being pumped down with two different aux carts, both of the ion pump controllers were turned on today, HAM2 system is currently sitting at 7 mA, but HAM1 still railed as stated above.  If the performance does not improve we'll need to break out the big wrenches to revisit the doors.

The squeezer path from HAM7 to HAM8 is open now, all closed valves were opened today, RV1, FCV1, FCV2, FCV3, FCV4, FCV5.

Main Turbo pumps were shut down today, output manifold turbo, Y-Beam manifold turbo, and the X-Beam manifold turbo.  HAM6 turbo pump was also turned off, but the cart still powered on.

Rogers Machinery was in the mechanical room today, see work in progress on the photo below, new compressor and new dryer skid, rough location, rough position.

TITLE: 05/29 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY: This evening was mostly focused on trying to gradually engage full IFO ASC. We've been able to consistently get relocked up to PREP_ASC_FOR_FULL_IFO as long as (mostly) PRM alignment is touched up every so often, but work is still ongoing to close ASC loops once there. See primarily alog84646 and comments for details.

For the night, we're leaving H1 locked at PREP_ASC_FOR_FULL_IFO with a few ASC loops closed, but 'DOWN' is requested so that it won't try to relock if it drops out. [Tagging OpsInfo] In the morning, if H1 is still locked here, hang tight until more commissioning of the ASC loops can happen. If unlocked, run an initial alignment skipping PRC steps (as we have been this week).

LOG:

Ryan S, Sheila, Syracuse Squad

After Sheila and Ryan turned up the BS oplev laser current more (and no one is climbing on HAM1), we seem to be requiring more successfully.

We got through DRMI_to_POP. To check it was safe, Sheila loaded the LSC POP_A input matrices into the unused XARM filter, and we checked the transfer function from PRCL, MICH, SRCL to the XARM for each input matrix. The PRCL TF looked flat and had 0 phase: good! The other DOFs had a bit of slope and phase but were close enough to 1 that we powered through, and DRMI_to_POP didn't cause any locklosses. It's on our to do list to check the LSC open loop transfer functions.

Then we sat at PREP_ASC_FOR_FULL_IFO and tried checking the phase of the ASC REFL diodes. Sheila++ plugged the LSC AO 2 into the refl servo so we could drive a line in frequency noise, which we want to tune the phasing so it shows up in the I quadrature for each QPD quadrant. I found some handy templates in /opt/rtcds/userapps/release/asc/h1/templates/phasing, complete with excitation. I turned the excitation down to 0.1 and that seemed good. The line was predominatnly in I for each quadrant in REFL_A_RF9 and REFL_B_RF9 EXCEPT Q3 of REFL_B. I imagined I would just tune the phase and see the line go down in Q, but this wasn't the case. It bounced around a bit and was hard to tell if I made progress. Attached screenshot (#1) is with the new phasing.

I accepted the changed phase in SDF, screenshot attached (#2) in case this was a bad move that needs to be reverted.

It seems like we have a 15 minute death (lockloss) timer while we sit at PREP_ASC_FOR_FULL_IFO right now, which is making it hard to get the ASC working, but we'll keep trying...

M. Todd, S. Dwyer

Following the same routine layed out in alog 64204, we had the SR785 already plugged in for a CARM OLG measurement using the gpib from the control room.

I adjusted the carm olg template a tiny bit as it didn't have the right gpib number.

Then I ran

Results:

I measured a 11kHz UGF with a 41 degree phase margin; while this is quite different from previous measurements (2022-07-29) which had something around 27 kHz, I think this is because of the different power states.

TITLE: 05/28 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:
Epochs of locking:
When I first got in to the control room I ran a full Auto initial alignment.
This lead us to no flashes on DRMI & PRMI.
We then manual initial alignment through a few PRX steps.
Which gave us flashes, but after that we had some noise on the beam splitter oplevs.

Then a REFLAIR phase issue was overcame.
Mean while the SQZrs are turning on the laser and did some aligning on the SQZ tables.
Then unknown 70hz feature was later found out to be ISI in HAM1.

The VAC team checked HAM1 for leeks, and didn't find any.


LOG:

TITLE: 05/28 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 14mph Gusts, 3mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY: H1 locking continues this evening; currently have made it up to CARM_TO_ANALOG and have paused to measure CARM OLG. More SQZ table work also going on.

J. Kissel, J. Warner, S. Dwyer, O. Patane, E. Capote, T. Sanchez

After finally making progress past Beam Splitter optical lever glitching (LHO:84631), a poorly phase REFLAIR sensor set for PRMI (LHO:84630), and adding loop gain to the REFL DC centering loops (LHO:84623), we were just about to see some success and made it ISC_LOCK's RESONANCE state.

Alas, Jim started commissioning/debugging the HAM1 ISI loops (in a different room), trying to carve out some time to deal with a ~70 Hz feature in some DOFs of the plant. In doing so he made sure to turn off the DOFs he thought were problematic (RX / RY). LHO:84638

We (including Jim) now know that even only having the X, Y, Z, and RZ loops closed, the ISI HAM1 X loop slowing goes into oscillation slowly, on the order of 5 to 10 minutes after the ISI is isolated.

This manifested in IFO commissioning in very confusing ways mostly because of the timing of events (and the "front row" didn't know that Jim had started commissioning the ISI). The first attachment "shows" this story.
    - The first re-acquisition after an unrelated lock loss started with the ALS COMM's out-of-loop sensor (H1:LSC-TR_X_NORM_INMON) oscillating at 70 Hz, i.e. "looking fuzzy" on the wall "DRMI buildups" screen.
        (See bottom, 5th panel.)
    - It started to dissipate in the middle of this acquisition (we now know because Jim was independently cycling the ISI Isolation loops)
        (See 4th panel)
    - But by the time that DRMI was locked, the "fuzziness" oscillations started to reappear.
        (again, see 5th panel)
    - All the while we notice that MC2's M2 stage -- feedback for the IMC -- is saturating. This in itself is confusing because our impression is that the IMC F / IMC L cross-over is at ~15 Hz, so "there shouldn't be any drive from the IMC common mode board to MC2 up there, especially not offloaded to the M2 stage."
        (see 2nd and 3rd panels)
    - But also, "why is the IMC seeing any HAM1 motion?"

I also attach an ASD of IMC F, the middle stage of MC2's DAC drive, and the HAM1 and HAM2 ISI motion. These clearly show the 70 Hz feature, and show nothing in HAM2.
I call out the "nothing in HAM2" to dispel the suspicions that vacuum equipment that's still vibrating and moving the HAM1 / HAM2 chambers is causing this noise. It's not. It's the oscillation in the ISI HAM1 loops.

Here's why "the IMC is seeing HAM1 motion:" at this point in the lock acquisition, ALS COMM is inserted as an additive offset to the IMC's Common Mode board, which drives MC2 length and the PSL frequency (see e.g. the difference between pg 12 and 13 of G1400519). This is why the MC2 M2 DAC request is peanuts when the IMC is locked alone, but then is gigantic once the ALS COMM signal is ramped in to push the laser frequency around to find the X arm resonance in IR. The ALS beam is "caught" in HAM1 with a periscope and steered around the table before being sent on to ISCT1. So the unstable 70 Hz motion in the new HAM1 ISI is imprinted there on the beam, which is then used to inform ALS COMM, which is then fed to the IMC.

For now, we're going to leave the HAM1 ISI loops off and carry on with ISI commissioning, and give Jim some dedicated time to figure out the issues with the ISI.

J. Freed

Contiuning the work from 84198 this alog is about characterizing the other components of the Double Mixer. D2400315

D2400296 PCB Board transimpedance amp

According to oscilloscope, the signals coming from PCB board are from J2 being cos and J3 being sin. The Vpp are 1.199V on J2 and 1.195V on J3. As before the phase measures are hard to get a read on as the phase measuremnt on the osciloscope says 90deg when I put J3 in the channel 1 position and 91deg when I put J2 in the channel 1 position. Instead I put a 4096 Hz signal generator on Channel 2 then put the of the sin and cos signals on channel 1.

ZLW-1BR Mixer

The mixer data was collected at a range of values incase LO input power needed to be changed, however I would not recomened going below 4dBm LO as the isolation of all the ports falls gets worse the lower the power. The indivitual signals were colected on the Agilent 4396B with a BW of 10 Hz (best one the spectrum analizer allowed without giving an overload notification). While the Total power was given on the E4418A power meter. SRS SG382 was used for the LO power.

ZMSC-2-1BR Combiner

The combiner values were colected by using the Agilent 4396B to apply a sweep of values around 80 MHz. All values were the same in about a 10kHz span that was measured

ZMDC-10-1+ Couplier

The couplier was characterized by applying a -1dBm from a SRS SG382 signal generator signal at 80MHz on the input port and reading off from the E4418A power meter. The other port not being measured was terminated. We do not care about relative phase so it was not collected

Camilla, Vicky

We found the PSAMS servos on ZM2/4/5 were railing (initially set up in 80685), so we reset them and tried to make it more robust for next time. What we did:

• Turn servo gains to 0
• Clear history on filter banks (ran into this problem before already 81697)
• In the filter banks, we changed the integrator "p0" to have Input = Zero History, Output = Ramp, and Ramp Time = 10 sec. At first we were having an issue that turning the filter bank gains to 1 caused the PSAMS servos to slam on and saturated the limiters. Having the 10-sec ramps on both the "p0" filter output and on the filter bank helped. We have previously lost lock  by slamming on the PSAMS servos so hopefully this helps in general. We SDF'd the 10-sec ramp times to both safe.snap and observe.snap.
• Turn servo gains to 1

Then all PSAMS servos were fine. Camilla re-adjusted the ZM2,4,5 osems alignments to set alignment back to yesterday 84593.

I haven't had time to post this because of the wind fence work, but I haven't been able to finish the commissioning of the HAM1 ISI because of a 70-ish hz feature in mostly the X and RZ plants. I didn't see or appreciate how large this 70hz feature was in my close out measurements before doors went on, and it's making the loop design very difficult. I was trying to notch the loops to make the ISI work, but 70hz is very close to the nominal 30hz loop ugf. The X,Y,RZ and Z loops are marginally stable right now, and the  70hz feature gets injected into the IMC when ALS is locked. I think that I can get the loops working, but probably with less gain than we would otherwise get.

Attached PDFs are the loops currently installed, the ISI is set to not use the RX and RY loops, but the X loop is probably ringing at 70hz when the ISI is isolated. We are currently running with just the damping loops though.

Georgia, Kevin, Camilla

Julia and I turned on the SQZ laser, PMC locked fine but the SHG PZT was railed high, Daniel needed to reduce H1:SQZ-SHG_SERVO_SLOWMON offset from 10V to 0V, it then locked fine too. I touched SHG polarizations to reduce SHG fiber rejected power.

Trended ZMs and FC1 top mass alignment. Adjusted ZM2P, ZM4P, ZM5P, FC1P and FC1Y as these were more than ~10urad from the last time in NLN. 

Started following last time we aligned Homodyne in 82153

Turned up SEED injected power from 0.7mW to 70mW.

We went out to SQZT7 and the beam was on the diodes adn there was fringing, we increased LO power to match SEED power using pico-waveplate. WE then adjusted the LO beam with SEED beam blocked to improve the subtraction: Checked we were centered on PDA/B using the steering mirrors downstream of the HD BS and then measured the HD DIFF spectrum. Adjusted BS, re centered on HD PDs and re-checked DIFF ndscope (spectrum of shot noise was noisy at low frequency, then repeated until we were close to zero on the DIFF channel.

Sheila, Elenna

I have commissioned the DC centering on the POP X WFS. This uses DC6 pitch and yaw. I made OLG measurements of both loops, setting them to have a UGF around 0.5 Hz. I had to add additional loop gain to get this UGF, similar to the REFL WFS centering.

Measurements saved in [userapps]/asc/h1/templates/DC_centering

Sheila is adding this centering loop to the ISC_DRMI guardian to engage when we lock DRMI.

We should probably also add "PM1 [P/Y] clear" buttons to the DC centering page.

I also edited the ISC_DRMI guardian to clear teh PM1 suspension when it goes to Down.

These alogs also contain relevant information regarding the PM1/DC6 control:84610, 84623, 84579

Georgia, Camilla, Kevin, Caroline, Julia

We did a few things to prepare for Kevin's ADF measurements. 

Refrencing the SQZT0 March 2024 Layout...

On SQZT0, we moved SHG Trans. camera back a few inches, we also noticed weird behavior with the camera: when the beam was on the camera it was black, but saturated when the beam wasn't on. 

We unblocked the LO path and aligned BS5 to get the beam on PD 1611. 

Camilla aligned the beam on on PZT 2 (used to control LO phase). 

We walked the beam with MR11 and XMR8 to maximize the power through the LO fiber. Going into the collimator, we had 7.3 mW. Coming out of the fiber after the collimator, we had 3.0 mW of power, then 1.9 mW out of the fiber going into the SQZT7 fiber patch. 

We then decided to clean the fiber tips, including those going into and out of the SQZT0 patch, and the fiber going into the SQZT7 patch, which didn't make a difference in the power. 

After adjusting the strain on the fiber, we had 1.45 mW of power out on SQT7.

We're now ready to set up the balanced homodyne using the SQZ LO independent of the PSL. 

J. Kissel, S. Dwyer

As opposed to the ''glitch'' I reported this morning (LHO:84622) which was while the IFO was configured in PRX and ISC loops created a large pitch excursion with M1 drive of the H1SUSBS. We're now seeing stuff that is much more "classic optical lever glitching" with the IFO configured in PRMI, with MICH ASC engaged. See attached. This is after Sheila/Camilla increased the current in the BS oplev laser this morning (LHO:84616)

As a reminder, Beam Splitter optical lever loops are only used in PRMI / DRMI until MICH ASC is turned on. The transition happens in the ISC_DRMI guardian, in the "ENGAGE_DRMI_ASC" (index 80) state; the gain in the ASC-MICH banks are ramped ON in 2 seconds, and the gain in SUS-BS_M2_OLDAMP banks are ramped off with a 20 sec ramp (i.e. it's not that the inputs or outputs are switched on or off).

So, beam splitter optical lever glitching had been particularly painful in the past few days when working in PRMI and/or DRMI without the corner ASC loops on. But, now that we've found a good alignment, and fixed the REFLAIR phase (LHO:84630) we're able to quickly transition to using DRMI ASC, and become insensitive to the optical lever performance -- which continues to glitch.

Ryan S., Sheila, Elenna

First thing Wednesday morning: run full initial alignment with green cameras

Ryan and I were able to lock the IFO on DRMI after many hours struggling down rabbit holes. In short: we were able to finally lock DRMI after reverting the ITMX and ITMY alignment to the alignment on Friday, and running manual initial alignment.

Sheila came online while we were in DRMI checking various things, and together we made it to CARM on Resonance. The alignment was very good (mostly hand tuned except for MICH ASC and DHARD). Sheila and I did our usual check of the PRG following alog 62110 and confirmed that everything looks great.

From there, Ryan and I ran the green camera offset scripts, watched them converge, and set the camera values. These are all SDFed- Ryan will add screenshots. To reiterate: run full initial alignment!

Sheila will add comments about checking and fixing the REFL phases.

While Sheila was adjusting the REFL phases so we could go to CARM on analog, I tried setting up the POP X centering using PM1 (so we could do DRMI on POP). I confirmed that moving PM1 moves the beam on POPX in reasonable ways. I had to flip the DC centering sign to positive when I engaged the loop, DC6, so the centering would converge. I was trying to check the UGF of the DC6 pitch loop by adding an offset to the loop, and accidentally added a massive offset, which tripped a lockloss since the beam went crazy on POPX and therefore LSC POP and that's a lockloss trigger diode.

I also had to turn on the PM1 signal output from the ASC model, which I then SDFed. After lockloss, the PM1 locking output doesn't get cleared, so Sheila will add that to the list of suspensions to clear after lockloss.

Calibration is currently regenerating the O4b uncertainty budgets.

Due to a missed change to the ETMX UIM suspension filters, which was found in LHO alog 82804, and then fixed only on Feb 27, 2025 (see LHO alog 83088), we need to add a correction TF to be included in the uncertainty budgets.

I attach a graph of that correction TF (corrected model / original model) and the text file needed for that correction.

We will be using correction TF in all our uncertainty budgets for O4b, and up to Feb 27, 2025 around 20:00 UTC, or GPS 1424721618 for O4c.