The ADS gain has been doubled so we can converge the ADS faster and move to camera servos. I updated the ads gains in LSC params to be 20. The LSC params value is used by the ISC_LOCK guardian in Lownoise ASC and by the Camera servo guardian. We should keep an eye on this for the next few locks and check that this doesn't rail the ADS at any point.

We have determined we want to operate with higher carm gain. Instead of slowly increasing the carm gain during thermalization, we decided to try increasing it from the start and avoid causing glitches. The SERVO gain for REFL A and B will both be set to 9 dB instead of 6 dB in LASER NOISE SUPPRESSION.

Jennie, Craig, Erik

I've been having trouble importing functions into python scripts from the labutils packages while on the control room workstations, even while in the labutils conda environment.

For some reason I can still run thermal_state_capture from the command line though...

Just putting this here in case anyone else is having this issue in the future.

The temporary fix (from Erik) is to manually add labutils to your path before activating the environment each time from the command line:

export PYTHONPATH=/ligo/gitcommon/labutils
 

We had a look at the next set of power supplies that likely have siezed fans and we found the following,

EY - All supplies register less than 80 degrees on input with sufficient air flow, no issues.

EX - VDD-1 LHS U12 24V H1-PCAL registers at 115F in the front, lower in the back.  Low temperature gradient & high temperature vs ambient = bad fan

EX - Remaining supplies regiseter 80 degrees no issues.

CER - C2 U34 RHS 92F front, 93F back, hard to feel air flow ISC-C3 -24V S1201927.  Low temperature gradient & moderate temperature vs ambient = bad fan

CER - C2 U30 RHS 90F front 115F back, low air flow, high heat on front mount, ISC-C2 -18V S1201978.  Moderate temperature gradient & moderate temperature vs ambient = failing fan (not failed yet)

CER - C3 U22 RHS 101F front, 104F back, low air flow, SEI-C4 BSC1, S1201989.  Low temperature graidnet & high temperature vs ambient = bad fan

CER - Remaining supplies regiseter 80 degrees no issues.

There are a few supplies in the CER which are not easily measured in the front.  These supplies have obstructed input vents so it is hard to tell if the fan is bad, or the supply is starved for fresh air.

M. Pirello, F. Mera

Closes FAMIS 17558

Both figures look nominal

J. Kissel, E. Goetz

   /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Measurements/FullIFOSensingTFs/
       2023-04-28_1702UTC_H1_PCALY2DARMTF_BB_3min.xml

More later.

J. Kissel, E. Goetz

We have changed and updated CALCS bandpass filters for LINE4, LINE10 so that they could read temporary CAL_AWG_LINES thermalization line (see LHO aLOG 68947) (24.5 Hz) and the X comparison line (410.2 Hz). In addition, we installed bandpass filters on the EXT DEMOD in the PCAL X and PCAL Y comparison demods:
CS_TDEP_PCAL_LINE4_ERR_DEMOD_SIG 0 butter("BandPass",6,24.45,24.55)
CS_TDEP_PCAL_LINE4_EXT_DEMOD_SIG 0 butter("BandPass",6,24.45,24.55)
CS_TDEP_PCAL_LINE4_PCAL_DEMOD_SIG 0 butter("BandPass",6,24.45,24.55)
CS_TDEP_PCAL_LINE10_ERR_DEMOD_SIG 0 butter("BandPass",6,410.17,410.23)
CS_TDEP_PCAL_LINE10_EXT_DEMOD_SIG 0 butter("BandPass",6,410.17,410.23)
CS_TDEP_PCAL_LINE10_PCAL_DEMOD_SIG 0 butter("BandPass",6,410.17,410.23)
CS_TDEP_PCAL_X_COMPARE_EXT_DEMOD_SIG 0 butter("BandPass",6,410.19,410.21)
CS_TDEP_PCAL_Y_COMPARE_EXT_DEMOD_SIG 0 butter("BandPass",6,410.29,410.31)

