We ran the a2l_min_multi_pretty.py script again today since we made changes to the OMC offsets (alog83087). There were minimal gain changes, the only one I updated in lscparams.py was ETMY P from 5.49 -> 5.52.

The range coherence template we normally use was giving odd results during the quiet commissioning times after the OMC reverting, no coherence above 20Hz is seen. Sheila mentions that this is something she has seen before and isn't physical. We ran the script expecting changes but didn't see much change in gains or to the range.

RESULTS

|      |   | Initial | Final |  Diff |
| ETMX | P |   3.23  |  3.24 |  0.01 |
| ETMX | Y |    4.9  |   4.9 |   0.0 |
| ETMY | P |   5.49  |  5.52 |  0.03 |
| ETMY | Y |   1.35  |  1.34 | -0.01 |
| ITMX | P |  -0.53  | -0.54 | -0.01 |
| ITMX | Y |   3.21  |  3.22 |  0.01 |
| ITMY | P |   0.06  |  0.05 | -0.01 |
| ITMY | Y |  -2.74  | -2.75 | -0.01 |
 

We've been having some issues with SRC2 P starting to go unstable after engaging for DRMI (alog83080, alog82997). Ryan C tested out lower the gain from 60 -> 40 on Sheila's suggestion yesterday and it seemed to work (alog83078), and I also bashed it in during a relock today that started to go unstable. Since this seems to work and the gain is brought back to 60 later in ENGAGE_ASC_FOR_FULL_IFO, we've made the change in ISC_DRMI and loaded the guardian.

J. Freed

ETMY shows strong coupling of BOSEM noise between 9-14Hz by about a factor of 20 below DARM from most sensors.

Today I did damping loop injections on all 6 BOSEMs on the ETMY M0. This is a continuation of the work done previously for ITMX, ITMY, PR2, PR3, PRM, SR2, SR3, SRM, and ETMX. As with PRM, gains of 300 and 600 were collected for SR3 (300 is labled as ln or L).  Calibration lines were off. Data was colected in two parts, as such, f1,f2,f3 had a different background than lf,rt,sd bosems.

Jennie W, Sheila

Since our range has been decreasing over the last week and the OMC QPD offsets did not definitely give us a clear gain long term in kappa C, we have reverted the change we did on Monday.

We might want to improve these offsets again once we sort out any other problems that are making larger impacts on our range currently.

See the below ndscope for how this affected the range and optical gain in the short term - this picture is slightly confusing as the calibration was being updated so kappa C will have been reset at the some point before or during our measurements.

The other two attached images show the QPD offsets being accepted in OBSERVE and SAFE snap files.

Thu Feb 27 10:05:41 2025 INFO: Fill completed in 5min 38secs

For this fill I tested that the rate-of-change trip value can be changed in the configuration yaml file and then loaded into the code. For this test it was reduced from 60.0 to 50.0 DEGC.

The code which generates the plot now dynamically reads the trip PV to set the horizontal bar.

It looks like we tripped on a TC-A sputter just before the LN2 got flowing, but looks like a good fill.

Lockloss @ 2025-02-27 16:36 UTC during commissioning after 22 minutes locked. People had just entered the LVEA.

Oli, Jonathan, Dave:

The DARM FOM in the control room (running on nuc30) stopped updating and could not be restarted. Jonathan tracked it down to an ongoing NDS2 issue which will hopefully be resolved soon. In the meantime I started the "local" version of this fom which only uses the local NDS and does not try to connect to NDS2.

I'm running the diaggui by hand from a terminal as controls on nuc30, it was started with:

cd /opt/rtcds/userapps/release/cds/h1/scripts/fom_startup/nuc30

diaggui --fom ./H1_DARM_FOM_cds.xml

TITLE: 02/27 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 3mph Gusts, 2mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.72 μm/s
QUICK SUMMARY:

Currently relocking and at CARM_TO_TR

TITLE: 02/27 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: TJ
SHIFT SUMMARY: 1 lockloss and we're on our way back past the troublesome CHECK_ASC now. I had to reduce the gain of SRC2_p from 60 to 40. We're about to start powering up now.
LOG: No log.

• 01:02 UTC superevent S250227y
• 02:44 UTC lockloss
  • I03:28 UTC Held at CHECK_ASC and it started ringing up after a few minutes and we lost lock ~30 seconds later
  • 03:37 UTC Held again and reduced the gain to 40, we could survive as it rung up and down. I ran a few averages of the OLG
    • I put in the wrong gain and we lost lock
  • ALS keeps dropping out during DRMI
  • 05:00 UTC, we're struggling to get DRMI, keep going through PRMI
  • 05:17 UTC after doing PRMI 3 times in a row I dropped to do another IA
  • 05:48 I reduced the gain to 40 and kept going and we seems fine?

