No obvious reason for the lock loss that ended the lock just shy of 26 hours. The lock loss tool doesn't seem to be working at the moment.

TITLE: 04/14 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: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 2mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.16 μm/s
QUICK SUMMARY: Locked for 25.5 hours. Some great triple coincidence over the last 24 hours.

TITLE: 04/13 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:

H1's been locked for ~17.5hrs (and currently observing for ~12hrs).
LOG:

• 2345 ran launch script for nuc33 (it was missing SQZ dtt).

H1 is humming along with a lock over 13.5hrs (and a 6.5+hr triple coincidence stretch).  Winds are low and microseism has been hovering over the 50th percentile the last couple shifts.

TITLE: 04/13 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 1mph Gusts, 0mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.25 μm/s
QUICK SUMMARY:

H1's been locked for 9.5+hrs, and it was Saturday Tour day, but TJ said the last tour has completed.

TITLE: 04/13 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Locked for 9.5 hours. We went out of Observing at 1830 UTC to run a calibration sweep in coordination with LLO, but went quickly back in Observing at 1901UTC.
LOG:

• 1832 Starting calibration sweep
• 1901 Observing

Ran a broadband and simulines sweep in coordination with LLO at 1830UTC and back to Observing at 1901UTC. Simulines info:

Start:

PDT: 2024-04-13 11:39:00.895189 PDT
UTC: 2024-04-13 18:39:00.895189 UTC
GPS: 1397068758.895189
 

End:

PDT: 2024-04-13 12:00:31.547582 PDT
UTC: 2024-04-13 19:00:31.547582 UTC
GPS: 1397070049.547582

2024-04-13 19:00:31,472 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20240413T
183901Z.hdf5
2024-04-13 19:00:31,479 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_202
40413T183901Z.hdf5
2024-04-13 19:00:31,485 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_202
40413T183901Z.hdf5
2024-04-13 19:00:31,490 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_202
40413T183901Z.hdf5
2024-04-13 19:00:31,494 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_202
40413T183901Z.hdf5
ICE default IO error handler doing an exit(), pid = 2063220, errno = 32
 

Sat Apr 13 10:13:33 2024 INFO: Fill completed in 13min 29secs

TITLE: 04/13 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 1mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.20 μm/s
QUICK SUMMARY: Locked for 1.5 hours, automated relock.

TITLE: 04/12 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Oli
SHIFT SUMMARY:

Nice shift with H1 eventually locking up on its own with no intervention; a GW candidate mid-shift; and H1 running on a 7+hr lock (and 5+ hrs of triple coincidence).  
LOG:

• H1 having troubles relocking and getting past DRMI ASC/BSC St2.
  • After 4th lockloss at beginning of BSC Stage2 with the AS Air video swinging in yaw
  • 5th lock was the charm getting past DRMI (POP18 did get noisy like previous locklosses around the DRMI ASC & BSC St2 steps, and also PR Gain also came on noisy and rang down within a few minutes.
  • 2349 At NLN, but some Squeezer changes needed to be addressed; (I accepted some TCSCS diffs for PSAM alignment) & Squeezer team (Naoki) needed to make adjustment to alignment of ZM4/5/6.  And Camilla ACCEPTED these changes.  Naoki then ran a measurement, and then H1 was taken to OBSERVING.
• 0222 Received automated phone calls for GW-candidate (GW240413p)
• 0601 Earthquake notification from Nepal (M5.5) which showed up as a small blip around the end of the shift 50min later.

H1's been locked for almost 3.25hrs (just under 3hrs of observing) and we have been in triple coincidence for much of this shift except for H1 being down at the beginning & Virgo down for a lockloss 2hrs ago.

For FAMIS #26294:  All looks well for the last week for all site HVAC fans (see attached trends).

(Camilla,Corey,Naoki, Vicky)

Once H1 got through a few hiccups at the DRMI ASC & BSC St2 steps, it went straight to NLN. 

There were some Squeezer items which needed to be changed:

1. PSAM Offset changes for ZM4 & ZM5 (under the TCSCS SDF) were ACCEPTED with Camilla's approval (see attached screenshot)
2. ZM4/5/6 alignment changes needed---Naoki updated pointing & Camilla ACCEPTED the SDF.
3. SQZ_MANAGER Guardian node needed to be transitioned to MANAGED---> Select MANAGED button on ALL screen
   • Plus SQZ_MANAGER needed to be listed as Managed by "ISC_LOCK"----> In a terminal entered:   caput H1:GRD-SQZ_MANAGER_MANAGER ISC_LOCK  (Vicky helped us with this)

I made an attempt at updating Camilla's PSAMs double raster script to include alignment scans to optimize the squeezing throughput at each step and to automate measurements of FDS and FDAS spectra:

/opt/rtcds/userapps/release/sqz/h1/scripts/PSAMs_double_raster_v2.py

This should roughly replecate the functionality of the PSAM scan automation code used at Livingston (llo 64645).  It likely still requires debugging, but I wanted to tag it here before I leave.

Naoki, Camilla, Eric

We've decided to try out our other candidate PSAM values for a few days.  While retuning, we also took some FDS/AS and FIS/AS traces so we can characterize this operating point using Dhruva's interactive_sqz code.

PSAMs at 8.8/-0.7

• 20:48:30-20:58:30 UTC  No SQZ time (10 min)

Measured NLG =  17.07 (following 76542). Adjusted OPO temperature  to 31.475

PSAMs moved to  7.5/0.5,  walked alignment back manually on ZM4/5 using trend from Tuesday, Ran Scan_alignment for FDAS. 

Data:

• 21:13:40-21:18:40  FDAS, CLF=104 (5 min)
• 21:20:30-21:25:30  FDAS +10deg,  CLF=114 (5min)
• 21:26:30-21:31:30  FDAS - 10deg,  CLF=94 (5 min)
• 21:33:45-21:38:45 FDS, CLF = 195 (5 min)
• 21:39:10-21:44:10 FDS + 10deg ,CLF=205 (5 min)
• 21:44:45-21:49:45 FDS - 10deg, CLF=185 (5 min)
• 21:51:00-21:56:00 MidSQZ, CLF=148 (5 min)
• 21:57:10-22:02:10 MidSQZ2, CLF = 216.45 (5 min)
• 22:06:00-22:11:00 FIAS, CLF = 104 (5 min)
• 22:13:20-22:18:20 FIS, CLF = 195 (5 min)
• 22:21:00-22:26:00 MidFIS, CLF = 217 (5 min)
• 22:27:10-22:32:10 MidFIS, CLF = 150 (5 min)

There was a fair amount of A2L work going on concurrently which may have been altering the technical noise quite a bit across the dataset.  We intended to grab another NoSQZ at the end, but there was lock loss :( 

We are going to leave things at this PSAM setting tonight with H1:SQZ-CLF_REFL_RF6_PHASE_PHASEDEG = 190.  

Jennie W, Sheila, Jenne

We did steps of 1 up in PITCH for camera offset servo 2 which controls the beam spot on ETMX by moving ITMX and ETMX, as suggested by this overnight test Camilla  and I did.

This improved the build-ups and we went past the optimum point which we found to be CAM_PIT2_OFFSET = -173, so we set the offset to this. The optimum point is shown by the right most cursor in this image.

We did steps of 1 up in YAW for camera offset servo 3 which controls the beam spot on ETMY by moving ITMY and ETMY, as suggested by this overnight test Camilla  and I did.

This improved the build-ups and we went past the optimum point which we found to be CAM_YAW3_OFFSET = -349.5, so we set the offset to this. The optimum point is shown by the right most cursor in this image. There was confusion as the PITCH and YAW degrees are cross-coupled (this confused us as one must wait for the pitch servo to converge while changing the yaw degree of freedom).

We then tried to optimise our last DOF for the camera servos: PITCH for servo 3. We first moved the offset up and then down, but made the build-ups worse each time. By this point we had increased thje gain of the camera servo filter banks by 2 to speed up the converging. CAM_PIT3_OFFSET should be set to its nominal at -230 counts.

Then we ran the A2L gain scripts we used the other day successfully to optimise thse loops to match the new arm alignment. During running of this script we lost lock, not sure why.

We did not add these new offsets to the guardian because of the lock loss, we will do them together with the A2L optimisation during the nest commissioning period.

The A2L script is is userapps/isc/h1/scripts and is called run_all_a2l.sh

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

Getting hand-off from TJ as H1 was recovering from a lockloss (from a 17.5hr lock).  So far we have had 3-locklosses in a row toward the end of DRMI turning on ASC (to most recently when turning on BS's Stage-2----contemplating an Initial Alignment if there is a 4th lockloss!

TITLE: 04/12 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Currently recovering from a 17.4 hour lock. Commissioning time from 1pmPT today and has just wrapped up. Handing off to Corey to finish locking.
LOG:

• 2010 Out of Observing for planned commissioning
• 2232 Lock loss

HAM1 ASC FF was off from 1396381762 to 1396382969 (20 minutes starting 90 minutes into lock). Using this data I could retune the feed forward filters that subtract HAM1 motion from the ASC signals.

I based the attached jupyter code on an older version, and automated the subtraction training for all pitch and yaw ASC signals (CHARD, INP1, PRC2, DC1 and DC2).

Looking at the filters that are loaded now, we used to do the FF only for the pitch degrees of freedom. The subtraction seems to be doing something good in yaw too, so I suggest we upload and try the yaw feedforward filter.

The first plot shows the expected subtraction predicted by NonSENS. The second plot shows the absolute value of the transfer functions.

Finally, the attached text file contains the foton filter definitions for all the feedforward filter banks. I haven't upload those flter to foton, and not tried them yet. Before each filter there is the name of the filter bank where it should be loaded, for example H1:HPI-HAM1_TTL4C_FF_CART2ASCP_1_1