TITLE: 07/12 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 3mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY:

• We've been locked and observing for 4:20, since 10:17 UTC
  • The lockloss overnight (08:24 UTC) was from an earthquake
• Lots of earthquakes overnight
• Range is ok, SQZing doesn't look the best from the trace on NUC33

TITLE: 07/12 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Mostly uneventful evening, but after the lockloss while trying to relock (hadn't done an IA), DRMI unlocked twice while we were in ENGAGE_DRMI_ASC, and got beamsplitter saturations both times, with the second time also getting a BS ISI saturation (1st time ndscope, 2nd time ndscope). Not sure what that was about, as I ran an IA and when I tried locking again it was fine. After being in Observing for a little bit I decided that I wanted to adjust sqz because it was really bad, and I had some issues after running it the first time (clicked things out of order even though it shouldn't matter??), but eventually I was able to get a lot more squeezing and a much better sensitivity at the higher frequencies.
LOG:

23:00 Relocking and at PARK_ALS_VCO
23:35 NOMINAL_LOW_NOISE
23:42 Started running simulines measurement to check if simulines is working
00:05 Simulines done
00:13 Observing

00:44 Earthquake mode activated due to EQ in El Salvador
01:04 Seismic to CALM

04:32 Lockloss
Relocking
    - 17 seconds into ENGAGE_DRMI_ASC, BS saturated and then LL
    - BS saturation twice in ENGAGE_DRMI_ASC, then ISI BS saturation, then LL
05:08 Started an initial alignment
05:27 IA done, relocking
06:21 NOMINAL_LOW_NOISE
06:23 Observing

06:38 Out of Observing to try and make sqz better because it's really bad
07:24 Observing                                                                                                            

Lockloss @ 07/12 04:32 UTC

Thu Jul 11 08:11:57 2024 INFO: Fill completed in 11min 53secs

late entry from this morning

Observing at 157Mpc and have been locked for 3.5  hours. We rode out a 5.2 earthquake from El Salvador earlier. Wind is low and going down.

Jennie, Sheila, Camilla

Last all done in March 76623,76323,  Jitter taken in June 78554. Committed to ligo/gitcommon/NoiseBudget/aligoNB/aligoNB/H1/couplings and on aligoNB git.

Followed instructions in 70642 (new dB, see below), 74681 and 74788. We left CARM control just on REFL B for all three of these injections sets so that Sheila can create the 78969 projection plots.

• Laser Frequcny noice simular compared to March, slightly different shape <100Hz. Intensity coupling still low, discussed increaing gains in 76339, but didn't.
• Jitter: still peaks up to DARM level 100-200Hz. Worse <80Hz compared to June, but still factor of 10 below DARM there.
• Full NB (MICH,PRCL,SRCL updated 78782)

Adjusting  70642 for Switch CARM control from REFL A+B to REFL B only:

• REFL A and B both have 3dB digital gain with 60W
• Via sitemap > LSC > REFL Servo, step down 1dB on REFL A and up 1dB on REFL B until the REFL A gain is -3dB and REFL B gain is 9dB
• Step down REFL A gain down to -32dB 
• Turn off the input 1 switch (REFL_SERVO_IN1EN) for REFL A

Notes on plugging in the CARM CMB excitation for frequency excitation. In PSL rack ISC-R4, Plug the BNC from row 18 labeled AO-OUT-2 into the D0901881 Common Mode Servo on Row 15: EXC on Excitation A.

TITLE: 07/11 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 14mph Gusts, 12mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY:

Currently relocking and at MOVE_SPOTS. Everything looking good

TITLE: 07/11 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Oli
SHIFT SUMMARY: We had a large and close 6.5M earthquake off the coast of Vancouver Island stop us from observing for most of the shift. This earthquake tripped all of the ISIs, but the only suspensions that tripped were IM1, SR3, SRM. Getting back was fully auto(!), expect for untripping WDs and some stops to allow for SEI testing. The delayed commissoining was then coordinated with LLO to start at 2030 UTC (130pm PT). A lock loss happened 1.5 hours into commissioning, the cause seeming to be one of those ETMX wiggles again. Relocking now has been full auto with an initial alignment so far.
LOG:

• 1510 Lock loss, earthquake from Canada
• 1934 Observing
• 2030 Out for coordinated commissioning
• 2154 Lock loss

