TJ, Camilla.

We turned on the HWS lasers via medm and the LVEA chassis, they came back with the same powers we turned them off with (1.7mW for Y and 3.2mW for X). Since we realigned SR3 to the pre-April alignment yesterday 80028, both beams are on the CCD cameras, picture. The HWS plates are still removed from when we started alignment work in 78083. We will need to replace these before getting HWS signals, then restart HWS code.

CO2X chassis tripped off with the "RTD or IR alarm" error when I turned on the HWS SLED chassis (same rack). Turned back on with no issue (keyed off/on, gate button). We've seen similar behavior before. These CO2 chassis are planning an upgrade as per FRS6639.

I found the LVEA, clean receiving entrance and EE bay lights still on, turned them off but they would have been on during observing since yesterday, tagging Detchar.

There was an earthquake rumbling through the site from Papua New Guinea during commissioning this morning, so Sheila suggested we could try the IMC gain redistribution again, as we got several notifications of IMC splitmon saturations. To do this, we commented out the IMC power adjust decorator in the IMC_LOCK guardian, unfortunately  in the wrong state, so we again got bit by IMC_LOCK readjusting IMC fast gain while we were trying to change IMC fast gain and IN1 and IN2 gains. After losing lock and catching the error, the decorator was commented out in the ISS_ON state for IMC_LOCK, and the gain redistribution was added to ISC_LOCK's LASER_NOISE_SUPPRESSION state. Still waiting for the ground to calm down enough for the arms to stay locked, but we will try locking with the gain redistribution in this time.

I realized that there isn't an explict alog about this because Paul was asking, so I'm adding this trend to show that after the OFI repair our optical gain is better by about 2.1%, implying that the optical losses are reduced by 4.3%.  While the OM2 heaters is now off and was on before the vent, that didn't have a large impact on optical gain last time that we changed it in late June. 

Wed Sep 11 08:12:51 2024 INFO: Fill completed in 12min 47secs

WP12069 New CDS NAT router test

Jonathan:

The new CDS NAT router was tested successfully. It has been left in place as the production machine. Details in Jonathan's alog.

WP12067 Add PEM ADC to h1iscey

Fil, Erik, Dave:

The additional PEM ADC was added to h1iscey's IO Chassis. At the same time the failed A2 Adnaco backplane in the chassis was investigated.

After replacing backplanes and swapping fibers the problem was traced to the Adnaco adapter card in the front end computer, specifically the PCIe slot it was in (slot7, left-most as viewed from rear of computer).

h1iscey does not have any Contec binary IO cards, so it was possible to skip PCIe-slot7 and temporarily only use three Adnaco adapter cards.

h1iopiscey model was modified to add the new ADC. A DAQ restart was required

WP12076 Add VACSTAT EPICS channels to DAQ

Dave:

A new H1EPICS_VACSTAT.ini was added to the DAQ. EDC+DAQ restart required.

WP12075 Add RACCESS UID EPICS channels to DAQ

Dave:

H1EPICS_RACCESS.ini was expanded to add the UID channels. EDC+DAQ restart required.

WP12059 Add CDS HW Status EPICS channels to DAQ

Dave:

H1EPICS_CDSHWSTAT.ini was added to the DAQ. DAQ+EDC restart required.

DAQ Restart

Dave:

The DAQ was restarted 12:01 0-leg, 12:05 1-leg for the above changes. EDC was restarted at 12:02.

No problems with the restart, no second GDS restarts were required.

h1digivideo3 cameras briefly offline

Dave:

While tracing the digital video servers ethernet cabling I discovered the WorkStation-VLAN ethernet cable in eth0 of h1digivideo3 was not fully seated and its cameras went blue-screen.

After Erik alerted me to the issue, I pushed the ethernet cable and it reseated with a satisfying snap and the images started streaming again.

TITLE: 09/11 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 4mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.14 μm/s
QUICK SUMMARY:

IFO is in NLN and OBSERVING as of 14:16 UTC.

SQZ is not perfectly optimized just looking at DARM.

Planning on going into planned calibration from 8AM PST to 10AM PST (15-17 UTC)

The IFO timed out during initial alignment because ALS Y would not lock. Flashes were at 0.8 but it wouldn't catch. I tried to manually move ETMY, TMSY, and eventually ITMY, but I couldn't increase the height of the flashes. After about 30 min of fussing with it, it caught and stayed locked. I have no idea what was different though. 

Initial alignment has just finished and main locking has commenced.