Also in the PCAL X and PCAL Y comparison demods, we installed the same 300 s low-pass filter to the EXT demod:
CS_TDEP_PCAL_X_COMPARE_EXT_DEMOD_I 0 butter("LowPass",4,0.0033)
CS_TDEP_PCAL_X_COMPARE_EXT_DEMOD_Q 0 butter("LowPass",4,0.0033)
CS_TDEP_PCAL_Y_COMPARE_EXT_DEMOD_I 0 butter("LowPass",4,0.0033)
CS_TDEP_PCAL_Y_COMPARE_EXT_DEMOD_Q 0 butter("LowPass",4,0.0033)

TITLE: 04/28 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 13mph Gusts, 10mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.13 μm/s
QUICK SUMMARY:

• Lost lock at 13:19 UTC, stuck at locking green arms with Xarm locked but Yarm struggling. Will start relocking
• No alarms, low wind, a few FPU lights on the CDS overview
• Lots of Squeeze test points are still open on NUC34 (over 16hours)
• LVEA is still LASER HAZARD

TITLE: 04/27 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Commissioning
SHIFT SUMMARY:

- IFO is locked at NLN, but not in Observing Mode due to unreconciled observe SDFs, attached below, so I am leaving it in Commissioning mode - Tagging ISC

- Lock #1:

• LOCKLOSS @ 03:35 - I believe this one is ground motion related - possible aftershock from EQ?

- Lock #2:

• Held in READY to put it values of ISC EX/Y whitening gains to allow IR to catch (alog here) 
• After caputting all values I am still having issues...this time with the LSC_TR_Y PD not getting any light.
• Tried from the beginning - set the values in READY and this time it was LSC_TR_X not catching...
• Rerequested FAST_SEARCH and COMM was able to catch...DIFF failed again...third times the charm
• After multiple attempts at rerequesting and putting in the values, it finally caught...praying we don't lose lock again
• DRMI failed, but let it run through to CHECK MICH FRINGES and back to PRIMI ASC where it caught and moved up
• Acquired NLN @ 05:57

Other Notes:

- 2:14 UTC - inc EQ from South Georgia - 5.8 mag eq

• We did not go to EQ mode, but I guess we didn't need to? Peakmon highest values were only at 80...interesting, quite low for a 5.6
• Also interesting - @ 2:31 UTC we got a SEISMIC to CALM alert, but no indication that it ever transitioned out of CALM to begin with? Tagging SEI

- 3:25 UTC - EX saturation, IFO was a little unstable, seeing ringups in INP1_P_INMON, MICH_Y_INMON, CSOFT_P_OUT, CHARD_Y_OUT, and DHARD_Y_OUT

• Though I'm probably chalking this up to ground motion, all pickets fence seismometers are lighting up and seeing elevated motion in both seismon DMT plots - maybe an aftershock from the previous EQ?

LOG:                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

All was going well until we had what I believe to be a ground motion related lockloss. Then when reacquiring lock, I ran into the same issue I did last night, despite resetting all the values to their working state from Ryan's alog. I'll keep trying...

EDIT: For sanities sake, I have attached a screen shot of the changes I implemented, which are the exact same as the ones noted in the alog.

EDIT 2: I have also screenshotted the SDF changes to show that they're actually there and that they're the correct channels, but for some reason it doesn't seem to be working.

EDIT 3: On the 5th(6th?) attempt it finally caught, and was able to go up ISC. This might need to be looked into more tomorrow

Thanks to the hard work from everyone at LHO, we have reconciled all observing.snap SDFs and have flipped the intention bit and LHO is now...

officially 🥳 OBSERVING FOR THE FIRST TIME IN O4 🥳

👏👏👏👏🙌🙌🙌

The mode was acquired at 00:53 UTC, Apr 28th and I intend on leaving it in this mode to allow for some offsite data analysis.

Congratulations to all!!