Jennie Siva Keita Mayank

Following our previous attempt  here .  We opened a new ISS PD array (S.N. 1202965).
This unit is in great condition. i.e. 

1) No sign of contamination.
2) All the optics are intact (No chipping)

We tried interfacing the QPD-cable S1203257 with the QPD but it turned out that they are not compatible.
We will look for the updated version of the QPD cable.   

02:44 UTC lockloss

Ibrahim, Oli

Attached are the most recent BBSS Model Comparisons with most recent BBSS parameter settings (+/- from FDR):

d0=+3.0mm

l1 = -3.0mm

m2 = +0.3kg

FDR, d1 = +3.5mm (which is equivalent to BP = -4mm)

TITLE: 02/27 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:
LOG:

15:30UTC Relocking
    - ISC_LOCK in PREP_FOR_LOCKING; H1_MANAGER had gone into error less than a minute before (15:29 UTC)
    - I ran an initial alignment
    - We got those saturations again during OFFLOAD_DRMI_ASC (ndscope)
    - Lockloss during LOWNOISE_ESD_ETMX due to earthquake coming in
    - Holding in DOWN until earth settles
    - Started another initial alignment
    - Another set of saturations during OFFLOAD_DRMI_ASC - this time we lost lock from them (ndscope2)
    - Saturations again but got through them this time
18:15 NOMINAL_LOW_NOISE
18:20 Observing

21:16 Commissioning to adjust A2L and PRCL FF

21:51 Back to Observing
22:48 Superevent S250226dl
00:13 Superevent S250227e                                                                                                                                                                                                                                                                                                                                               

TITLE: 02/27 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 143Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 11mph Gusts, 6mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.43 μm/s
QUICK SUMMARY:

• We've been locked for almot 6.5 hours
• Wind is low, 2ndary microseism looks be to slightly rising

Sheila, Matt, Camilla

We aligned and took some SQZ HD data this morning but realized that the ZM optics were noisy with HAM7 tripped and the increased (60mph!! wind). After un-tripping HAM7, Matt and Sheila rechecked balancing and visibility, started at 98.3% but noisy, improved to 99.0%. Since then HAM7 tripped and was un-tripped again but assumed nothing would have changed.

NLG Measurements:

Data saved to camilla.compton/Documents/sqz/templates/dtt/20250225_GOOD_HD.xml

FC2 is misaligned during this dataset.

[Vlad, Louis, Jeff, Joe B]
So while exercising the latest pydarm code with an eye towards correcting the issues noted in LHO alog 82804, we ran into a few issues which we are still trying to resolve.

First, Vlad was able to recover all but the last data point from the simulines run on Feb 15th, which lost lock at the very end of the sweeps.  See his LHO alog 82904 on that process.

I updated the pydarm_H1.ini file to account for the current drive align gains and point at the current L1SUSETMX foton file (saved in the calibration svn as /ligo/svncommon/CalSVN/aligocalibration/trunk/Common/H1CalFilterArchive/h1susetmx/H1SUSETMX_1421694933.txt ).  However, I had to also merge some changes for it submitted from offsite.  Specifically https://git.ligo.org/Calibration/ifo/H1/-/commit/05c153b1f8dc7234ec4d710bd23eed425cfe4d95, which is associated with MR 10 which was intended to add some improvements to the FIR filter generation.

Next, Louis updated the pydarm install at LHO from tag 20240821.0 to tag 202502220.0.

We then generated the report and associated GDS FIR filters.  This is /ligo/groups/cal/H1/reports/20250215T193653Z.  The report and fits to the sweeps looked reasonable, however, the FIR generation did not look good.  The combination of the newly updated pydarm and ini changes was producing some nonsensical filter fits.  This is the first attachment.

We reverted the .ini file changes, and this helped to recover more expected GDS filters, however, there's still a bit of a small ~1% change visible around 10 Hz (instead of being a flat 1.0 ratio) in the filter response using the new pydarm tag versus the old pydarm tag which we don't understand quite yet, and would like to before updating the calibration.  I'm hoping we can do this in the next day or two after going through the code changes between the versions.

Given the measured ~6 Hz SRC detuning spring frequency (as seen in the reports), we will need to include that effect in the calcs front end to eliminate a non-trivial error when we do get around to updating the calibration.  I created a quick plot based off the 20250215T193653Z measured parameters, comparing the full model over a model without the SRC detuning included.  This is the attached New_over_nosrc.png image.