TITLE: 04/20 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 2mph Gusts, 1mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:

• Winds calming down
• Lost locking at the end of the CAL measurement, relocking at green arms

After coordinating with LLO & notifying Virgo, went with running the Saturday Calibration Measurements (broadband [~5min] + simullines [~25min]) at ~ 2200utc. 

LOCKLOSS (at 2225utc) During Measurement!!  Sadly, it looks like we had a lockloss toward the end of the Calibration.  Vlad said we should let Louis know so he could look at the script to see if the excitations are too strong toward the end of the Simulines measurement.

• Following instructions (link)
  • NOTE:  In the procedure there is mention of "Take ISC_LOCK to AUTO (from MANAGED by H1_MANAGER....will need to undo this when done)."  But H1_MANAGER is in IDLE after we revert on-call operator at the beginning of the shift---so ISC_LOCK is already in AUTO.
• 2200 ISC LOCK to NLN_CAL_MEAS
  • Screenshot is attached
• 2201-2206 Broadband measurement run
  • Measurement at:  /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/
• 2206-xxxx Simullines measurement
  • gps START time:  GPS:  1397685998.905604
  • gps END time:  GPS: 1397687180.225995  (this was given after a few ERROR lines ran after H1 lost lock.
  • Files writtten to subfolders here:  /ligo/groups/cal/H1/measurements

Today is my first time being on shift to attempt a Saturday calibration  measurement, but have had a few wrinkles:

1. h1 lockloss early in the shift; this is noteworthy because for the calib measurement you need to be thermalized (H1 has to be locked at high power for atleast 3hrs).
2. When I was about 45min away from running the measurment, L1 had just recovered from their lockloss (so this resets the timers back to 3hrs again for L1 to thermalize).
3. We are aiming to have a coordinated calibration measurement at 2200utc (3pm PDT).

No other notables for H1 from the shift

Sat Apr 20 10:09:46 2024 INFO: Fill completed in 9min 42secs

For some reason none of us got texts for this fill, but subsequent test texts were getting through and fill emails were received as normal. I restarted the locklossalert service on cdslogin at 10:23 PDT. Tested it by sending test texts, we will see if this fixes our cp1 fill text issue tomorrow.

TITLE: 04/20 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 20mph Gusts, 18mph 5min avg
    Primary useism: 0.07 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY:

H1 had a lockloss about 4.5hrs ago, but has been UP about 3hrs. 

For the Alarm Handlers there was a "Not Connected Error" window up (and WHITE alarm for dust monitors) at 2:23amlocal which cleared up in 3 seconds.

For those who felt it (or heard) there was a M2.8 earthquake in Richland last night (at 9:18pm Local).  H1 rode right through it and it was only seen on our seismometer DMTs for the 3-10 & 10-30Hz bands (it's the orange EX x-axis line at about 11hrs --see attached-- (I happened to look at it last night after my sister texted me about it while she was working at the Emerald; she (and I) didn't feel it.)  :)

Calibration measurement scheduled for 11:30amLocal /1830utc.

TITLE: 04/20 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: We stayed locked the whole shift, 1 small local EQ. The range hovered around 155-165
 

Bit of local motion that was reported as a 2.7 EQ in Richland, WA on USGS and EMSC at 04:19UTC

Virgo went down later in the evening (around 06:00UTC) and wasn't able to relock from their green ALS laser needing to be fixed (new amplifier) Valog 64030

LOG:                                                                                                                                                                                                                                                                                                                                                                                                                        

We've been locked for about 4 hours. The range has been just over 160.

TITLE: 04/19 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:

Commissioning time from 1900-2200utc but there was a lockloss at the end---H1 currently at 60W so almost back up.

Picket Fence froze earlier in the shift.
LOG:

• 1550 Dave restarted Picket Fence (it yad a YELLOW status box on the overview)
• 1604-1640 Pcal set-up in lab (francisco)
• 1610-1854 SHG work in the Optics Lab (Camilla, Terry, Kar Meng)
• 1616-1650 Picking up hot spot at EX & a check at EY (fil)
• 1730-1757 Univ of Montana tour (RyanS)
• 1900 Commissioning Begins
• 2000 Topped off the PSL chiller (since the low level alarm was heard in the Receiving Area) [Richard]
• 2051 PCal work (tony)
  • 2108 Francisco joining
• 2156 Lockloss (errant gain change)
• 2226-2231 Moving an amp (robert)

TITLE: 04/19 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 12mph Gusts, 9mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY:

• Relocking at LOWNOISE_ASC, Robert has a PEM EXC running that he will take care off
• Little windy, but not that bad
• Lots of test points still open

Sheila, Gabriele, Camilla, Jennie

The other day I used Elenna's template to make a PRCL excitation: 77252

