Kevin, Sheila, Evan, Vicky

Summary: SQZ-OMC mode scans with hot OM2, and PSAMS 120/120 vs. 200/200. From this data, we should get single-bounce SQZ-OMC mode-matching with hot OM2, check SQZ readout losses (AS port throughput), and measure OMC losses via cavity visibility when locked/unlocked to the squeezer beam. With hot OM2, in sqz single bounce, SQZ-OMC mode-matching looks a bit better with PSAMS 120/120 than 200/200.

We'll ask Jennie W. to help us fit these SQZ-OMC mode scans. She can fit the double-peak in the 2xHOM, to give an accurate measure of SQZ-OMC mode-matching with hot OM2 and these two PSAMS settings. Here is just naively calculating mismatch from the relative power in TEM20 (TEM20/(TEM00 + TEM10/01 + TEM20)), and then calculating the total power not in TEM00 (ie 1-TEM00/(TEM00 + TEM10/01 + TEM20)), to get the following estimates on SQZ-OMC mode matching:

PSAMS 120/120, scan: 10/24/23 19:46:53 UTC + 200 seconds.
   --> mismatch ~ TEM20/peak_sums ~ 2%.      Total incl. mismatch + misalignment: 1-tem00/peak_sums ~ 8%.
PSAMS 200/200, scan: 10/24/23 19:04:57 UTC + 200 seconds.
   --> mismatch ~ TEM20/peak_sums ~ 5%.      Total incl. mismatch + misalignment: 1-tem00/peak_sums ~ 12%.

We will follow-up with analysis on OMC loss measurements based on cavity visibility, more accurate SQZ-OMC mode mismatches from these scans, and checking single-bounce SQZ powers through the AS port.

---------------------------------------------------------------------------

Notes:

• To begin SQZ-OMC mode scan, if SQZ-IFO is aligned -- with SRM aligned, SR2 + SR3 misaligned, Open sqz beam diverter, open fast shutter.
  • We started aligning with the PSL beam before we realized we forgot to open the fast shutter. For reference with this working, 10W PSL gave about  ASC_AS_{B,C}_DC_NSUM_OUT16 ~ 2000, ASC-AS_C_NSUM_OUT16~0.023, ASC-OMC_{A,B}_NSUM_OUT_DQ~0.023.  
  • With 75mW seed power into SQZT0 seed fiber, and opo at LOCKED_SEED_DITHER:
    • At the end, we measured the opo ir transmitted powers on sqzt7: OPO_IR_PD_LF_OUTPUT = 0.867mW, and OPO_IR_PD_DC_POWERMON = 0.856mW. This PD calibration was checked recently LHO:72761, Sept 2023.
    • 51 counts on ASC-AS_{A/B}_DC_NSUM_OUT16, 520e-6 counts on ASC-AS_C_NSUM_OUT16.
  • Then engaging DC3/4 centering loops worked. 
  • Then OMC QPD ASC set master gain to 0.02 (one click up), this aligned OM3 + OMC SUS. 
• Lock OMC on SQZ seed beam as carrier. Sheila manually walked through relevant OMC_LOCK guardian steps, including manual scan of OMC PZT2 volts to find sqz tem00 carrier.
  • Set trigger to 0 or 0.1 for OMC to lock on SQZ seed beam as the carrier 
• Turn on OMC QPD ASC servo to align OM3+OMC SUS to sqz beam. Master gain = 0.02 (one click up). With OMC QPD ASC, this brought DC sum = 0.4 now, which from DTT was the TEM00 peak height.
  • OMC scan here before walking OMC QPD alignment, PSAMS 200/200. DTT Refs 24 (dcpd sum), 25 (omc pzt). 
• Manually optimize OM3/OMC alignment with OMC locked on SQZ beam. This was after using & converging OMC QPD servos, then turning them off. Mostly walking yaw between OM3/OMC, then slightly in pitch. This manual walking improved OMC DCPD SUM transmission from 0.405 to 0.411 (~1.5% improvement).
• We can compare OMC visibility with OMC locked/unlocked from the SQZ beam. Follow up: calculate OMC losses from OMC-SQZ locked/unlocked visibility.
  • Locked GPS times, PSAMS 200/200: 1382207658 - 1382208152
  • Unlocked OMC:  Turned off integrator, boost, trigger, then moved PZT offset to off-resonance. 
  • Unlocked GPS times: 1382208285 - 1382208585
  • Dark noise: Turned off DC centering, fast shutter, sqz beam diverter.
  • Dark GPS times: 1382208720 - 1382208813
  • Then re-opened sqz beam diverter, opened fast shutter, DC centering loops DC3 + DC4 engaged, OMC QPD ASC master gain set to 0.02, converge OMC QPD ASC then freeze it, then scan OMC-PZT2_OFFSET (green slider). Use PZT2 offset scan to manually find SQZ TEM00 carrier. Turn ON OMC-LSC servo input, integrator, boost. Manually re-align OM3 + OMC SUS to optimize OMC-DCPD_SUM_OUT transmission. Again it was mostly yaw on OM3+OMC, then slightly pitch; manual walking improved alignment slightly (few %) again.