TITLE: 09/11 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: Easy automated acquisitions but some short locks following the SR3 move, 22 and 14 minutes, the 3rd lock we were able to survive. The low range check yielded high PRCL, CHARD_Y, and a little DHARD_Y (mostly just at low frequency, <20Hz) coherence with cleaned DARM. We've been locked for almost 5 hours. LLO is currently down due to the incoming tropical storm/hurricane.

• 21:41 UTC lockloss
• 23:06 UTC back to NLN, where SQZ resumed their adjustments
• 23:20 UTC lockloss, after only 14 minutes
  • The BS alignment was now off, so we had to go through check_mich
• 00:15 UTC back to NLN, 01:05 UTC observing after Naoki and Vicky finished working on the SQZer alog80031

Naoki, Vicky

We are back to observing after the SR3 move. For SQZ, we had to move quite a lot to get the SQZ LO loop to lock (Naoki mostly moved ZM5 yaw sliders around +200 urad).

PSAMS SDFs attached to get back to our recent values (not the single-bounce values we found this morning in lho80010, but what we used yesterday / last couple weeks). So ZM 4,5 strains = +5.5V, -0.8V as they were yesterday.

We weren't able to try these new values properly in full lock because

1) OPO TEC temperature was off, Naoki had to move the OPO TEC setpoint from 31.474 --> 31.457 (ie, lowered it by 0.017 degC). Noticed this because anti-squeezing was like 2-3 dB too low.
2) SR3 move meant a big alignment shift for SQZ, regardless of PSAMS settings. The new SCAN_ALIGNMENT plots now also include OMC_RF3_Q so we can compare whether this is a usable signal for SQZ ASC.

So now we're basically back to where we were this morning, after the sr3 move. We can try the single-bounce psams settings from lho80010 in full lock another time.

TITLE: 09/10 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:

IFO is in PREVENTATIVE_MAINTENANCE as of 23:06 UTC

Post-Tues Maintenance

We’re trying to get to observing but waiting on SQZ Team to finish alignment. We've reached NLN twice now.

Locking started at 19:58 UTC where after our SR3 move, we went into initial alignment in prep for full IFO locking. Initial alignment finished at 20:37 UTC. It took a while because we had to move SRM to alignment with the new SRM and SR2 positions.

We fully automatically got to NLN at 21:18 UTC but lost lock 22 minutes later (21:41 UTC) for unknown reasons. We didn’t get to observing due to SQZ commissioning work happening at that time.

Following the lockloss, we were not able to lock X-Arm ALS, losing lock twice unexpectedly, prompting yet another initial alignment. This initial alignment stalled at SRC align, which was unexpected considering we just moved SRM to proper alignment manually at this state. Ryan C paused the state and apparently that was all that was needed in order for initial alignment to re-catch, finishing the process. Onto real locking.

We lost lock unexpectedly at CHECK_IR but in relocking, were able to lock DRMI without going through PRMI or MICH. We then fully automatically got to NLN for a second time. SDF Diffs from first NLN acquisition attached.

UPDATE 16:21 UTC:

We lost lock again from NLN during SQZ alignment, convincing me that perhaps the previous LL was also SQZ related. 14 min lock. On the bright side, it seems we are reliably locking to NLN following the SR3 movement.

Other:

• H1Digivideo3 cameras (EX, EY, OMC Trans, SQZ) were temporarily down (cable was knocked out accidentally but replugged shortly after notifying CDS).
• SQUEEZE_OUT was railing during intial alignment of SRC, something I had not seen before.

Planned + Completed Tuesday Maint Activities (All times UTC)

• Align SQZ Pump AOM - WP12077 - Completed Monday 09/09
• Alternate lea/lag chiller units at LVEA, mid stations and end stations - WP12073 - Done 09/10 before shift
• PEM Magnetic Injections and SUS In-Lock Charge Measurements run successfully - 14:30 to 15:00:
• CDS Switch to Backup Router - now being tested during maintenance, WP 12069 - 15:00 - 15:05
• FARO IAS Survey Activities - WP11757 - 15:20 - 18:50
• HAM6 New RGA to CR RGA Computer - WP12074 - 15:32 - 16:25
• EY ADC PEM IO Chassis Install - WP 12067 - 15:20 - 17:40 (partially complete - done for now)
• SQZ to OMC Scans and Mode Matching - 15:25 - 18:35
• EX New DAC Transition from read only to read and write - WP12079 - 16:22 - 18:55
• Dave DAC Restart (incl. Node load + nds1 restart) following EX DAC work (and also doing more opportunistic CDS edits - WP 12075, WP 12076) - 19:00 to 19:10
• Planned SR3 IFO Alignment Move - 19:20 to 20:20
• Visual iunspection on picomotor chassis K&L to update spare channels list - WP12078 - not completed due to other EX DAC work going over-time