We were only about 2 and half hours into lock when I did this test due to our earthquake lockloss this morning.

I ran the

python auto_darm_offset_step.py

in /ligo/gitcommon/labutils/darm_offset_step

Starting at GPS 1404768828

See attached image.

Analysis to follow.

Returned DARM offset H1:OMC-READOUT_X0_OFFSET to 10.941038 (nominal) at 2024 Jul 11 21:47:58 UTC (GPS 1404769696)

DARM offset moves recorded to 
data/darm_offset_steps_2024_Jul_11_21_33_30_UTC.txt

I tested out two changes to H1_MANAGER today:

• It will no longer restart initial alignments if the node is engaged from IDLE.
  • This was a problem between shifts or if people are just transitioning from using the node. It worked on my testing today during earthquakes and during another relock today
• If in the state Assistance_Required, it will attempt main locking if initial alignment finishes.
  • Previously, it would stop at the end with the thought that someone would move it along, but we have run into this a few times where people haven't cleared the Assistance_Required state in fear of restarting an initial alignment or just forgetting about it.

Lock loss 1404770064

Lost lock during commissioning time, but we were between measurements so it was caused by something else. Looking at the lock loss tool ndscopes, ETMX has that movement we've been seeing a lot of just before the lock loss.

Ibrahim, Oli

Attached are the most recent (07-10-2024) BBSS Transfer Functions following the most recent RAL visit and rebuild. The Diaggui screenshots show the first 01-05-2024 round of measurements as a reference. The PDF shows these results with respect to expectations from the dynamical model. Here is what we think so far:

• Results are less coherent in certain orders of magnitude, namely L, P, Y.
• The percieveable roll we have not fixed in M3 does not seem to change the Roll TF measurement
• The F3 OSEM sways more than the others as a response to the TF excitations and is in general, more reactive than the others (attached gif)
• Pitch has unexpected and shifted peaks, which seem to cross couple into the other TFs
• Most percieveeable in Y, there is increased signal noise from around 1.5-6hz
• The F1, LF and RT OSEMs have drifted from their nominal centered positions (this will be a seperate alog).

Thoughts:

The nicest sounding conclusion here is that something is wrong with the F3 OSEM because it is the only OSEM and/or flag involved in L, P, Y (less coherent measurements) but not in the others; F3 fluctuates and reacts much more irratically than the others, and in Y, the F3 OSEM has the greatest proportion of actuation than P and a higher magnitude than L, so if there were something wrong with F3, we'd see it in Y the loudest. This is exactly where we see the loudest ring-up. I will take spectra and upload this in another alog. This would account for all issues but the F1, LF and RT OSEM drift, which I will plot and share in a seperate seperate alog.

We're running a patched version of simuLines during the next calibration measurement run. The patch (attached) was provided by Erik to try and get around what we think are awg issues introduce (or exacerbated) by the recent awg server updates (mentioned in LHO:78757).

Operators: there's is nothing special to do. just follow the normal routine as I applied the patch changes in place. Depending on the results of this test, I will either roll them back or work with Vlad to make them permanent (at least for LHO).

The following settings seems to be working for now and I will commit it in the lscparams after a couple of IFO lock stretches.

New settings (ITMY05/06):- FM5 FM6 FM7 FM10 Gain +0.01 (new phase -90 degree), might increase the gain later on depending upon how slow the damping is.

Nominal settings (ITMY05/06): FM6 FM8 FM10 Gain +0.02 (phase -30deg)

Given below are settings I tried this morning and it did not work,

1. no phase, 0.01 gain - increase
2. -30 phase, -0.01 gain - increase
3. +30 phase, 0.01 gain - increase
4. -30 phase, 0.01 gain - IY05 decreasing (both filters) IY06 increasing (both filters)
5. -60 phase, 0.01 gain - IY05 decreasing (both filters) IY06 increasing (only in narrow filter)

---

After talking to TJ, I have set the gain to zero on lscparams and saved it but not loaded it since we are OBSERVING. Will load it once there is a target or opportunity.

[Dave, Erik]

Dave found that DACs in h1sush2a were in a FIFO HIQTR state since 2024-04-09 11:33 UTC.

FIFO HIQTR means that DAC buffers had more data than expected.  DAC latency would be proportionally higher than expected.

The models were restarted, which fixed the issue.