TITLE: 11/16 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: One lock loss from commissioning with an automated relock during the shift. Most of the shift has been occupied by commissioning time, but we are back to observing at 0033 UTC.
LOG:

• 1606 Senske on site to start blowing out sprinklers
• 1709 Out of Observing for commissioning time
• 1906 Observing
• 2009 Commissioning
• 2009 Lock loss
• 2117 Low noise, more commissioning
• 0033 Observing

Louis and I have been looking at increasing the offloading of the signal from the ESD to the PUM and UIM, in light of 73913. 

I have attempted a few times to make measurements by exciting at the L2 LOCK L filter, this results in poor coherence even for amplitudes that are quite large in DARM, and turning up the amplitude slightly has caused a lockloss by saturating the ESD. 

On Tuesday morning I engaged the PUM boost (L2 LOCKL FM2, boost4.5 which is a boost with a little resG aaround 4.5Hz).  Some history (with links to old alogs about this filter is here: 48767) we used to run with this boost but turned it off in early O3 because angle to length cross couplings were causing instabilities of the DARM loop.  On Tuesday morning I engaged this boost, and we stayed locked.  The first attachment shows a comparison of our ETMX drives to LLO's (LLO also uses ETMY L1 for DARM control, but I haven't plotted that here), H1's usual configuration is in gold and the time with the PUM boost engaged is in red. The ESD drive RMS is reduced by more than a fator of 2 with the PUM boost engaged.  I quickly tried a swept sine injection, and saw that the coherence was somewhat better than earlier measurements with a very small amplitude injection, so it seemed promising that we might be able to get a better measurement of the cross over with the PUM boost engaged.  

Today I engaged this boost again during commisoning time and we immediately lost lock.  The third attachment shows that turning on the boost certainly seems to be the cause of the lockloss. 

We can probably rely on the pyDARM model for the PUM crossover, since the calibration measurements validate the model above 10Hz. Today I was able to make a measurement of the UIM crossover, which Louis can use to compare to pyDARM from 1-10Hz. 

I measured FC IR OLG as shown in the attached figure. The FC IR OLG is higher than the purple reference on March 2023. So I decreased the IR gain from -5 to -3.5 and the OLG became similar to the purple reference. I updated the fc_wfs_a_ir_gain in sqzparams and loaded SQZ_FC guardian.

As commissioning started again, there was a commissioning caused lock loss. We are relocking now and almost back up. When we return to low noise commissioning will continue.

Sheila, Naoki, Camilla

Started testing a phase dither on the SQZ LO that dithers the SQZ angle, so that we can eventually demod the change on the SQZ BLRMS and use for monitoring and adjusting the SQZ level.

Yesterday

Sheila had already added all elements needed to the h1sqz model under H1:SQZ-PHASE and Naoki made a new medm screen (sitemap > sqz > sqz overview  > sqz omc blrms > phase dither). GEO600 uses something similar to this and it's in 'Quantum noise locking' K.McKenzie Paper.

In the SQZ racks we plugged in the DAC output for the DITHER_OUT output into IN2 of the SQZ LO servo (chassis in right rack, slot 16). We had to unplug the "ISC_SQ_232" cable from IN2 of the LO board. If we want to the lock the LO using the homodyme again, we'll need to revert this. 

Today during commissioning time we injected a 7.2Hz signal via H1:SQZ-PHASE_DITHER_OSC . 

Copying whats used in ADS dither locks, we added added a bandpass around 7.2Hz to PHASE_DITHER_DEMOD_SIG to see the sqz angle dither using SQZ BRLMs #4, added low pass at 2Hz to PHASE_DITHER_DEMOD_{I,Q} as the 7Hz x 7Hz gives us a 14Hz and a 0Hz signal, we only want the 0Hz.

We made the #4 SQZ BLRMS use a wider band pass, was 700 to 800Hz, now 700 to 1750Hz. The signal got smoother, so we could think about expanding all the SQZ BLRMS. 

Can already see the change demoded signal having a zero crossing a maximum and minimum squeezing as expected, see attached, where Sheila stepped the SQZ angle via the 'ezcastep' command. We still need to tune the demod phase to minimize Q and understand what amplitude we should use. We can also think about if we can achieve similar SQZ angle monitoring using the ADF signal.

To turn this back on: need to turn on IN2 on SQZ LO servo and put an amplitude in H1:SQZ-PHASE_DITHER_OSC_CLKGAIN. Other settings saved in sdf.

I've released a new version of the ndscope trend plot generator. The new system is more automated, making it easier for anyone to add trends to the system. Details are in the User Guide, which is a wiki page linked at to bottom of the web page.