• PSAMS 200/200 data, with re-optimized alignment:
  • Locked GPS times, PSAMS 200/200: 1382209341 - 1382209482
  • OMC Scan, PSAMS 200/200. DTT Refs 26 (dcpd sum), 27 (omc pzt). Gpstime: 10/24/23 19:04:57 UTC, 100 second ramp.
  • Unlocked GPS times: 1382210147 - 1382210207
• Changed ZM4/5 PSAMS to 120/120, left DC3/4 centering ON. Re-lock OMC on seed beam (without touching OMC QPD ASC since we previously aligned/optimized it). With OMC-SQZ locked again and same OM3+OMC alignments as before, alignment with psams120/120 is not good. Some alignment confusion with OMC-LSC servo bank saturating. We turned back on OMC QPD ASC master gain 0.02 since we were kinda far off in the alignment. Here with hot OM2, the OMC transmission looks higher with PSAMS 120/120 than with PSAMS 200/200.
• PSAMS 120/120 data, with re-optimized alignment:
  • Locked GPS times, PSAMS 120/120: 1382211311 - 1382211449
  • Unlocked GPS times: 1382211637 - 1382211755
  • OMC Scan, PSAMS 120/120. DTT Refs 28 (dcpd sum), 29 (omc pzt). Gpstime: 10/24/23 19:46:53 UTC, 100 second ramp.

---------------------------------------------------------------------------

Some relevant alogs, as we try to piece together the SQZ-IFO, IFO-OMC, and SQZ-OMC mode matchings:

• Cold OM2, single bounce SQZ-OMC mode scans, alignment less controlled than this time: Jan 2023, LHO:66946.
  • Cold OM2, single bounce, PSAMS 200/200 ~ better SQZ-OMC mode-matching.
• SQZ-IFO full-lock frequency-dependent mode matching: LHO:73400 first pass, then LHO:73621 repeat with ASC frozen.
  • Hot OM2, full lock, PSAMS 200/200 ~ better SQZ-IFO(-OMC?) mode-matching. DARM SQZ noticeably flatter in this configuration.
  • 200/200 better also suggested by ADF transmission + more anti-squeezing.
• Hot OM2, single bounce SQZ-OMC mode scans (this alog):
  • Hot OM2, single bounce, PSAMS 120/120 ~ better SQZ-OMC mode-matching.

Summary - Camilla and I removed the running TCSX chiller and replaced it with a new ThermoFlex 1400 SN#1153600201231003.

We've been having some issues with the TCSX laser relocking itself during Observing (ex: alog73331). This seems to be due to inconsistent water temperature from two of our three chilers, causing the temperature of the laser to shift slightly. We've swapped out SN#0110193301120813 for the new chiller and sent off the spare chiller for service. We input the settings from the CO2Y chiller and it the new chiller fired right up and seems to be outputing correct flow and pressure. We'll keep an eye on it the next few days.

TITLE: 10/24 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 15mph Gusts, 12mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.18 μm/s
QUICK SUMMARY:
Full day of maintenance so Locking will start here after the channel H1:TCS-ITMX_HWS_LIVE_AQUISITION_GPSTIM SPM channel issue is resolved.
Tagging TCS.

I will be watching EY and EX temps. And OPO SDF Diffs when getting to Observing.

I also have H1:DAQ-H1EDC_CHAN_NOCON is 88 which seems like a few things are still not working correctly.
Tagging CDS.

TITLE: 10/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Maintenance is over and we are starting the process of getting back up.

Things to keep track of:

- EY heater tripped off at some point and caused temps to drop, should be good now but keep close eye on EY temps.

- There will be an OPO TEMP SDF, but shouldn't be any other sqz diffs
LOG:

15:00UTC Detector Locked for 28.5hrs, all SUS Charge measurements ran
23:00 Starting to move back towards locking    

Jordan, Mitchell

Today, we were able to install one of the new 150 l/s ion pumps on FC-CI, C1 cross. The Ion Pump/Tee/Angle valve assembly was pre-built in the staging building and then pumped down and leak checked. This assembly was stored under vacuum and then brought to the Filter Cavity Enclosure.

