TITLE: 05/05 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 15mph Gusts, 12mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.13 μm/s
QUICK SUMMARY:

H1's been locked just over 2hrs (after being down ~100min to relock on its own).  Range is hovering just below 135Mpc.

TITLE: 05/05 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
SHIFT SUMMARY: Locked for the first half of shift and high winds and an earthquake kept us unlocked for the second half. Currently locking well at ENGAGE_ASC_FOR_FULL_IFO.
LOG:

Naoki, Vicky

This is the continued work of alog69276. After centering the FC2 by ZM3, the optimal green QPD output is 0.046 for pitch and -0.0037 for yaw. So we set the offset of input matrix for INJ ANG as -0.046 for pitch and 0.0037 for yaw. Then we moved the ZM3 and checked the response of green QPD and IR camera as shown in the attached figure. The green QPD and IR camera respond to the ZM3 well. We will implement the beam spot control with these signals soon.

We attempted to move to the SRX router again today.  We took an outage from about 6:20pm to 10:00pm localtime (1am-5am UTC).  We were able to have some ESnet engineers and a Juniper support engineer working with us.  Unfortunately we were unable to get bits flowing through the SRX.  Neither us, ESnet, nor the vendor understand why the packets are not flowing.

We ruled out issues with the fiber, optics.  We rewrote, removed, disabled firewall rules.  We reworked the routing setup and policies several times.

We could send packages but not receive them, a symptom of that was we were never able to get an arp entry for ESnet.  ESnet received packets from us and had a correct apr entry.  We also tried set a static arp rule on our end, but that did not help.

Below I have listed the relvant alogs for TCS changes while at 76W input power. Alog 68491 listed the TCS changes with 60W input power. 

I'm not documenting between 7th April and 13th April as at that time we were experimenting with 70 and 78W locks.

IFO has been locked for 6h45. In observing for the last hour. Range is 130-138MPc.

Louis, Jeff, Camilla

Attached is the sitemap > CAL CS > Calibration Monitor screen ~5 minutes after the first measurement was started. Note that Both CO2s are Annular not central as shown in the screenshot, I'll adjust this medm.

'pydarm report' command gave attached report H1_calibration_report_20230505T012609Z.pdf

I've been making a few changes to the ALS_COMM node over the past couple of days to attempt to fix some of the ir finding issues we've been seeing. After pulling myself out of an awful conditional and lack of sleep mess I made, we're now in a good spot. Summary of changes:

1. When finding IR, the transmitted power would be just barely below threshold to recognize it and fine tune the signal. The signal without IR, dark, would often be off by about +/-0.2, making a found IR seem as though it wasn't there. I added a PREP_SEARCH state to move the VCO frequency away, take some dark time, and then reset the H1:LSC-TR_X_QPD_B_SUM_OFFSET. This seems to have helped with the consistency.
2. Finding IR in the fast search consists of moving the VCO to two known good frequencies. Sometimes it would go to a frequency and while there was clearly something visible on the output, it would be just below threshold. With the previous PREP_SEARCH step added, I was able to lower the thresholds a fair amount (0.22 to 0.8) and so far this has been good. This threshold might need to be adjusted, we'll see as we get more relocks.

ALS_DIFF's IR finding works a bit different, but I think some of this can be carried over. Working on that next.

I have updated the IMC_LOCK guardian to open the ISS second loop if the diffracted power changes by more than 30% when first closed, then close it again. The check lives in the CLOSE_ISS state, where the necessary things are done to close the second loop. When the second loop closes, the guardian now waits for 30 seconds to see if the ISS diffracted power changes by more than 30% (high or low), and if it does, request OPEN_ISS to open it again. The node will stall briefly, but then it will move to close the second loop again by going through the LOCKED and CLOSE_ISS states. This update should fix our recurring issue where the input power differs lock to lock due to the second loop engaging its DC coupling at an irregular place and changing our input power, sometimes by up to 1.5W.

I encountered an issue when testing this change where if the node had a notification, in this case the IMC WFS needed centering, the unstall_nodes decorator used by ISC_LOCK to revive its subordinates wouldn't work. This meant that IMC_LOCK would see the diffracted power had changed too much, correctly move to OPEN_ISS, then get stuck. To remedy this, TJ and I decided the best course of action was to move this notification into DIAG_MAIN. I then raised the threshold for the IMC WFS checker in IMC_LOCK to 0.7, up from 0.5, so that IMC_LOCK would only show a notification if the WFS are very off-centered.

All of these changes have been appropriately updated in svn.

JoeB, DriptaB, RickS

After a lengthy discussion on the Pcal call today, we have developed a revised plan for realizing the Pcal XY comparison.

In a nutshell, it is to:
a) drive the X-end systematic error Pcal line at 283.91 Hz  with an ampliutude (sin only) of approximately 10 x the current amplitude (200 cts -> 2000 cts)
b) drive a Y-end Pcal XY comparison line at 284.01 Hz (0.1 Hz higher) with similar amplitude (in DARM).  This should require about 1430 cts.

LLO plans to implement a similar scheme.  This should enable calculation of the Pcal XY comparison factor with sufficient SNR.

We plan to hold off implementing this scheme until tomorrow to avoid overlap with other ongoing calibration-related work and to allow some time for further discussion.

TITLE: 05/04 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Commissioning
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 22mph Gusts, 19mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.17 μm/s
QUICK SUMMARY: IFO has been locked for 2h45.  Currently in commissioning for some SQZ changes and calibration measurements. 

TITLE: 05/04 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
SHIFT SUMMARY:

Main Notes:

• IFO is locked at NLN for ~2:45 hrs and measurements are currently ongoing
• Still some SDF diffs in the observe snaps preventing us from going to OBSERVING (though most are due to ongoing work)
• GRD was able to do most of the locking automation with the exception of DRMI, where I had to intervene in ACQUIRE_PRMI

- LOCKLOSS @  14:35 UTC, DCPD saturation, then again trying to relock at LOCKING_ALS, not sure why

- Held at LOCKING_ALS to allow TJ for automation work on IR locking

- Lock #1:

• Acquired NLN @ 16:51 UTC
• IN OBSERVING: 17:17 UTC
• OUT OF OBSERVING: 17:26 UTC
• PI24/31 ringups
• LOCKLOSS @ 18:28 UTC - PI ringups 

- Lock #2:

• Had to intervene at DRMI (after GRD failed a few times) to catch PRMI by moving PRM in Yaw (~20 microradians)
• Stopped at ENGAGE_ASC for measurements
• Jeff ran a broadband PCAL measurement on EX
• Acquired NLN @ 20:12 UTC
• Ryan S did some ISS second loop off for testing
• EX saturation @ 21:34 UTC - Probably CAL related - and again at 22:13 UTC

- Other Notes:

- Unmonitored ALS POL step size channel - Screenshot attached

- PSL DM counts - room 101 300 nm alert - trended at was ~320 counts and has been slowly creeping up over the past 4 hrs, Screenshot attached

- Vicky reverted the PI damping guardian to old working settings (success)
LOG:                                                                                                                                                                     

There was an occurence of the 4 Hz bumps during a ten minute test where the squeezer was off (alog 69077). So we can eliminate the squeezer as a cause.

Daniel made the good point at the commissioning meeting that we should try turning down the analog gain of the LSC-POP_A PD, to avoid saturating the I ADC signal if we can.  Attached shows that we currently have 21dB of analog gain, so we probably have some room to turn it down.  I think we semi-recently checked the power calibration filters of many of our PDs, so if we believe this to-microWatt filter, then we have 35 mW on that diode.

We concluded the analysis concerning the back-scattered light introduced by the OFI. We used the data mentioned in the logbook entries: 68910 and 68926. A presentation summarizing the analysis and the results can be found on the DCC: G2300951-v1.

We first estimate the G-factor from the spctrum during the noise injections and then we used this factor to simulate the scattered light noise projections.

In Fig. 1 it is show the noise spectrum considering the OFI displacement signals during the Earthquake in New Zeland (24th April 2023 00:42:00 UTC). In green is the correct projection, where the differential motion between the SRM and the OFI is shown. The orange curve takes into account only the displacement of the OFI. 

In Fig. 2 it is show the noise spectrum considering the OFI displacement signals during a low seismic activity period (27th April 2023 12:00:00 UTC). In green is the correct projection, where the differential motion between the SRM and the OFI is shown. The orange curve takes into account only the displacement of the OFI. 

The conclusion is that for the moment the back-scattered light coming from the OFI is not limiting the sensitivity of LHO.

WP 11173

Issues reported with EY temperature channel H1:PEM-Y_EBAY_RACK2_TEMPERATURE. With fence work ongoing this morning, we swapped cabling for Rack1 and Rack2 sensors on the EtherCAT End Link Chassis. This will help us determine if issue stays with Beckhoff channel or sensor. I did note that the M12 connector threads on port 1 seems to striped. Connector will need to be replaced.

Time cables were swapped: 10-10:30 am

We just had a lockloss after 20.5 hours of lock that appears to be from the ASC, specifically CSOFT P. The oscillation was at about 0.45 Hz and the ring up occurred within the last two minutes of lock. The oscillation appears in other ASC signals, such as INP1, DHARD, and MICH.

I am suprised to see this kind of lockloss so long into the lock, so I am not exactly sure what action to take. I have increased the DSOFT P and CSOFT P gain to give more bandwidth to the loops. I also think we should try to get an OLG of CSOFT P at this higher power (the last OLG was taken at 60W, 67539). OLGs of all arm ASC loops at 430 kW of power would be ideal, but take time.

Austin, Betsy, Karla, Rahul

We have finished bonding fused sillica Ears to ETM12 using Hydroxide Catalysis Bonding (HCB) technique, please see pictures attached below for reference. The ear-test mass bond layer has few air bubbles within our tolerance (less than 50 sq mm of the total bond area). We can confirm that the position of both the ears on the two flat surface of the mirror are within the required +-0.1mm.

ETM12 (also see galaxy page for details on the optic) is a our spare test mass mirror between the two sites. The details of the ear and test mass mirror is given below,

- Ear s/n 30077403-04 (Q2300015) is bonded to the flat side S3.

- Ear s/n 30077403-05 (Q2300016) is bonded to the flat side S4.

Both the ears were 22.3 grams heavy (measured using a calibrated scale in a clean room).

The fiducial line measurements on the optic was performed at CIT and the details are posted in E2200356_v1.

I have uploaded the latest version V27 of Jig settings calculation on the DCC.

We still need to measure the total weight of the optic and apply First contact to clean the HR side.

- all calibartion lines off (NLN_CAL_MEAS) with frequency dependent squeezing
    from  PDT: 2023-04-27 07:56:44 PDT
          UTC: 2023-04-27 14:56:44 UTC
          GPS: 1366642622

    to    PDT: 2023-04-27 08:06:56 PDT
          UTC: 2023-04-27 15:06:56 UTC
          GPS: 1366643234
- no squeezing
    from  PDT: 2023-04-27 08:07:28 PDT
          UTC: 2023-04-27 15:07:28 UTC
          GPS: 1366643266
    to    PDT: 2023-04-27 08:17:29 PDT
          UTC: 2023-04-27 15:17:29 UTC
          GPS: 1366643867