Ndscope Trends

Wed Nov 15 10:04:59 2023 INFO: Fill completed in 4min 56secs

Gerardo confirmed a good fill curbside.

Taking some time to do some opportunistic commissioning while LLO is down.

A contractor is on site to blow out our sprinklers. This work requires a large compressor to move air through the underground water lines near the OSB. Since we are observing and this specific noise source has not been vetted, we are marking the times here.

Rough start time: 1610 UTC

End time: Unfortunately we don't have a good end time. We would guess that this work would take roughly 30 minutes or less.

TITLE: 11/15 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 3mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.28 μm/s
QUICK SUMMARY: Locked for 6 hours, calm environment. Only alarm is the PT524B EX vacuum gauge that the vac team has been working on. Plans today consist of some commissioning time in the afternoon.

TITLE: 11/15 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Pretty quiet night, I ran a calibration suite, and the range has been steadily just under 160 Mpc. Lock time of 9:35 at the end of the shift.

03:02 dropped observing to run a calibration measurement alog74212

03:32 Back to NLN, the DARM fom timed out during the state transition and I had to restart it

03:33 back into Observing

I've seen the MC3 camera on NUC26 flash blue a few times.

I ran the analysis for the OPLEV charge measurements on ETMY that Rahul took this morning. The charge on ETMY is fairly stable, some small increases and decreases on the quadrants since the last measurement.

• H1 Observing at 158 Mpc
• We've been locked for 5:33
• I dropped us out of Observing from 03:03 to 03:33 to run a calibration measurement

Following the wiki I ran a calibration measurement while LLO was still relocking.

Starting with the BB

NLN calibration screenshot

03:02 NLN to NLN_CAL_MEAS

03:04 Broadband measurement started:

• /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20231115T030313Z.xml

03:09 Simulines:

PST start: 2023-11-14 19:09:20.280160 PST
UTC start: 2023-11-15 03:09:20.280160 UTC
GPS start: 1384052978.280160

2023-11-15 03:31:25,595 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20231115T030922Z.hdf5
2023-11-15 03:31:25,644 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20231115T030922Z.hdf5
2023-11-15 03:31:25,657 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20231115T030922Z.hdf5
2023-11-15 03:31:25,671 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20231115T030922Z.hdf5
2023-11-15 03:31:25,683 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20231115T030922Z.hdf5

PST end: 2023-11-14 19:31:25.778909 PST
UTC end: 2023-11-15 03:31:25.778909 UTC
GPS end: 1384054303.778909

Closes FAMIS 26066, last checked in alog73538

I had to change the env to get the plots to show as RyanS mentions in alog73432

TITLE: 11/15 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Maintenance day recovery was fairly straight forward, with one lock loss on the way to low noise. We've been locked for almost 2 hours now.
LOG:

• 1612 Lock loss to start maintenance
• 2130 Lost lock at Laser_Noise_Suppression.
• 2252 Observing. ISS 2nd loop had no issues this time (alog74204)

TITLE: 11/14 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 5mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.50 μm/s
QUICK SUMMARY:

• All systems look good, microseism still a little high, range looks to be rising
• In observing since 22:52 UTC

I checked the FC GR SUS/VCO crossover as shown in the attached figure. The crossover is about 60 Hz which is much larger than the blue reference on December 2022. This higher GR SUS gain could cause the instability during the transition from GR to IR. I reduced the GR SUS gain from 1 to 0.5 and the crossover became similar to the blue reference. I updated the SQZ_FC guardian to change this gain. Let's see if this helps the recent failure of FC GR to IR transition. 

Following up on the observtion that the SRCL FF is increasing the DARM low frequency (2-3 Hz) motion (73561) and that this motion might be the origin of non-stationary noise (73546), I designed a new high pass filter for SRCLFF and retuned the FF.

The new high pass gives us about 4 times less reinjection between 2 and 4 Hz, at the price of a phase rotation of 20 degrees at 10 Hz. Therefore the old SRCL FF was not performing well anymore. I did a noise inection and refit the FF filter. Fitting this filter is tricky and I don't think I got an optimal solution. But it looks like the new highpass with the new FF performs fine, is at least as effective as the old highpass and the old FF, by looking at the coherence between DARM and SRCL.

DARM RMS is improved a little between 3 and 4 Hz, so maybe we'll see some improvement in the non-stationary noise. We need to figure out what else is making DARM noise at 3.4 Hz. There is also an enormous line at 1.23 Hz that is the cause of most of DARM RMS. I think the bicoherence shows that the 1.23 Hz line is a source of noise modulation too.