We closed FCV-3 (BSC3), FCV-5, FCV-6, and FCV-9 (HAM8) to isolate the C1 cross. Then closed the -Z axis GV on the C6 cross to isolate the ion pump port. We then vented the ion pump assembly with N2 and removed the angle valve/6" zero-length reducer on the cross, and installed the ion pump on the 6" CF port. A genie lift was used to lift/hold the ion pump while the connections were made.

Once installed, we used the leak detector/small turbo to pump down the assembly, and then helium leak tested the one CF connection that was made. There was no detectable signal above the helium background of 9.5E-11 Torr-l/s.

The ion pump was powered on locally, and quickly dropped to ~8E-8 Torr, using a new IPCMini controller. The -Z gate valve remains closed, and the rest of the FCT gate valves were reopened once the ion pump was leak checked and powered on. We will continue with the installation of the rest of the pumps in the LVEA in the following weeks.

LVEA swept.

The GV8 annulus ion pump was replaced today with a rebuilt, Galaxy-style pump body and a rebuilt old-style (fanless) MiniVac controller.  A controller swap took place last week, but upon powering on this controller with the new pump, I noticed that the polarity of the controller was positive.  So, I powered it down and swapped it with another rebuilt controller with negative polarity.  

The annulus system was pumped down to the mid e-5 torr range via local turbo and aux cart, at which time I powered on the ion pump.  Within a couple of minutes, the display on the controller showed 1-light of ion current (good).  The local turbo and aux cart were disconnected and the system restored to nominal Observing-run mode.  

WP11492 SUSPROC PI PLL model changes

Vladimir, Naoki, Erik, Dave

A new h1susprocpi model was installed. A DAQ restart was required

WP11485 h1hwsmsr disk replacement

Jonathan.

The failed 2TB HDD disk which is part of the /data raid was replaced with a 2TB SSD drive. At time of writing it is 70% done with the new disk rebuild.

Jonathan also cloned the boot disk. I verified that /data is being backed up to LDAS on a daily basis at 5am.

WP11478 Add HOFT and NOLINES H1 effective range to EPICS and DAQ.

Jonathan, Dave:

On Keith's suggestion, the HOFT and NOLINES versions of the H1 effective range were added to the dmt2epics IOC on h1fescript0. The MPC and GPS channels were also added to the H1EPICS_DMT.ini for inclusion into the DAQ. A DAQ restart was required.

WP11488 Deactivate opslogin

Jonathan

The old opslogin machine (not to be confused with opslogin0) was powered down.

WP11479 Add zotvac0 epics monitor channels to DAQ

Dave:

H1EPICS_CDSMON was modified to add zotvac0's channels. A DAQ restart was required.

DAQ Restart

Jonathan, Dave:

The DAQ was restarted for the above changes. This was a very messy restart.

0-leg was restarted. h1gds0 needed a second restart to sync its channel list.

EDC on h1susauxb123 was restarted

8 minutes later fw0 spontaneously restarted itself. At this point h1susauxb123 front end locked up, all models and EDC crashed.

Jonathan connected a local console to h1susauxb123, but there was no errors printed, the keyboard was unresponsive. h1susauxb123 was rebooted.

After the EDC came back online, the DAQ 1-leg was restarted.

h1gds1 needed a second restart to sync up its disks.

Here's a BruCo repot for GDS-CALIB_STRAIN_NOLINES from last night lock: https://ldas-jobs.ligo-wa.caltech.edu/~gabriele.vajente/bruco_1382152121_STRAIN/ 

Some highlights:

