I accepted these P2L spot gain SDF Diffs to get into Observing.

Summary highlights of DQ shift the week from 2024-04-08 to 2024-04-14

• The IFO was in observing mode for 74% avg. (lower during the first half of the week and better during the second half)

• LHO was observing at a range of 158 Mpc with some dip in range to 134Mpc on the first 2 days of the week (8th and 9th).

• For most of the week, whenever the IFO transitioned to observing from a lockloss, the strain h(t) showed noise in the lower frequency regions 10-50Hz and also broadband high frequency noise (above 500Hz) which reduced with time. On some days, these features lasted for more than a couple of hours.

• Violin modes at 500Hz and its harmonics were strong at the beginning of observation time after lock loss but dampened after a couple of hours.

• Most of the high SNR omicron glitches were centered at ~ 40Hz

• The dominant channels in Hveto were usually

  • H1:PEM-EX_VMON_ETMX_ESDPOWER48_DQ

  • H1:ASC-CHARD_Y_OUT_DQ

• Fscan lines have been on the higher side in the range of 600 to 700 on most days this week.

Full DQ shift report with daily observations can be found in the wiki page here: https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20240408

TITLE: 04/18 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Aligning
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM_EARTHQUAKE
    Wind: 3mph Gusts, 1mph 5min avg
    Primary useism: 0.97 μm/s
    Secondary useism: 1.28 μm/s
QUICK SUMMARY:

Starting the Shift Oli and I noticed that the IFO was still relocking and needed an initial_alignment.
Since then Initial_alignment had stalled and been restarted. Possibly because the IMC was unlocked. I'm usure if Oli had done that or not.

Once that completed Another earthquake hit but was not announced over verbals.
M 5.3 - 60 km WSW of Pozo Dulce, Mexico 2024-04-18 07:39:45 (UTC)26.546°N 110.267°W10.0 km depth
So I'm just waiting on the earthquake to pass.

TITLE: 04/18 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Quiet night most of the night, but had a local earthquake knock us out close to the end of my shift. Currently running an initial alignment with the help of H1 MANAGER running an initial alignment and Tony watching H1 MANAGER run the initial alignment to make sure H1 MANAGER gets us locking once that's done.
LOG:

23:00 Detector Observing and Locked for over 15 hours

06:08 Earthquake mode activated
06:11 Lockloss due to local earthquake
    - ALS flashed were really low and took a while to get up
07:03 Started an Initial Alignment

Lockloss 04/18 06:11UTC due to local earthquake :( We were locked for 22.5 hours

Observing at 155Mpc and locked for 20 hours exactly. Calm evening with low wind

Naoki, Vicky, Jennie W

Naoki followed the directions in to set up the SQZ beam OMC scan.

We had a problem with the DC centering loops. After we switched them on they saturated the OM1 and OM2 suspensions.

We got around this by switching each of the 4 degrees of freedom on first - ie. DC3 Y, DC3 P, DC4 Y, DC4 P.

Then we engaged OMC ASC and this seemed to work ok.

When we tried to manually lock the OMC length loop we had problems as when we switched the gain of 1 on it would lose lock, even when on a TM00 mode of the expected height (0.6mA on DCPD_SUM).

Vicky got around this this using a lower gain and not engaging the BOOST filter in the servo filter bank.

Then she had to touch up the alignment in lock with OM3.

locked quiet time 1397329970 GPS 1 min:

OMC-REFL_A_LF_OUT16 = 0.0930255 mW

OMC-DCPD_SUM_OUTPUT = 0.652156 mA

unlocked quiet time 1397330106 GPS 1 minute:

OMC-REFL_A_LF_OUT16  = 1.04825 mW

OMC-DCPD_SUM_OUTPUT = -0.00133668 mA

dark measurement 1397330625 GPS 1 minute:

OMC-REFL_A_LF_OUT16  = -0.0133655 mW

OMC-DCPD_SUM_OUTPUT = -0.00133668 mA

I noticed after I took the dark measurement that OM1 and 2 were staurating again and need to clear history twice on OM1 to remove this.

Reverted OM1 and 2, 3 OMC sliders at 8:33 am (local time) on the 16th April.

Data is saved as REf 3, 4 and 5 in /ligo/home/jennifer.wright/Documents/OMC_scan/2024_04_16_OMC_scan.xml. Where 3 is the scan channel OMC-DCPD_SUM_OUT_DQ on the bottom right plot, 4 is the PZT excitation channel OMC-PZT2_EXC on the bottom left plot, and 5 is the monitor of the actual PZT output voltage OMC-PZT2_MON_DC_OUT_DQ on the top right plot.

TJ, Camilla. WP 11811

Yesterday, we repeated the  76715 CO2 beam scan using a razor blade on a 25mm transition stage while measuring the power transmitted to our PD (channel H1:TCS-ITMX/Y_CO2_LSRPWR_MTR_OUTPUT).

We realized that some of the blocked beam was transmitted through a hole in the razor blade in our first set of measurements (changed radius measurement ~1mm) so the CO2X 76715  are not as trusted. 

All data taken for CO2X and CO2Y attached and summarized below:

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

IFO is in NLN and OBSERVING

Comissioning today went well. We survived a few high magntitude earthquakes.
 

LOG:

TITLE: 04/17 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 16mph Gusts, 12mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:

We're Observing and have been Locked for over 15 hours.

Jennie, Jim

We tried Gabriele's newest version of the HAM1 ASC feedforward. New filters were installed last week, but we ran out of time during the commissioning window. It seems like we can still only get good subtraction from the pitch degrees of freedom, we got a lot of 10-ish hz injection when we engaged the yaw degrees of freedom.

To start we turned off the HAM1 ff, by setting H1:HPI-HAM1_TTL4C_FF_INF_{RX,RY,Z,X)}_GAIN to zero, then shutting off the H1:HPI-HAM1_TTL4C_FF_OUTSW. While collecting that data we switched to the new filters, and zerod the gains for all of the individual H1:HPI-HAM1_TTL4C_FF_CART2ASC{P,Y}_{DOF}_{DOF}_GAIN filter banks.  We then tried turning on all of the pitch feedforward first, by ramping the gains in a couple of steps from 0 to 1. It seemed like it worked well, but I don't think we actually got to full gain of 1. We then tried turning on the yaw FF, but that pretty quickly started injecting noise around 10hz, first attached spectra, red traces are with the new ff, blue are with ff off.

