Jennie W, Sheila, Camilla

I looked at the results of the A2L tests from the weekend for ETMY, ITMX and ETMX.

For ETMY the steps seem too small / A2L gain changing has little effect on the power recycling (LSC-POP-A and ASC-POP_NSUM), build-ups (ASC-{X,Y}_PWR), range (MPC range channel and BLRMS channels) or optical gain (KAPPA C). See first image.

More of a difference can be seen in the arm build-ups and PRG for ETMX. The best value for P2L looks like 4.4 as this maxmises the arm power and PRG, while the best range is for a Y2L of 4.6. See second image.

Y2L gains for ITMX seem to already be at their optimised value in terms of arm build-ups and power recycling, however the range improved slightly when the P2L gain was at  -0.4. See third image.

In summary maybe we need to retune ETMX and ITMX A2L gains a bit, but for ETMY it doesn't seem to gain us much.

See comment from Elenna below, we will run these again as per this entry.

Sheila, Daniel, Naoki, Nutsinee

This morning OPO failed to lock because our green launch power was too high. As of this morning the OPO guardian will take itself to DOWN when the power reaches above 35mW. Though this doesn't stop SQZ_MANAGER from re-requesting OPO to lock even if the pump ISS fails repeatedly (because SHG launch power was too high). Daniel also cranked up the OPO PZT offset to 10V using CLF slow offset to lower the lock point of the OPO PZT.

We made a few rough adjustments to the OPO guaridan:

1) In the ENGAGE_PUMP_ISS if ISS fails up to 20 times it will take itself to DOWN.  Injecting squeezing with no pump ISS means bad squeezing. Squeeze level will drift. Squeeze angle will drift. We shouldn't inject bad squeezing into the interferometer.

2) If the SHG launch power is higher than 35mW the flipper will close and the guardian will take itself to DOWN. The point of this statement is to protect the fiber. We should close the flipper.

3) We added two functions and two GuardStateDecorator.  GRLAUNCH checker lives in DOWN state and @ISS_checker lives in PRE_LOCK_CLF. If SQZ_MANAGER tries to take OPO to lock when these bad conditions are still true, OPO will refuse to go up and stays in DOWN.

The code has been loaded into the OPO Guardian. We still see to make SQZ_MANAGER put out nofification as well. For now the notifications live in the OPO guardian.

J. Kissel, L. Dartez
ECR E2400103
IIET 30760
WP 11786

To better coordinate and confirm the front end portion of the calibration pipeline and the GDS portion running on the DMT machines remain in sync in terms of calibration model installed, which is necessary for good calibration, we are adding two slow 16 Hz EPICS channels to the h1/l1calcs models (so both LLO and LHO) that will be added to the GDS broadcaster list so the GDS calibration pipeline can read them. These are H1/L1:CAL-CALIB_REPORT_ID_INT and H1/L1:CAL-CALIB_REPORT_HASH_INT.

Louis and I created the top-level EPICs records today; see attached screenshot.

The change has been committed to the userapps SVN under:
    /opt/rtcds/userapps/release/cal/h1/models/
        h1calcs.mdl          committed at rev 27307.


It's in no way a complicated add to the model, but I've ran a test compile of the h1calcs.mdl on the build machine anyways just to check. The test compiled succeeded without issue.

Mon Mar 25 10:09:43 2024 INFO: Fill completed in 9min 39secs

Jordan confirmed a good fill curbside.