• CHARD_Y is likely the leading limiting factor between 10 and 20 Hz, while DHARD_Y is the main contributor to residual noise below 8 Hz (to be confirmed with another BruCo scan on LSC-DARM_IN1
  • maybe it's time to retune / recheck the A2L gains
• SRCL is also contributing to a good fraction of the noise between 10 and 20 Hz.
  • maybe we can try an iterative retuning of the SRCL FF
• MICH is also not too far between 10 and 50 Hz:
  • time to do an iterative retuning of MICH FF
• PRCL shows (surprisingly?) some coherence between 24 and 50 Hz: PRCL could explain the peaks and structures between 24 and 40 Hz
  • maybe coupling throuhg MICH? Or is it time to put back in operation a PRCL FF?

Large frequency bands are completely devoid of coherence.

Tue Oct 24 10:05:21 2023 INFO: Fill completed in 5min 18secs

Summary - Jim fixed it with a little shake.

We cycled through the various ISI state controls. The 1Hz line would start appearing when stage 1 is isolated. In any states below this point, we can clearly see the difference in the 'sensor response' of the local H1 L4C wrt T240 or CPS. While Jim was taking an olg measurement, the ISI tripped, which seem to have changed the response of the H1 L4C back to the nominal response, see the first pdf attached, showing the L4C/T240 local TF, before (p1) vs after (p2) the ISI trip. The 2nd pdf attached shows the ISI spectra in the isolated state before (p1) vs after (p2) the shake, no other changes.
We've had sticky L4Cs in the past and solved it in a similar way (see alog 38939), but the symptoms were much more obvious than a slight change in resonant frequency as we are seeing here.

Timeline of tests :

16:04 - 16:12 UTC ETMX ISI/HEPI OFFLINE
16:15 - 16:30 UTC HEPI ON / ETMX ISI OFFLINE
16:31 - 16:37 UTC HEPI ON /ETMX DAMPED
16:38 - 16:44 UTC HEPI ON / ETMX ST1 ISO - We can see the giant ~1Hz line
16:45 - 16:48 UTC HEPI ON/ ETMX ST1 ISO - H1 L4C gain 0.5 - sym filter off - ~1Hz line goes down
16:50 - 16:52 UTC HEPION/ETMX ST1/ST2 ISO - H1 L4C gain 0.5 - sym filter off
16:55 - 17:07 UTC Back to nominal
17:25 - Jim changing stage 1 Rz blend to noL4C
17:38 - Jim changing stage 1 Y blend to noL4C
18:00 - Jim measuring Rz olgf

Ref alog 73625

I replaced two disks on the h1hwsmsr system.

 * cloned a failing boot disk
 * replaced a failed raid drive that holds the image repository

I used clonezilla to replicate the boot disk.  Then after booting into the newly cloned disk I replaced the failed raid disk.  At this point in time the data is being automatically replicated onto the new disk, it should take a few hours.

I prepared a new filter module with resonant gains at 2.8 Hz and 3.4 Hz. This can be tried tomorrow (on during some commissioning time) to reduce the DARM RMS and see if it helps the non-stationary noise.

The new FM is loaded into DARM2 FM1 "RG2.8-3.4". It is not engaged now.

For future reference, here are the FMs that are used during lock acquisition:

DARM1: FM1 FM2 FM3 FM4 FM7 FM9 FM10

DARM2: FM3 FM4 FM5 FM6 FM7 FM8 FM9 FM10

leaving DARM1 FM5,6,8 and DARM2 FM1,2 unused

WP #11489, and #11492 (not marked as Tuesday Maintinence as LHO apparently doesn't track that).

I have altered the h1susprocpi model in the follownig ways:

• Removed hard-coded amplitude limit of 10 (and the addition of a pre-limit amplitude offset and a post-limit amplitude offset)
• Added a filter bank AMP_FINAL in its place. This will serve as the output signal filtering/offsetting/limiting.
• Restored the PLL_SEL_MTRX size to 3 and reinstated the option to bypass PLL completely, linked to the input to the PLL blocks. Now you can use raw signals in the damping loop once again if you are having difficulties with the PLL locking.

These changes affected libraries:

• PLL_MASTER/PLL (first 2 changes)
• PI_MASTER_V2/PLL_BY_MODE (last change)

Changes will come in when the model is restarted on the h1oaf0 and the DAQ is restarted, as the new filter block adds channels.

Using two periods of quiet time during the last couple of days (1381575618 + 3600s, 1381550418 + 3600s) I computed the usual coherences:

https://ldas-jobs.ligo-wa.caltech.edu/~gabriele.vajente/bruco_STRAIN_1381550418/
https://ldas-jobs.ligo-wa.caltech.edu/~gabriele.vajente/bruco_STRAIN_1381575618/

The most interesting observation is that, for the first time as far as I can remember, there is no coherence above threshold with any channels for wide bands in the low frequency range, notably between 20 and 30 Hz, and also for many bands above 50 Hz. I'll assume for now that most of the noise above ~50 Hz is explained by thermal noise and quantum noise, and focus on the low frequency range (<50 Hz).

Looking at the PSDs for the two hour-long times, the noise belowe 50 Hz seems to be quite repeatable, and follows closely a 1/f^4 slope. Looking at a spectrogram (especially when whitened with the median), one can see that there is still some non-stationary noise, although not very large. So it seems to me that the noise below ~50 Hz is made up o some stationary 1/f^4 unknown noise (not coherent with any of the 4000+ auxiliary channels we record) and some non-stationary noise. This is not hard evidence, but an interesting observation.

Concerning the non-stationary noise, I think there is evidence that it's correlated with the DARM low frequency RMS. I computed the GDS-CALIB RMS between 20 and 50 Hz (whitened to the median to weight equally the frequency bins even though the PSD has a steep slope), and the LSC_DARM_IN1 RMS between 2.5 and 3.5 Hz (I tried a few different bands and this is the best). There is a clear correlation between the two RMS, as shown in a scatter plot, where every dot is the RMS computed over 5 seconds of data, using a spectrogram.