Ran a broad band and simulines meaurement starting at 1531UTC.

Simulines start:

PDT: 2024-05-30 08:37:11.822463 PDT
UTC: 2024-05-30 15:37:11.822463 UTC
GPS: 1401118649.822463

End:

2024-05-30 15:58:42,508 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_
SS/DARMOLG_SS_20240530T153713Z.hdf5
2024-05-30 15:58:42,515 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DA
RM_SS/PCALY2DARM_SS_20240530T153713Z.hdf5
2024-05-30 15:58:42,520 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_
L1_SS/SUSETMX_L1_SS_20240530T153713Z.hdf5
2024-05-30 15:58:42,524 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_
L2_SS/SUSETMX_L2_SS_20240530T153713Z.hdf5
2024-05-30 15:58:42,529 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_
L3_SS/SUSETMX_L3_SS_20240530T153713Z.hdf5
ICE default IO error handler doing an exit(), pid = 1172966, errno = 32
PDT: 2024-05-30 08:58:42.575781 PDT
UTC: 2024-05-30 15:58:42.575781 UTC
GPS: 1401119940.575781
 

TITLE: 05/30 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY: Locked for 13 hours, range around 150+. Planned calibration and commissioning today from 830-1200PT.

TITLE: 05/29 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

Decent shift with more Observing time compared to last night's shift.  Notables for locking was the continue locklosses for FIND IR (even after an alignment).  Pausing seemed to help.  There was also a superevent as well (102nd of O4).
LOG:

• 2340 Lockloss
  • Locking notes:
    • Several locklosses at early state (FIND IR)---during Diff Beatnote sweeps
    • 2358 Started Initial Alignment
      • For ALS it only took about 7min to complete (but while waiting for offload x-arm would lose lock randomly even with the good transmitted power)...Ryan S mentioned a very long ALS step (over 40min!) which ended up sending him a wake-up call during his Owl shift.
      • Continued to have a couple more FIND IR loclosses.  So, waited at LOCKING ALS for 2min, and then watched both ALS COMM & DIFF guardians.  And finally made it past FIND IR.  (Should also mention wind speeds have been increasing.)
      • 0116 OBSERVING
• 0120-0141 Washington teachers tour in Control Room (Cassidy)
• 0124 S240530a

Decent night even with winds and a lockloss.  (H1 had issues getting past FIND IR.)  Also managed a super event at the very beginning of this current 2+hr lock.

Jennie W, Sheila

Summary: We need to rerun this test with slightly different starting QPD offsets and a different amplitude to get a meaningful measurement of how the optical gain would be affected by changing the OMC alignment.