Other/Opportunistic (All times in UTC):

• Center IMC WFs - 18:35 to 18:45
• Routine 3IFO Checks - 16:45 - 18:10
• TCS Line Inspection - 16:15 - 16:50
• LVEA Walkabout Chamber Sweep - 16:35 - 17:25
• HAM1/2 Cleanroom Check - 17:30 - 18:30
• Battery Maintenance - 17:55 - 20:20
• LVEA Capturing Photos - 18:00 - 18:20
• Forklift Recycling Transport - 15:30 - 18:45
• Access and Camera Restart - 22:25 - 22:45

LOG:

Marc Daniel

We measured the gain and phase difference between the new DAC and the existing 20-bit DAC in SUS ETMX. For this we injected 1kHz sine waves and measure gain and phase shifts between the two. We started with a digital gain value of 275.65 for the new DAC and adjusted it to 275.31 after the measurement to keep the gains identical. The new DAC implements a digital AI filter that has a gain of 1.00074 and a phase of -5.48° at 1kHz, which corresponds to a delay of 15.2µs.

This puts the relative gain (new/old) to 1.00074±0.00125 and the delay to 13.71±0.66µs. The variations can be due to the gain variations in the LIGO DAC, the 20-bit DAC, the ADC or the AA chassis.

TITLE: 09/10 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 19mph Gusts, 12mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:

• Relocking at TRANSITION_FROM_ETMX, we recovered lock from maintenance earlier but we lost it 22 minutes later, before we could recover observing.
• Wind is low to moderate

TJ and I turned up the CO2s from 1.7W to 2.0W today before we lost lock for Tuesday Maintenance at 2024/09/10 15:10 UTC. We then lost lock at 2024/09/10 15:18 UTC. We did this after mention that PRCL to CHARD coupling could be reduced by CO2 power changed in 79989, but we didn't have time to think about if we should make an injection.

Closes FAMIS 28370

All the measurements ran, ITMX could not be processed due to low bias_drive_bias_off coherence.

No clear trends, everything seems steady.

Per WP12079 we started measurements to compare directly the 20 bit DAC driving the ESD and L3 to our LD32. 

Comparing ESD Driving Signals
Test 1 - LD32 bank 1 (ch 0-7) attached to 0-7 on the PEM ADC ; 20 bit DAC ESD signal attached to 8-15 on the PEM ADC

Comparing L3 Driving Signals
Test 2 - 20 bit DAC L3 attached to 0-7 PEM ADC : LD32 bank 2 (ch 8-15) attached to 8-15 on the PEM ADC

After analysis of the data, we measured about ~14us delay in the LD32 which is accounted for by the Anti Imaging filter on the FPGA.  We also determined the gain should be ~275.65 to achieve the same calibration between both DACs.

Driving the ESD and L3 with the LD32 will be postponed until next week.

daniel sigg, dave barker, marc pirello

Vicky, Camilla

Repeated 66946 PSAMs changes with SQZ-OMC scans with a new method of dithering the PZT around the TEM02 mode and minimizing it. With this we improved the mode mismatch from 4% to 3%. It will interesting to see if these settings are still better in full lock. Plots of OMC scan attached and same plot zoomed on peaks attached.