I have added 3 more nodes to the guardian exclude list for tonight.  This is not at all what we want, but they need further thought tomorrow.  This lets us flip the Observing Bit tonight.

The DIAG_EXC node is not happy, since there are 2 calibration lines that it is flagging as going on.  We will have these lines on for at least through our calibration week to monitor the SRCL detuning, but then they'll (I think) be turned off.  So, it's excluded.

Also, the THERMALIZATION guardian needs to be reworked so that it can return OK some time sooner than many hours after we've locked. I've excluded it, and I've also excluded ISC_LOCK since it won't return OK until Thermalization is OK.  We must re think these and fix them tomorrow or ASAP.  For these two, this will be the state of things during the observing run, and we clearly need to be able to set the observing bit earlier than many hours after having locked.

Attached is the list of excluded nodes, with my comments on our needing to deal with these three nodes.

I've accepted the last few SDF diffs we've got.  Some still need review tomorrow, but for the most part I think these are now matching what we have in safe.snaps. 

SDF is now clear, and so we are one major step closer to pushing the Intent Bit!

R. Short, J. Driggers, T. Shaffer

We've learned that the main issue with locking last night and this morning stemmed from whitening gains and gain steps for the TR_A/B channels in the EX/Y_ISC models being accepted as all zeros (see TJ's alog 69103 for details). I've also discovered that the OBSERVE.snap file is in fact symlinked to a SAFE.snap, which means these two tables are the same. We assume someone accepting SDFs at NLN had accepted these to zero not knowing about the linked tables. TJ and I plan to reconcile this issue tomorrow morning and double-check other models that have recently been added to the SDF_REVERT state.

In the effort to be able to use the Observation intent bit tonight -- meaning all SDF differences must be cleared -- I have accepted these differences, knowing they are incorrect for the locking process. If we are attempting to relock before we can fix the table issue, these values must be changed back to the listed setpoints (see attached screenshots).

I added fudge factors to squeezer BLRMS NULL gain so the monitors read 0dB when we are not squeezing. All of the changes have been accepted in SDF.

Elenna, Gabriele

We noticed coherence between DARM and INP1_P and INP1_Y. So we redesigned the loops to have a much larger roll-off at 10 Hz and above, for both P and Y

SQZ Team. Last night we left the ADF on at 1300Hz while the IFO thermalized. See attached plot for how ADF calculated phase changes 25degrees over the first 5 hours of the IFO lock. We plan to repeat this tonight with the ADF nearer 100Hz (where H1 range is effected by SQZ changes more) and expect less change. See alog 69055 for optimizing SQZ angle during first ~1hour of lock. SQZ angle H1:SQZ-CLF_REFL_RF6_PHASE_PHASEDEG = 140.33 throughout.

J. Betzwieser, L. Dartez, E. Goetz, J. Kissel, J. Rollins

The details are happening all too fast in order to write them all down here but at the 10000 foot level, as of 2024-04-26 19:54 UTC, we've updated
   - the primary CAL-CS variables that create CAL-DELTAL_EXTERNAL_DQ, which correspond to the interferometrically-measured free parameters (optical gain, cavity pole, actuation gains for TST, PUM, and UIM changes)
       :: Values are informed by last Thursday's 2023-04-20 IFO measurement. No major change here, just pushing these to get them consistent with the rest of the pipeline. Not informed yet by the current state of the IFO, especially the TCS settings and SRCL offsets

   - The "DARM model transfer function function values at calibration line frequencies" EPICs records
       :: Importantly, this comes with changes that are the fall out of LHO:68880 and the solution pyDARM Merge Request 234

   - The GDS-CALIB_STRAIN pipeline has new filters, and importantly its got a configuration change that now using the corner station copy of the PCAL, H1:CAL-DELTAL_REF_PCAL_DQ, as it's measure of the PCAL system rather than the end-station.
       :: Again, this is the fall out of LHO:68880

Many details to come in the comments.