I started an injection into the OMC ASC loops (which feed back to the OMC and the OM3 pitch and yaw to keep the beams centred to specific offsets on OMC QPD A and B.

With this we can raster the OMC alignment and find which QPD offsets allow us to maximise optical gain.

The injection started at about 20:30 UTC while no squeezing was injected.

I used this template at /ligo/home/jennifer.wright/Documents/OMC_Alignment/20240419_OMC_Alignment_EXC.xml with amplitudes of 3 counts in all four degrees of freedom.

Within one cycle the OMC suspension saturated.

Why did we saturate with an injection amplitude of 3 as this ran the last time we did this test without any saturations?

Decreased amplitude to 1 to run it without saturating the OMC suspension.

Restarted at 20:39:07 UTC roughly.

Stopped injecting after 21:06:00 UTC.

Results inconclusive as changing the QPD in offset does not seem to change the noise injected around the calibration line between 410 to 411 Hz, so maybe we need to have higher injection amplitudes but start raster from different QPD offset set points so we don't staurate the suspension.

Looking at ndscope of the channels when they saturated.

OMC T2 and T3 saturated (this is an18 bit DAC). This is OMC pitch degree of freedom, which corresponds to Y direction in the OMC ASC loop basis.

Looking at the top left plot the POS Y DOF seems to correspond to the time of saturation and is the highest Y channel so we want to put in a +0.5 offset to this before the next time we run this raster to bring the input to the POS Y loop down in magnitude.

TITLE: 05/29 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY:

IFO is in NLN since 17:45 UTC

IFO States for the day has been:

14:25 UTC: OBSERVING

14:45 UTC: Lockloss - after initial alignment, we went into planned comissioning from 16:00 UTC to 19:00 UTC. IFO stayed in down during this time for comissioning tasks. After these, we began to lock again.

17:45 UTC: Reached NLN and went into COMISSIONING

19:11 UTC: OBSERVING after comissioning tasks wrapped up

20:30 UTC: COMMISSIONING impromptu comissioning time coinciding with LLO since neither site had a fully locked IFO during the original alotted time. An hour of comissioning time was agreed upon.

21:34 UTC: OBSERVING

23:30 UTC: Shift End - OBSERVING

LOG:

TITLE: 05/29 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 18mph Gusts, 12mph 5min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

H1's been locked almost 5.5hrs and seem a little calmer than yesterday at this time, althought we've had some gusts approaching 30mph.  No items to hand over from Ibrahim for locking tonight (other than possibly proactively run an Initial Alignment if there are ALS or DRMI/PRMI issues

FAMIS 26304, last checked in alog77997

Only notable change was yesterday, where the new fan bearing on CS fan 6 looks to have lowered the noise picked up by the vibrometer.

Sheila, Camilla 

Checking SQZ:

• Single bounce ITMX, OM centering loops on and frozen (turn off inputs)
• Increased SEED injected power from 0.2mW to 76mW (same as April 16th 19:19UTC as in 77518 and 77518 plot)
• SQZ Manager LOCKED SEED DITHER
• ALIGN SRM, misaligned ITMs
• Previously injecting 1.28mW into HAM6 (OPO_IR_PD_LF with BeamDiv closed), now 1.25mW to 1.29mW, so similar power to before. 
• Started with ~360 on AS_C NSUM
• Kept centered on AS_C with ZM4 while moving ZM5 to increase power on AS_C.
• Power was fluctuating a lot and it seems like we were mainly on a plateau.
• Accepted new alignments (scattering in IFO will tell us if they are better or worse, hard to tell if AS_C power really increased), attached in two sdfs, mainly pitch move then yaw.
• Got peaks of 384 on AS_C_SUM, average was 370 (want 380). Still loosing 2-3% from what’s expected. 
• Similar power on AS_A and AS_B ~75.
• Plot attached. 

Checking IFO:

• Single bounce ITMX 10W in, previously had 762e-2 on AS_C_NSUM. Today had 750e-2. 
• With similar power into IMC 9.60W today, 9.61W prevoiulsy.
• Sheila checked the alignment sliders, we are ~15urad off in SR2 PIT witness channel. Everything else looks good  (DC centering not on at time). Plot attached.
• Didn't change IFO alignment, started locking. 

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.

FAMIS 25993, last checked in alog77948

No appreciable difference that I can see compared to last check.

Sheila added a new boost in DHARD to the guardian, and we relocked with it successfully, so I have accepted the SDF diff in Observe.

TITLE: 05/29 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 142Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 4mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s 
QUICK SUMMARY:

IFO just lost lock 14:47 UTC and now relocking

Dust monitors also have a few warnings:

*H1:PEM-CS_DUST_LVEA6      WARNING: dust counts did not change, please investigate
  *H1:PEM-CS_DUST_LVEA10     WARNING: dust counts did not change, please investigate
  *H1:PEM-CS_DUST_PSL101     WARNING: dust counts did not change, please investigate
   *H1:PEM-CS_DUST_PSL102     WARNING: dust counts did not change, please investigate

 
 

TITLE: 05/29 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Wind
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

A bit of a wind storm at the beginning of the shift but luckily strongest winds only lasted about an hour and allowed for locking shortly thereafter.  Had about 4-5hrs of observing during this shift (with another lockloss minutes before the end of the shift).
LOG:

• 0010 Winds drop below ~30mph!
• 0100 NLN
• 0105 nuc30
• 0113 Took SQZ Manager to FDS
  • 0115 Ran SCAN_ALIGNMENT_FDS and then SQZ Angle
  • 0140 Naoki joined me in teamspeak to look at alignment (& camilla also joined).  ZM4 was adjusted in alignment slightly again.
  • H1 range is hovering around 130-140Mpc.
  • 0411 LOCKLOSS (
• Locking notes:
  • ALSx arm took some time to lock as it had trouble staying locked (but eventually made it)
  • PRMI looked off in yaw, and I was not able to get it better by hand.  Ran a Manual Alignmnet of just the PRC.  Unfortunately, DRMI still had issues locking (even with SRM tweaks, so a full Initial Alignment was run).  After this H1 made it to NLN with no problem.
  • 0616 Back to Observing with a range around 150Mpc.
• 0752  Sadly as I typed this summary H1 had another lockloss (this was with calm winds)

Andrei, Sheila

We've analyzed the time-traces of the effective range (H1:CDS-SENSMON_CAL_SNSW_EFFECTIVE_RANGE_MPC) along with the alignment channels FC_WFC_A(B) and AS_A(B)_RF42 (see attached figures). We found no observable dependance between those.