Lockloss during comissioning time at 17:52UTC, 1 issue relocking which was due to the alignment not being the best.

We just returned to Observing at 19:31 UTC, I accepted SDF diffs for Sheilas SCRFF gain and Y2L measurements.

18:21 UTC, SRM saturation then LL. The ASC loops were not done working when GRD advanced us to turn on BS_STAGE2

HEPI HAM1 watchdog trip, ACT. Potentially from a jack being used in the optics lab

https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1398707582

I adjsuted the gain of the SRCLFF filter while running a SRCL injection to reduce the coupling to DARM.  (Screenshot attached). I've add the gain of 1.15 to the lscparams file so that the guardian will use this gain in future locks.

This is similar to what Gabriele did in 77492, and the calibration of traces in his screenshot is the same as mine (they are made using the same template.)  Gabriele's "new FF" (red trace, -160 dB at 30 Hz) is giving worse performance today, shown by the blue trace "Old FF" in my plot, (-145dB at 30 Hz).

So it seems the SRCL FF gain that we need has changed quite a bit.  This may be because of the OMC alignment offsets that Jennie Wright added to improve our optical gain in 77543

Thu May 02 10:15:33 2024 INFO: Fill completed in 15min 29secs

Gerardo confirmed a good fill curbside.

We've started comissioning which will run from 16:00 - 19:00 UTC (9am - 12pm PST). Some of the plans include, SQZ tuning, PEM injections, SRCL FF, and Y2L.

TITLE: 05/02 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 4mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

• We've been locked for 8.5 hours, in Observing since 06:30UTC
• We rode through some earthquakes this morning, 4.7 - 5.5s from the Aleutian islands of Alaska and some of similar magnitudes from the Sandwich islands
• Microseism is still trending down, low wind
• The LVEA is still in laser hazard

TITLE: 05/02 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: During relocking we were able to catch DRMI without needing to go through PRMI, but had locklosses from ENGAGE_DRMI_ASC and TURN_ON_BS_STAGE2 before I started an initial alignment. During initial alignment we couldn't get past WFS_CENTERING_SRY, so I just took us out of IA and started relocking. LVEA is still in LASER HAZARD.

LOG:

22:49 Detector Locked for 2 hours
00:10 Dropped Observing to run SQZ and regular calibrations
00:19 Went to NLN_CAL_MEAS for calibration measurements
00:30 Earthquake mode activated
00:50 Back to NOMINAL_LOW_NOISE and Observing
01:00 Seismic to CALM

04:59 Lockloss
05:10 Lockloss from ENGAGE_DRMI_ASC
05:18 Lockloss from TURN_ON_BS_STAGE2 - started an initial alignment
05:37 - 05:45 Stuck at SRC alignment
    - Constant SRM, IFO_OUT, SQUEEZE_OUT saturations
    - We weren't able to get past WFS_CENTERING_SRY, so I took us to DOWN
    - Backed out of initial alignment and started relocking
06:27 NOMINAL_LOW_NOISE
06:30 Observing

Lockloss 05/02 04:59UTC

Currently Observing and have now been locked for 6 hours. Wind is calming down

Ran bb calibration measurements and simulines between 05/02/2024 00:10 and 00:50 UTC. *Earthquake mode was activated at 00:30UTC and stayed activated through the rest of the measurements, but I presume should have no effect?

Broadband

Started: 2024/05/02 00:20:20UTC

Output file: /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20240502T002020Z.xml

Simulines

Started: 2024/05/02 00:27:28UTC

Output files:

/ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20240502T002728Z.hdf5
/ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20240502T002728Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20240502T002728Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20240502T002728Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20240502T002728Z.hdf5

Robert, Anamaria

Yesterday we opened the viewports of the oplevs for both ITMX and ITMY to find the alignment of the CP's.
The procedure relies on the fact that the optics are not coated for red so we can see all four surfaces. The separation between the beams at this distance (~34m) is about 10cm due to the wedges (in the table below from the galaxy page). The test mass has a vertical wedge, thick down, so the AR beam will show up directly below. The CP is supposed to be perfectly parallel to the back surface so the closest surface of the CP (CP1) would land essentially right on top of the ITM AR beam. Then the CP has a similar size wedge, but horizontal, so the second CP surface would hit at the same level as CP1 and ITM AR but to the left or right, depending which ITM. 

The first plot attached shows the nominal view of these beams as seen at the oplev viewport on the white page. The yellow pages were attached to the lexand covering the viewport and the beams were marked. The full view of all the beams no longer fits through the viewport due to the addition of nozzle baffles so we had to walk the oplev sender to find all the beams. For the ITMX we lucked out and the ITM AR beam was visible at the top gap of the baffle at the same time as the second AR reflection and the CP beam were visible in the aperture. As such we are able to scale the misalignments to the wedge value. We verified the CP beams by moving the CPs, and we scanned to find the second CP surface (CP2) horizontally at about the right distance from CP1. 

By down I mean they are further pitched down towards the arm.

One would think that we have +/- 440 urad range in pitch on the R0, but it seems its range is much less than advertised. Even stranger, this was also found to be the case at L1, on both ITM R0. When we moved CPY, with respect to this calibration it only moves ~230 urad. So we cannot make it back to the nominal position of overlapping the ITM AR beam. For yaw we did a smaller step so more error on it, but it's about 60% of slider value. More on this later.

(CPY is the one that Robert found to modulate the noise from the MC tube baffle.) Speaking of the L1 experience, we even had to vent back in 2016 to fix one of these CP misalignments, which was too close to HR actually. The interesting thing to me, looking back, is that L1 still has a similar misalignment for CPX to the H1 CPY and we don't see as high noise coupling at the IMC tube. 

CPX is very misaligned by comparison, but not linked to the MC tube scatter. Alena has agreed to help us track where these ghost beams land at P/SR3 and the scraper baffles, now that we know their exact orientation. 

I ran the SCAN_ALIGNMENT with new OMC alignment in 77543 after 3 hours into lock.

Then I ran the SCAN_SQZANG. Compared with the reference in NUC33, the squeezing in the bucket is similar, but the high frequency squeezing is a bit worse with new OMC alignment.

May 02 00:10UTC We just went into Commissioning to run our normal calibration sweep and calibrate sqz

TITLE: 05/01 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 21mph Gusts, 19mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY:

We are Observing and have been Locked for 2 hours. wind is around 25mph but going down.