TITLE: 06/14 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:

IFO is in NLN and OBSERVING as of 21:33 UTC.

21:07 UTC to 21:33 UTC: COMISSIONING

19:28 UTC to 21:07 UTC: OBSERVING

Things of note:

• Sheila, Camilla and I investigated SRCL FF mistuning that showed up on the low range checks - alog 78441 - this was our 30 mins of comissioning that improved the mistuning (as shown in the alog). All in all, an LSC SRC Offset was changed - SDF Diff below.
• A2l script was edited, used and SDF diffs were accepted (and some reverted). This is documented in both alog 78439 (midshift update) and alog 78438.
• ISC_LOCK was also loaded while OBSERVING after changes were made so we dropped in and out of observing briefly (4 seconds) due to that.
• ITMY CPS Glitch occured at 22:46 UTC - first time I've seen this.
• Hanford Fire Dept. visited and asked to go down the arms, to which I refused since we were in Observing. They went to the kitchen patio area, turned around, then left.

LOG:

TITLE: 06/14 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 3mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:

Detector Observing and has been locked for over 4 hours. Range isn't great, around 148 MPc, but besides that everything is good.

I looked at the SUS-{SR2,SR3,SRM_M1_DAMP_{P,Y}_INMON channels for a period on the 21st April before the OFI, and after we had re-aligned through the OFI to rcover our optical gain on the 25th April after the OFI burn.

I have compared these to the drift in alignment in the signal extraction cavity yesterday. This is partly to figure out why we have to keep retuning our SRCL feedfoward.

The only angular degrees of freedom that changed significantly between these dates were:

• SR3 yaw which was changing during lock about 6 times its normal drift on the 25th vewrsus how much it changed during the lock on the 21st. Yesterday its drfit during lock seems back to its value before the OFI burn.
• SRM pitch drift seems to vary a lot between these three different locks. Not sure what we can learn from this.

Ibrahim, Sheila, Camilla

After Ibrahim relocked the IFO, the range is lower around 150 Mpc.  Ibrahim ran the coherence checks from the low range wiki, and saw that there was braod SRCL coherence.  He double checked that the SRC ASC offsets 78415 from yesterday are correctly still in place.  The squeezing level is quite good in this lock.

I accidentally started to run the A2L script (by clicking in a terminal I didn't mean to), so we took a few minutes to try to retune SRCL FF.  We tried the feedforward that Gabriele fit last week, 78307, which gives us worse coupling than the April 29th filters do.  Then we adjusted the gain using the April 29th filter, screenshot attached.  The SRCL coherence is still highly, and the range is still low.  We would need a new filter to get good SRCL decoupling in this lock, but we do not understand why this has changed since last lock.

IFO is in NLN and OBSERVING as of 19:26 UTC

Mini-Events Today:

• Lost lock around time when CP1 Fill just ended - Dave informed us that while the last part of the fill is loud, it doesn't usually cause a lockloss
• Sheila edited the A2L Script TJ made earlier this week (adjusting wait times to allow gain to settle - alog 78438
• Had to run and rerun Align SQZ script due to High Freq Noise being higher than usual
• Accepted and reverted certain diffs per Sheila's instruction (from aforementioned edits). The diffs are linked below.

Since the yaw ASC cross couplings to DARM were high in our last lock, Ibrahim and I took a couple minutes before going into observing to run the script that TJ edited yesterday  (78419) again.  The attached screenshot shows that in our first time running the script the ADS values were still drifting when the script moved on to measuring the next step.  This might have been because the IFO had locked recently, or because it needs to wait longer.  We added a 30 second wait after we change the A2L gains before checking the values by adding +30 on line 185, after this it looked like things had settled well. 

We ran the script for all test masses yaw only from the terminal using: python a2l_min_multi.py --quads ETMX ETMY ITMX ITMY --dofs Y 

After the script ran, there were many SDF diff that Ibrahim has screenshots of.  It would be good to edit the end of the script to have fewer of these diffs each time we run it. We added these new values to lscparams and loaded ISC_LOCK.

Here are our first and second run results. 

*************************************************
RESULTS
*************************************************
          ETMX Y
Initial:  4.94
Final:    4.95

     ETMY Y
Initial:  0.94
Final:    1.01
          ITMX Y
Initial:  2.89
Final:    2.89

          ITMY Y
Initial:  -2.51
Final:    -2.39
Diff:     0.11999999999999966

*************************************************
RESULTS
*************************************************
          ETMX Y
Initial:  4.95
Final:    4.91
Diff:     -0.040000000000000036

          ETMY Y
Initial:  1.01
Final:    1.0
Diff:     -0.010000000000000009

          ITMX Y
Initial:  2.89
Final:    2.85
Diff:     -0.040000000000000036

          ITMY Y
Initial:  -2.39
Final:    -2.45
Diff:     -0.06000000000000005

Here are some plots that show the fuctioning of the fast shutter, before, during and after the June 7th pressure spikes.  The fast shutter functions the same way before and after the pressure spikes.  However, in the locking attempts with the HAM6 alignment different the beam going to AS_C was clipped, and this meant that the fast shutter didn't block the beam on AS_A and AS_B as quickly as it normally does. 

The first attachment shows a lockloss from June 6th, the lockloss before the pressure spikes started.  The fast channel that records power on the shutter trigger diode (H1:ASC-AS_C_NSUM_OUT_DQ) is calibrated into Watts arriving in HAM6.  Normally these NSUM channels are normalized by the input power scaling, but as the simulink screenshot shows that is not done in this case.  Using the time that the power on AS_A is blocked, the shutter triggered when there was 0.733 Watts arriving in HAM6, and the light on AS_A which is behind the shutter is blocked.  There is a bounce, where the beam passes by the shutter again 51.5 ms after it first closes, this bounce last 15ms and in that time the power into HAM6 rises to 1.3W.  In total, AS_A (and AS_B) where saturated for 24ms.  This pattern is consistent for 4 locklosses in several locklosses from higher powers, with the normal alignment on AS_C, both before and after the pressure spikes in HAM6. 

In the first lockloss with a pressure spike, 78308, the interferometer input power was 10W, rather then the usual 60W, and the alignment into HAM6 was in an unusual state.  The shutter triggered when the input power was 0.3Watts according to AS_C, which was clipped at the time and so is underestimating the power into HAM6.  The trend of power on AS_A and AS_B was different this time, with what looks like two bounces and a total of 35ms of time when AS_A was saturated.  The first bounce is about 14ms after the shutter first triggers, but the beam isn't unblocked enough to satrate the diode, and a second bounce saturates the diode 36ms after the shutter first closed, and lasted 26ms, during which time the power into HAM6 rose to 0.55W.  The power on AS_C peaked about 250ms after the shutter triggered, at about 1W onto AS_C.  Keita is going to look at energy deposited into HAM6 in typical locklosses, where AS_C is not clipping as that will be more accurate. The pressure spike shows up on H0:VAC-LY_RT_PT152_MOD2_PRESS_TORR about 1.5 seconds after the power peaks on AS_C, and peaks at 1.1-7 Torr.

At the next pressure spike, the interferometer was locked with 60W input power, and AS_A was saturated for 80ms before the shutter triggered, and there was no bouncing.  This time the pressure rise was recorded 2 seconds after the lockloss, and 1.8 seconds after the power on AS_C peaked, this was a larger pressure spike than the first at 1.3e-7 Torr.  

The third pressure spike was also a 60W lockloss, with AS_A saturated for 80ms and no bounce from the AS shutter visibile.  The pressure rise was recorded 2.1 seconds after the lockloss, and was 3.1e-7 Torr. 

The final attachment shows the first lockloss after we reverted the alignment in AS_C, when the fast shutter behavoir follows the same pattern seen before the pressure spikes happened.

Fri Jun 14 10:09:56 2024 INFO: Fill completed in 9min 53secs

Jordan confirmed a good fill curbside.

Closes FAMIS 26252

Laser Status:
    NPRO output power is 1.813W (nominal ~2W)
    AMP1 output power is 66.77W (nominal ~70W)
    AMP2 output power is 137.7W (nominal 135-140W)
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 16 days, 20 hr 27 minutes
    Reflected power = 21.32W
    Transmitted power = 106.0W
    PowerSum = 127.3W

FSS:
    It has been locked for 0 days 18 hr and 48 min
    TPD[V] = 0.8414V

ISS:
    The diffracted power is around 2.7%
    Last saturation event was 0 days 18 hours and 48 minutes ago

Possible Issues:
    PMC reflected power is high

TITLE: 06/14 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 5mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY:

IFO is in NLN and OBSERVING (17 hrs 28 mins)

Woke up to see that the SQZ_OPO_LR Guardian had the message:

"disabled pump iss after 10 locklosses. Reset SQZ-OPO_ISS_LIMITCOUNT to clear message"

Followed 73053, but did NOT need to touch up the OPO temp (it was already at its max value); then took SQZ Manager back to FRE_DEP_SQZ, and H1 went back to OBSERVING.

State of H1: Observing at 157Mpc, locked for 6.5 hours.

Quiet shift so far except for another errant Picket Fence trigger to EQ mode just like ones seen last night (alog78404) at 02:42 UTC (tagging SEI).

I took the script that we have been using to run our A2L and converted it to run the measurements for all quads and degrees of freedom at the same time, or less, as desired. The new script is (userapps)/isc/h1/scripts/a2l/a2l_min_multi.py. Today Sheila and I tested it for all quads with just Y with the results below. These values were accepted in SDF, updated in lscparams.py, and ISC_LOCK reloaded. More details about the script at the bottom of this log.

Results for ETMX Y
Initial:  4.99
Final:    4.94
Diff:     -0.04999999999999982

Results for ETMY Y
Initial:  0.86
Final:    0.94
Diff:     0.07999999999999996

Results for ITMX Y
Initial:  2.93
Final:    2.89
Diff:     -0.040000000000000036

Results for ITMY Y
Initial:  -2.59
Final:    -2.51
Diff:     0.08000000000000007

The script we used to use was (userapps)/isc/common/scripts/decoup/a2l_min_generic_LHO.py which was, I think, originally written by Vlad B. and then Jenne changed it up to work for us at LHO. I took this and changed a few things around to then call the optimiseDOF function for each desired quad and dof under a ThreadPool class from multiprocess to run all of the measurements simultaneously. We had to move or change filters in the H1:ASC-ADS_{PIT,YAW}{bank#}_DEMOD_{SIG, I, Q} banks so that each optic and dof is associated with a particular frequency and used the ADS banks 6-9. These frequencies needed to be spaced apart enought but still within our area of interest. We also had to engage notches for all of these potential lines in the H1:SUS-{QUAD}_L3_ISCINF_{P,Y} banks (FM6&7). We also accepted the ADS output matrix values in SDF for these new banks with a gain of 1.

This hasn't been tested for all quads and both P&Y, so far only Y.

I ran the DARM offset step code starting at:

2024 Jun 13 16:13:20 UTC (GPS 1402330418)

Before recording this time stamp it records the PCAL current line settings and makes sure notches for 2 PCAL frequencies are set in the DARM2 filter bank.

It then puts all the PCAL power into these lines at 410.3 and 255Hz (giving them both a height of 4000 counts), and measures the current DARM offset value.

It then steps the DARM offset and waits for 120s each time.

The script stopped at 2024 Jun 13 16:27:48 UTC (GPS 1402331286).

In the analysis the PCAL lines can be used to calculate how the optical gain changes at each offset.

See the attached traces, where you can see that H1:OMC-READOUT_X0_OFFSET is stepped and the OMC-DCPD_SUM and ASC-AS_C respond to this change.

Watch this space for analysed data.

The script sets all the PCAL settings back to nominal after the test from the record it ook at the start.

The script lives here:

/ligo/gitcommon/labutils/darm_offset_step/auto_darm_offset_step.py

The data lives here:

/ligo/gitcommon/labutils/darm_offset_step/data/darm_offset_steps_2024_Jun_13_16_13_20_UTC.txt

Following on from Sheila's alog 77427, checked on VAC trends and OFI temperature around April 22nd.

I checked (maybe a repeat of someone else) that there were no vacuum spikes during the locks when Kappa_C dropped or the locklosses afterwards. Plot of Kappa_ C with VAC channels attached.

Looking at the OFI TEC readbacks during that time, they were significantly noisier than usual during Tuesday maintenance after the 5% optical gain drop, before out alignment shift.  Noisy between 6:30am and 4pm. This is before any Tuesday maintenance 77363 or injections start. Plot attached, including zoom out and zoom in. It also happened the May 28th to May 30th.

Last night and today we are in a different spot through the OFI.  See Sheila's alog 78096 for the move that was made. 

Overall, SR2 and SRM yaw are much closer to center in this position, however SRM pitch is farther from center.  I did a quick double check of the SRM pit, and indeed this is where it wants to be.

The previous spots (with the previous SR3 alignment) are recorded in alog 77443.

Attached are the saved SDF diffs for both Observe and Safe snap files.