I used two hours of quiet data over the weekend to compute coherences of DARM with all channels with a bandwidth of 0.5 Hz, meaning about 7200 averages. The goal was to look for coherences in the high frequency (>100 Hz). Nothing there except residual jitter coherence (I'm using GDS-CALIB_STRAIN_CLEAN)

https://ldas-jobs.ligo-wa.caltech.edu/~gabriele.vajente/bruco_1395364856_GDS_CALIB/

Same time period, with a bandwidth of 0.1 Hz, and about 1800 averages

https://ldas-jobs.ligo-wa.caltech.edu/~gabriele.vajente/bruco_1395364856_GDS_CALIB_0.1Hz/

Notable at low frequency: CHARD_P, CHARD_Y, DHARD_Y, SRCL

Ryan took the IMC offline after a lockloss so that we could measure dark noise.  The attachment shows that there is a change in the location of the lump from 40Hz to 60Hz.  Jeff pointed me to this alog: 68377 where he previously saw this moving around.

Other than that, there is little change in the dark noise, if anythingit is slightly better now than before the OMC swap from 100-300Hz.

This is in the Noise budget repo: /ligo/gitcommon/NoiseBudget/aligoNB/aligoNB/H1/couplings/Reference_noises.xml

Now we have improved low frequecny, I've attached a new version of the H1 summary pages range ASD plot from 76349, comparing December 20th 2023 in Red (SQZ/noSQZ in 76537) to  March 25th today in green  (25th March).

 Everything below 40Hz is better than December. Everything 40 -500Hz is worse

FAMIS 20021

PMC_TRANS and FSS_TPD have been dropping over the past several days while PMC_REFL has been rising.

Previously done 76151 - closes FAMIS#27785

TCSX was at 29.5, so I added 290mL of water to get it to 30.

TCSY was still at max, so I did not add any water.

There was no leaking.

TITLE: 03/25 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 2mph Gusts, 0mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.35 μm/s
QUICK SUMMARY: H1 has now been locked at NLN for 32 hours. SQZ just unlocked (looks the the OPO PZT railed), Sheila and I are debugging.

• Wind is low, microseism is starting to rise
• All other systems nominal

TITLE: 03/25 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
INCOMING OPERATOR: (None) Remote txt2 Sheila.
SHIFT SUMMARY:
H1 has now been locked for 24 hours!
Currently Observing after surviving a few mag 5 earthquakes.
Quiet night, everything seems to be running smoothly!

LOG:
No Log

FAMIS 26289
Out side of that glitch I dont see an increase in noise on any of the fans.

Zooming in on the Glitches I found that the glitches were minutes apart and not actually at the same time yesterday.

TITLE: 03/24 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 13mph Gusts, 11mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.23 μm/s
QUICK SUMMARY:
H1 Is locked an Observing for 16.5 hours.
H1:PEM-CS_DUST_PSL101                    Error: data set contains 'not-a-number' (NaN) entries

All three IFO's are locked and Observing.
Everything looks good.

TITLE: 03/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY:

• 13:00 - ETMX A2L stepper script started (scheduled)
• 17:00 - ETMX A2L stepper script finished
• 17:03 - ITMX A2L stepper script started; dropped observing
• 21:03 - ITMX A2L stepper script finished
• 21:05 - To NLN_CAL_MEAS for calibration sweeps
• 21:38 - Calibration sweeps finished; back to NLN and resuming observing

LOG:

No log for this shift.

Following instructions from the TakingCalibrationMeasurements wiki, this afternoon I ran both broadband PCal and Simulines measurements.

Sun Mar 24 10:11:41 2024 INFO: Fill completed in 11min 37secs

Code located in /ligo/gitcommon/labutils/beam_spot_raster/a2l_gain_stepper.py

Current spot positions (e.g. H1:SUS-ITMX_L2_DRIVEALIGN_P2L_SPOT_GAIN):

It will step the nominal values up and down 0.4 in 0.2 steps / 15 minutes. e.g. starting a2l + [-0.2, -0.4, -0.2, 0, 0.2, 0.4, 0.2, 0]

I've set up a script to run this on ETMY at 6am to 10am tomorrow (23rd) in a tmux session on cdsws26, will only run if the IFO is at NLN (>=600)  at 6am.

Ryan S will try to find times (4 hours each) to run this on the other optics ITMX and ETMX over the weekend, command below. We don't have beam spot control on ITMY so can skip that.

>> python /ligo/gitcommon/labutils/beam_spot_raster/a2l_gain_stepper.py ETMY --start 'now'

Oli P, Jeff K

As a continuation of the SUS model updates (76269), yesterday I updated the models, medms, and watchdog filter banks for the ITMs and BS. Everything looks to be functioning as intended. Changes made are basically the same as what was done for the ETMs and TMSs, with the exception of the pi model for the ITMs(attachment1). I will list the model files that have changed:
SUS
- QUAD_ITM_MASTER.mdl
- h1susitmx.mdl
- h1susitmy.mdl
- h1susitmpi.mdl
- BSFM_MASTER.mdl
- h1susbs.mdl
ISI
- h1isiitmx.mdl
- h1isiitmy.mdl
- h1isibs.mdl
The OVERVIEW and WD medm files have been updated for each suspension, there has been the addition of a new filter bank within the WD screen to accomodate for the addition of the RMSLP put into the WD models, and these filters, along with the BANDLIM filter banks, have been updated with the correct filters. SDFs have been accepted for safe(attachment2) and OBSERVE(attachment3). All changes are in svn.

A PCAL End station measurement was performed at End Y today. Analysis Pending.

Also Fil and I went back to EY to test the PCAL Temperature channels.
This time Fil and I went down and Turn ON the PCAL enclosure bypass and then pulled the PCAL cable out of the back of the PCAL Enclosure bypass Chassis.

GPS Time 1394909058

The ndscope of these channels did not appear any cleaner when we unplugged the PCAL cable out of the back of the PCAL Enclosure bypass Chassis.
The ndscope of these channels did not appear any cleaner when we unplugged the Rx Module Temperature cable from the front of the PCAL Chassis. But the Rx Temp did go to 0.
The ndscope of these channels did not appear any cleaner when we unplugged the Tx module Temperature cable from the front of the PCAL Chassis. But Tx Temp did go to 0.