We can use this to check on our PRCL to SRCL feedforward element in the LSC input matrix, where we add some of the POP A 9I signal (PRCL) to the POP A 45I signal (SRCL) to cancel the POP45 sensitivity to PRCL.

When the PRCL excitation is on, the transfer function of POP45I/POP9I is -0.028716 cnts/cnt

We want to set out input matrix such that:

5_1 = -5_3 * POP41/POP9I tf (with PRCL excitation on) to cancel the PRCL contribution to the SRCL error signal.  This means that now, our POP 9I to SRCL ERR matrix element should be 0.107 but it is now 0.06. 

EDITING to Add:

Today I re did this measurement and saw that POP45/POP9I is -0.02551 cnts/cnt, meaning that the input matrix should be 0.0946. Updating the input matrix to this did improve the PRCL to SRCL decoupling, as shown in the second attachment. 

I also tried moving the PRCL offset, this did not seem to change the POP45I/POP9I ratio much, so the PRCL to SRCL decoupling doesn't seem to need retuning each time the PRCL offset changes. 

The third screenshot shows the PRCL to DARM coupling, there are small changes (2-3dB change) with these changes in PRCL offset and PRCL to SRCL decoupling.  So this suggests that the main coupling of PRCL to DARM isn't through SRCL.  (And that the PRCL offset sn't helping much). 

Gabriele remembered that the PRCL to DARM coupling could also be through MICH, indeed the third screenshot shows that the PRCL signal is a factor of 10 smaller in POP45 Q than in I. In 66151 Anamaria tuned the phasing so that the PRCL signal in 45Q was a factor of 100 smaller than in I, so we can try to improve this by rephasing POP45.

Edited again:

Camilla and I moved the POP45 phase from 8 to 11, this reduced the PRCL to POP45Q transfer function to be about a factor of 100 below PRCL to POP45I (last screenshot blue references show the improvement from a phase of 8 to 11).  We then remeasured the SRCL to PRCL input matrix element, which should be 0.087.  This made the SRCL coherence in DARM rather bad, although the PRCL to MICH and PRCL to SRCL couplings were improved.  We decided to revert these, and wait for next week to make the changes at a time when we could immediately retune FF.  As I stepped the phase back I accidentaly moved us from 11 to 6 in one step, which unlocked the IFO. 

[Jennie, Sheila, Gabriele]

Low frequency OMC alignement lines were injected between 20:19 UTC and 21:16 UTC, following a similar method to what described in 76462.

Using the code attached, I looked at how the noise in DARM and the amplitude of the 410.x Hz calibration line changes with respect to the OMC QPD signals.

One can see from a spectrogram that the noise in GDS-CALIB_STRAIN_NOLINES is strongly modulated by the OMC angular lines. The spectrogram shows GDS-CALIB_STRAIN_NOLINES normalized to the median over time.

Then one can compute BLRMS as several bands of GDS-CALIB_STRAIN_NOLINES to see how the noise changes, and of OMC-DCPD_SUM at 410-411 Hz to monitor the amplitude of the DARM calibration line, that is a proxy to optical gain. Time series are shown in the attached figure, where the OMC-DCPD_SUM BLRMS time series are comapred with the OMC QPD signals.

Finally, I plotted the 410-411 Hz BLRMS of OMC-DCPD_SUM (optical gain) in a scatter plot vs all four QPD. This allows me to select a value of the QPD signals that maximize the optical gain. The negative of those values is the offset that should be added to the OMC QPD on top of the existing offset.

CAVEAT: However, looking at the noise in GDS-CALIB_STRAIN_NOLINES between 800 and 900 Hz (that should be shot noise) one see that it is minimum for the current OMC offsets. Maybe this is an indication that the SQZ is aligned with the current OMC, but the current OMC is not well aligned to the IFO. I suspect that using the offsets above will increase the optical gain, but make SQZ worse

Naoki, Camilla, Sheila

We did 5+5 minutes ON/OFF test of ADF line at 322 Hz. While the ADF is ON, we changed the ADF demod phase to make the ADF SQZ angle around 0 so that we can use the ADF servo with 322 Hz ADF line. 

The script to change the ADF frequency is in (userapps)/sqz/h1/scripts/ADF/setADF.py. The command is as follows.

python setADF.py -f 322

1st cycle
ON (5 min)
UTC: 2024/04/19 19:02:10 UTC
GPS: 1397588548

OFF (5 min)
UTC: 2024/04/19 19:07:21 UTC
GPS: 1397588859

2nd cycle
ON (5 min)
UTC: 2024/04/19 20:02:52 UTC
GPS: 1397592190

OFF (5 min)
UTC: 2024/04/19 20:08:00 UTC
GPS: 1397592498