• Increased SEED power from 0.7 to 75mW. SQZ_OPO_LR to LOCKED_SEED_DITHER. Started with 0.07mW on OPO_IR_PD but we're misaligned on SQZT7. This increased to 1.25mW when we move the ZM4/5 alignment. Will need to fix table alignment to match IFO alignment when we're happy.
• Took IMC to OFFLINE (mis-aligns MC2), aligned SRM, misaligned SR2.
• Note, that we should have (but didn't) misalign the ITMs to make the REFL signal cleaner.
• When we bring ZMs back to IFO alignment, SQZ beam is on AS_AIR (a little high).
• Turned on DC 3/4 centering loops and then OMC ASC. Have power on AS_A/B/C. 70 counts on A/B_DC_SUM.
• Locked OMC with SQZ beam: OMC_LOCK guardian to DOWN. Changed H1:OMC-LSC_LOCK_TRIGGER_THRESHOLD from 1.0 to 0.3. Manually scanned using  H1:OMC-PZT2_OFFSET. Watched OMC-DCPD_SUM_OUT_DQ and OMC TRANS camera (exposure increased). Autolocker off. When we found the resonance, turned H1:OMC-LSC_SERVO ON, gain to 1, INT and BOOST on.
• Sending in 1.25mW, expect 70% reflected off SRM would be ~0.9mW, get 0.95mW on AS_C_NSUM, get 0.64mW transmitted though OMC.

Took OMC scans using tempalte /sqz/h1/Templates/dtt/OMC_SCANS/Sept10_2024_PSAMS_OMC_scan_coldOM2.xml  Unlock OMC and H1:OMC-PZT2_OFFSET to -50 (nominal is-17) before starting scan.

Over 1V and under -1V on ZM5 is bad at most ZM4 strains (tested at 4.0V ZM4). For each step we adjusted ZM4 and then fine adjusted ZM5.

In preparation for WP 12079, I prepared ESDOUTF (L3) and COILOUTF (L1, L2) filters to make up the calibration difference between 18-bit and the new 32-bit DACs. This is similar to what was done in LHO:64274 to adjust from 18-bit DACs to 20-bit DACs. Similarly, I placed new '32bitDAC' gains in CALCS-ETMX. In CAL-CS, the new gains are intended to replace the gains of '4'. 

I have not yet loaded the filter coefficients, but they have been saved in the filter files. 

We made some improvements today in the sensitivity, going from about 151 Mpc on GDS CLEAN to about 158 Mpc. However, our best range from April 11th (DARM FOM reference pre-OFI disaster) is around 165 Mpc. I made a comparison of that time and now with today's commissioning improvements to see where we are still missing range. I have attached the four plot results from the darm_integral_compare results (see alog 76935 for directions).

The range integrand plot makes it much easier to see that we are still missing sensitivity around the mid-frequency band. However, the sensitivity difference shows that we lose 5 Mpc of range by 40 Hz as well. Much of this range loss seems to come from a variety of peaks that have appeared since the OFI vent, such as the 20 Hz peak. We lose another ~3 Mpc between 40-200 Hz.

I ran a bruco with GDS CALIB STRAIN CLEAN on high range time after commissioning today: post-commissioning bruco

It looks like many of these new low frequency peaks (like the large 20 Hz peak) are well witnessed by things like PSL accelerometers, indicating that they could be from jitter: PEM-CS_ACC_PSL_TABLE1_Y_DQ

Generally, there is a lot of jitter coherence, and given that this is the CLEAN channel, that's probably a sign that the jitter cleaning could be improved, maybe making use of other witness channels if the current witnesses are insufficient to subtract the noise.

A peak at 30 Hz has some coherence with MAG sensor channels, here is one: PEM-CS_MAG_LVEA_VERTEX_X_DQ

Right around 35.4 Hz, there is a lot of coherence with various ISI HAM6 sensors and OMC ASC sensors. For example: ISI-HAM6_GS13INF_V1_IN1_DQ

There is also still a large amount of LSC REFL RIN coherence up to 1 kHz: LSC-REFL_RIN_DQ

I think we should test the PRCL offset again, especially because this will help reduce the CHARD Y noise coupling (ASC-CHARD_Y_OUT_DQ) and will also possibly help this HF noise (frequency noise? intensity noise?)

SRCL is better than before, but maybe has more room for improvement between 10-25 Hz: LSC-SRCL_OUT_DQ

DHARD Y coherence is low, but still present, so we should be careful with the WFS offset: ASC-DHARD_Y_OUT_DQ

There is still PRCL coherence: LSC-PRCL_OUT_DQ which is likely coupling through a combination of CHARD Y, SRCL, and LSC REFL RIN. Again a PRCL offset will help. Other strategies are to check POP phasing, POP sensing, etc. Reminder: PRCL feedforward failed, so we need to consider other avenues for noise reduction.

To summarize some strategies to get back to April sensitivity:

• check if squeezing can be further optimized in the bucket
• work on improving jitter subtraction, and consider possible low frequency jitter as well
• investigate and improve PRCL coupling through the ASC and possible offsets causing excess frequency or intensity noise
• continue to hunt other low frequency peaks, especially those that are new from the OFI vent
• fiddle with SRCL FF a bit more

Editing because I went back to check the previous PRCL offset work and found this comment: 76818, in short, we can fix the REFL RIN coherence, but it has no effect on the sensitivity. However, it can improve CHARD Y noise, although at the time I don't think we were limited by CHARD Y enough to see the low frequency benefit.