Second image are trends where Jennie tries to reconstruct the timeline, which is how we found the first pitch test wasn't complete. Sheila ran an A2L measurement, then we tried the pitch ff again, spectra in the third plot. All of the red traces are new P ff (1397415884), blue is the old (1397407980), green is with the ff off (1397405754).  This worked well, we got some slight improvements around 15hz, new chard p gets rid of some noise injection around 2hz. We didn't see the pitch ff affect the yaw dofs.

We left the new pitch filters running, and accepted in the Observe SDF. The yaw filters were left off.

 TCS Chiller Water Level Top-Off (Bi-Weekly, FAMIS #27787)

• TCSx Chiller:  Had level of 31cm.  Added 235 to get to 39 (over-filled slightly beyond ruler)
• TCSy Chiller:  Had level of 11cm cm.  Added 185 to get to 17 (over-filled slightly beyond ruler)
• There was no water in the small cup under the slow leak.

Closes FAMIS 27787

We wanted to check the PRCL offset during our commissoning time this morning, we ended up not having much time for that but did re-run Elenna's template from 76814.  It looks like the PRCL to REFL RIN transfer function is much the same as at that time.  It seems as though there was a change in the PRCL to DARM transfer function, but that measurement has low coherence at most frequencies.

Joe B from LLO and I ran the short and long stochastic injections with the commands below starting at 19:08UTC. Both ran successfully, back to Observing at 1955UTC

H1 is now finished with comissioning and IFO is now OBSERVING

Following up on 77139, we set the camera offsets to those found, and added these to lscparams.py:

cam_offsets = {'PIT':{'1':-233,
            '2':-173,
            '3':-230},
        'YAW':{
             '1':-236,
             '2':-422,
             '3':-349.5},}

This increased the power in the X arm by 5kW, the Y arm by 6 kW, as the screenshot shows. After this we re-ran the A2L script, starting with much lower amplitudes for ETMX yaw.  It seems that with the A2L as badly tuned as this, we need to adjust the amplitude of the excitations for each test mass and each DOF separately

I edited the my_a2l.py script in userapps/isc/h1/scripts to round the A2L gains that it sets, to make it easier to deal with these values in SDF. 

Editing to add, we found that there was still angular coherence so re-ran the script for all DOFs with an amplitude of 1.  This made changed gains for ITMX, ITMY, ETMX, Y2L gains, ETMX and ETMY P2L gain,  not ETMY Y2L gain, or ITMX , ITMY P2L.  The end result is fairly high CHARD P coherence, which is limiting our range right now (see attached screenshot).

J. Kissel 

During today's Systems Call, it came up that there was scant documentation on the timing performance of the existing fast shutter system. A quick look through the aLOG showed some results from the 2016 era including examples like LHO aLOGs 29062, 28958, and 26263. Koji's LHO:29062 is probably the most conclusive, quoting (repeated here for convenience): "The fast mechanical shutter start blocking the beam at 1.7ms, reaches half blocking at 1.85ms, complete block at 2.0ms."

Here, I take some modern data with what digital signals stored in the frames:
    [65 kHz]  H1:OMC-PI_DCPD_64KHZ_AHF_DQ                OMC DCPDs (down stream of the OMC Cavity)
    [4096 Hz] H1:ISI-HAM6_BLND_GS13Z_DQ                  Vertical GS13s on the HAM6 ISI (nominally calibrated into 1 nm/s, but I've scaled it to arbitrarily show up demonstratively on the OMC DCPD plot)    
    [2048 Hz] H1:ASC-OMC_A_NSUM_OUT_DQ                   OMC QPD A SUM (up-stream of the OMC Cavity, but still down-stream from the fast shutter)
    [2048 Hz] H1:ASC-OMC_B_NSUM_OUT_DQ                   OMC QPD B SUM (""")
    [2048 Hz] H1:ASC-AS_C_NSUM_OUT_DQ                    AS_C QPD SUM (up-stream of the fast shutter)
    [16 Hz]   H1:SYS-MOTION_C_FASTSHUTTER_A_STATE        Slow-channel record of the logical state of the shutter
    [16 Hz]   H1:YSY-MOTION_C_SHUTTER_G_TRIGGER_VOLTS    Slow-channel record of the trigger PD voltage (which is AS_C)

With these channels, I show three recent lock-losses. 

It seems like all of the photo-diode signals show a very long "turn off time," (of order ~1 [sec]) and are pretty un-reliable at precision estimates of shutter timing. This is likely a linear combination of 
   - For the OMC DCPDs at least, there's an *additional* hardware "shutter" where the cavity's length actuator -- the OMC PZT -- are quickly railed to unlock the cavity after a lock-loss trigger,
   - For the OMC DCPDs at least, there's a non-negligible cavity ring-down time,
   - For OMC DCPDs and all the QPDs, impulse response of the photo-diode's readout electronics and anti-aliasing filters, and/or the  

However, the "clunk" of the shutter on the HAM6-ISI is quite obvious and precise, so I use the start of the impulse (a few samples after the transition from "no motion" to "large fast negative start of the clunk's ring-down") that as an upper-bound estimate of when the shutter is completely closed. But, with the imprecision of the [16 Hz] channels -- 62 ms -- it's tough to get anywhere.

In short -- what's stored in the frames are a pretty bad metrics for precision timing of the fast shutter system. 

But anyways -- the upper limit of the time between the change of the logical state of the trigger and the HAM6 ISI GS13s registering a large kick is 
    - 08:23:20 UTC :: 0.3125 (+/-0.0625) and 0.341064 (+/-0.000244) = 0.02856 [sec] = 28.5 [ms].
    - 13:01:26 UTC :: 0.125 and 0.1604 = 0.0354 [sec] = 35.4 [msec]
    - 23:39:28 UTC :: 0.3125 and 0.328857 = 0.016357 [sec] = 16.4 [msec]

I'll keep looking for better ways to increase the precision on this statement, but for now, we should still role with Koji's results from LHO:29062

WP11812

Jamie, Jonathan, Erik, Dave:

The two CAL HASH channels (H1:CAL-CALIB_REPORT_HASH_INT and H1:CAL-CALIB_REPORT_ID_INT) were moved from the h1calcs model, where they were being acquired as single-precision floats, to a new custom EPICS IOC called cal_hash_ioc, where they are acquired as signed 32bit integers.

The h1calcs.mdl model was modified to remove the EPICS-INPUT parts for these channels. The model was then restarted.

The IOC, which was being tested with H3 channels, was modifed and rstarted to serve the H1 channels as integers.

The EDC was modified to add H1EPICS_CALHASH.ini to its master list. This added 5 channels the the DAQ, the two hash channels and three IOC status channels.

The EDC was restarted, followed in short order by a DAQ restart.

WP 11805
ECR E2400083

Lengths for possible SPI Pick-off fiber. Part of ECR E2400083.

PSL Enclosure to PSL-R2 - 50ft
PSL-R2 to SUS-R2 - 100ft
SUS-R2 to Top of HAM3 (flange D7/D8) - 25ft
SUS-R2 to HAM3 (flange D5) - 20ft