3rd cycle
ON (5 min)
UTC: 2024/04/19 20:13:16 UTC
GPS: 1397592814

OFF (5 min)
UTC: 2024/04/19 20:18:35 UTC
GPS: 1397593133

The x509 certificate for cdsldap0 was due to expire tomorrow.  This would have caused the control room systems to not recognize users.  Due to the age of our ldap server and an updated signature type from our regular certificate authority we were unable to follow our usual certificate renewal and replacement procedure.  To address this we issued a certificate from an an internal CA for cdsldap0 and pushed out the required configuration changes to the clients today.

At this point everything should be working, though CDS laptops may need to go through a cycle of puppet running to get the updates in place.

As a note to our sysadmins if there are issues the steps to check are as follows (these should all be done by puppet):

 1. ensure the LHO_CDS_CA.crt file is installed
 2. restart the nslcd service
 3. reload the nscd service

We are also working on the replacement for cdsldap0, however it will not be ready before tomorrow.

[Jennie, Jim, Gabriele]

We tried again turning on the HAM1 yaw FF to ASC, like in 77254. This time we wanted to turn on one dof at a time.

We first turend on the CHARD_Y FF since we care mostly about that loop. It worked well and reduced the CHARD_Y noise below 20 Hz.

We then turned on the INP1_Y FF. This imrpvoed slighlty the INP1 dof, but made the CHARD_Y g back to the original noise level.

We did not try the other dofs, since the predicted subtraction had very little effect.

We lft the CHARD_Y FFs on, and all other yaw off. This improves CHARD_Y and maybe also DARM, to be confirmed.

Jim accepted the new values in SDF

Fri Apr 19 10:07:41 2024 INFO: Fill completed in 7min 38secs

Jordan confirmed a good fill curbside.

Jennie W, Sheila

Summary: We spent some time today resetting A2L gains, which make a large impact on our range.  We are leaving the gains set in guardian to be the ones that we've found for 3 hours into the lock, but this will probably cost us about 5Mpc of range early in the lock.

Overnight, our our low range was partially because the angle to length decoupling was poor (and partly because the squeezing angle was poor). We were running the angle to legnth decoupling script this morning when an EQ unlocked the IFO, and now we have re-run it with a not thermalized IFO. 

I manually changed the amplitudes for the A2L script again on a per optic bassis to get each A2L set in a first round, there was still significant CHARD P coherence.  I've edited the run_all_a2L.sh script so that some degrees of freedom are run with amplitudes of 1, 3 or 10 counts excitations, this has now run and suceeded in tuning A2L for each DOF on each optic, this second round seems to have improved the sensitivity.  We may need to tune these amplitudes each time we run a2L for now.

After our second round of A2L, the ASC coherences were actually worse than after only one round.  We tried some manual tuning using DHARD and CHARD injections, but that didn't work well probably because we took steps that were too large.

After the IFO had been locked and at high power for ~3 hours, we re-ran the A2L script again, which again set all 4 A2L gains, and impoved the range by ~5Mpc compared to the A2L settings early in the lock (see screenshot).  I've accepted these in SDF and added them to LSCparams:

        'FINAL':{
            'P2L':{'ITMX':-0.9598, #+1.0,
                   'ITMY':-0.3693, #+1.0,
                   'ETMX':4.1126,
                   'ETMY':4.2506}, #+1.0},
            'Y2L':{'ITMX':2.8428, #+1.0,
                   'ITMY':-2.2665, #+1.0,
                   'ETMX':4.9016,
                   'ETMY':2.9922 },#+1.0}

This means that the A2L probably won't be well tuned for early in the locks when we relock, which may cost us range early in the locks.  In O4a we werw also using the camera servo, not ADS, and since we set the camera servo offsets to match ADS alignment early in the locks, we probably had less than optimal decoupling late in the lock stretches.  This probably had less of an impact on range since these noises are contributing in the same frequency range as the ESD noise was in O4a.

Jeff K, Sheila D

We are interested in which signals we can use to try to damp triple bounce and roll modes, since these are probably responsible for some of the peaks in our forest of peaks around 25-35Hz (77109 and 76505).  Jeff is preparing to implement a damping path on the HSTSs so that we can try to damp these. 

We looked at signals (in addition to DARM) that we may want as options for damping. 

• 27.42 Hz - REFL A 9I PIT
• 27.5 Hz -nothing other than DARM
• 27.6 Hz - REFL A 45I yaw (plus several LSC signals, PRCL, SRCL, REFL45 I, POP9Q)
• 27.72 Hz nothing but DARM
• 28.2 Hz PRCL, LSC REFL45 I, ASC REFL A 9I pit, ASC REFL A 45 I yaw

Dtt template is at /ligo/home/sheila.dwyer/SUS/HSTS_damping_signals_checks.xml