[Julian, Naoki, Camilla, Sheila, Vicky]

Summary to get SQZ alignment beam: Launched 76mW into seed fiber, ~25 mW incident on opo cavity, ~0.85 mW transmitted through opo cavity. Had to find opo transmission past the VIP, for this we used green SK path as a reference. This ~0.85 mW opo transmission was bright on an IR card at the HAM5 gate valve, and enough to iris the SQZ beam in HAM7 and HAM6 (for OMC work 75512). DC 3/4 centering loops engaged easily, then OMC A/B QPD's saw the sqz beam.

----------- Notes from today ------------------------------------------

Launched power into SEED fiber (SQZT0): 76 mW

OPO IR REFL (CLF_TRIG_REFL_DC_POWERMON @ SQZT7): 24.8mW   (when opo is dither-locked).

Fiber rejected power PD in HAM7 (CLF_REFL_REJ) is 5.3 mW.
  -->  Seed fiber coupling: ~34% of the seed fiber launched power was incident on the opo cavity. 
  -->  40% coupling through fiber, ~6% mispolarized and rejected after fiber. This is similar to recent fiber alignment 75344, even after more recent on-table work 75486.

We had to find the OPO IR transmitted beam after the VIP. Nothing at first despite restoring suspensions 75502. Notes to self on what worked to find the SQZ beam post-vent:

• Started with no opo trans after the VIP, despite checking SQZT7 periscopes and the HAM7 RLF QPD's (which we use for FC WFS).
• 75502 saw ZMs had shifted after vent. Naoki 1) offloaded all FC+SQZ ASC and set all PSAMS offsets back to "nominal", then 2) he and Austin restored ZM1-6 + FC1 slider values to the same P/Y damp values as we last had in observe. Still did not see beam past the VIP (nothing on RLF QPD's, nothing on SQZT7 IR camera).
• SK path was helpful to find the VIP transmitted beam.
• Looking at the bottom SK periscope mirror on SQZT7 like here, we walked FC1 P/Y sliders to overlap FC_GR_REFL (which sees FC REFL), with OPO_REFL (which does not see FC REFL, and thus is a good alignment reference for the FC REFL path including ZM1-2-3-FC1).
• Used FC1 P/Y sliders to overlap FC_GR_REFL with OPO_REFL (looking at an IR card on the periscope lower mirror). While doing this, we found OPO IR TRANS on the RLF QPD's.
• Then we walked FC1 and ZM3 to maximize transmitted power, ie OPO_IR_DC_POWERMON. Not totally optimized, but seemed reasonable to keep going.

OPO IR TRANS (OPO_IR_PD_DC_POWERMON @ SQZT7): 0.85 mW  -- Just before opening the HAM7/5 gate valves. Opened the beam diverter, SQZ beam was bright on an IR card held at the HAM5 gate valve.

After opening gate valve, immediately saw the beam on AS A/B/C QPDs.

ASC-AS_A/B_DC_SUM_OUTPUT ~ 60.  ASC-AS_C_NSUM_OUT16 ~ 0.65-0.67.  

HAM6 crew irising SQZ beam, 75512.

HAM7 crew irising SQZ beam. Julian has some photos of HAM6 and HAM7 irses. Sheila -- looks like there is some clipping on the VIP (we have not totally optimized FC_REFL path slider alignments post-vent, just found the beam). Revisit this FC REFL alignment later.

Engaged DC 3/4 centering. It just worked. Control signals near 0. 

We see the beam on the OMC QPD's, power is consistent with ASC-AS_C power, around 300-400e-6 on each OMC QPD A/B. Power goes away when SQZ beam diverter is closed. See omc powers screenshot with as_wfs powers.

TO-DO SQZ work later:

• more photos of HAM7 irises
• measure sqz beam powers with power meter
• undo VIP clipping (using e.g. FC1/ZM3) - we didn't fully optimize this FC REFL alignment yet after venting.

TITLE: 01/23 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:

• Today focused on OMC work with LVEA switching to laser SAFE for the day.
• EX vented for baffle work tomorrow.  
• EY is Laser HAZARD for PCAL work (and transitioned back to SAFE afterward).
• LVEA back to HAZARD

LOG:

• 1545-1642 LVEA cleaning & HAM6 all clean (karen.kim)
  • 1715-1818 EX maintenance cleaning (kim)
  • 1738-1921 EY.MY maintenance cleaning (karen)
  • 1838-1953 More LVEA cleaning (kim)
• 1600 Snow removal for Y-arm/EY (randy)
• 1608 FAMIS checks in LVEA and then down Yarm and then Xarm (Chris)
• 1612 Fire alarm contractor arrives for Tyler
• 1622-1641 Transitioning LVEA to Laser (Upgrade) SAFE! (tj)
  • Also moved a dust monitor near HAM3 (tj)
• 1632-1647 Parts check in East Bay (jordan)
• 1655-1709 TCS Chiller checks/fill (corey)
• 1701 OMC swap @HAM6 (keita, betsy, rahul, koji)
  • 1748-1807 High dust counts noticed, TJ heading out to check.  (Mentioned counts were low/normal when he came back.)
  • Lunch break around 1945
• 1723-1741 Dew point measurements in lvea (gerardo)
• 1723-1729 Grabbing parts in LVEA (jordan)
• 1727-2330 Prep for EX baffle work (robert)
  • Needs to wait until VAC team is done venting
• 1741-1956 RGA work at EX (gerardo, jordan)
  • 1956 lunch break
• 1745-1917 Slow controls upgrade + DAQ restart (daniel, dave)
• 1754-1935 LN2 delivery for MX (norco)
• 1812 VAC work while laser SAFE (janos)
• 1817-1848 Squeezer slow controls power supply swap (marc)
• 1827-1845 Grabbing part from Filter Cavity Tube Enclosure (travis)
• 1842-1901 LVEA walkthru (richard)
• 1845-1911 Looking at removed OMC (tj, oli, austin, ryanC)
  • 1916-1932 Another look (ryanS,vicky, naoki)
• 1907-2011 FARO work (jason, ryanC)
• 1925-2252 EX lights (ken)
• 1928-1946 LVEA recon (travis)
• 1943/afternoon:  Moving equipment to EY for Wind Fence (randy)
• 2007-2012 Checking on patch panels at CER (jonathan)
• 2010 PCal Maintenance at EX & EY (tony, rick)
• 2040-2254 Baffle assy work in lvea (mitch)
• 2103-2327 Optics Lab and then off to SQZT7 (vicky, daniel, naoki)
• 2103-2303 HAM6 OMC team return (rahul, koji, keita, betsy, Ali)
• 2112-2146 Disabling high Voltage at EX (fil)
  • Confirmed EX Picomotor 
• 2114-2344 FARO work (jason, ryanC, tyler)
• 2128-2300 TCS Laser swap prep (tj, camilla)
• 2129-2300 Checking out electronics for accelerometer for making a work permit (marc.jamari)
• 2152 Venting EX (travis.janos.gerardo.jordan)
  • Took EX ISI to:  ISI_DAMPED_HEPI_OFFLINE 
• 2245 EY to laser HAZARD (tony)
• 2303-2348 Rahul running OMC SUS rubbing measurements
• 2345-2350 Transitioning LVEA back to HAZARD (camilla)
• 2345-0000 Searching for vacuum cleaner in lvea (tj)
• 2347 Restoring purge air (Betsy)
• 2351 Turning on the Squeezer laser (camilla)
• 2354 SQZT0 & maybe SQZT7 work  (vicky, daniel, naoki) 

WP 11645
Procedure M1300464

The following high voltage power supplies/electronics were powered off in preparation for the EX vent.

1. EX ESD HV and Low Voltage Chassis
2. EX Ring Heater

F. Clara, G. Moreno

Late entry. Activities on Jan 22nd:
- The HAM7 X+ and X- doors have been removed
- The purge air was switched on at EX
- GV20 (at EX) was closed - the GV struggled with closing, but in the end it seems to be OK
- Electrically 1, mechanically both 2 spare roughing stations are finished
- VPW C+B door issue - 2 screws stuck, tomorrow will open it: this load has some blanks and new Hepta headers, which will be also needed

At 10:33 the DAQ 0-leg was restarted, followed at 10:38 by the 1-leg. The DAQ restart was for two EDC changes: Daniel's new slow controls CS_SQZ channels and Patrick's additional FMCS channels.

The EDC was restarted at 10:33.

A new SQZ SDF monitor.req file was installed the and h1syscssqzsdf service was restarted.

Tue Jan 23 10:06:58 2024 INFO: Fill completed in 6min 54secs

Gerardo confirmed a good fill curbside.

Addressed TCS Chillers (Tues [Jan23] 855-910pm local) & CLOSED FAMIS #26166:

• TCSx Chiller:  Had level of 29.4 cm.  Added 310mL for 30.2cm.
• TCSy Chiller:  Had level of 9.8 cm.  Added 85mL for 10.0cm.
• There was no water in the small cup under the slow leak.

TITLE: 01/23 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: EARTHQUAKE
    Wind: 6mph Gusts, 3mph 5min avg
    Primary useism: 0.22 μm/s
    Secondary useism: 0.15 μm/s
QUICK SUMMARY:

• LVEA transitions to SAFE today!!
• HAM7 SQZ work continues today.
• HAM6 OMC swap continues with extraction next.
• About 90min ago we had a 6.3M EQ from Vanuatu area.

Workstations were updated and rebooted.  This was an OS package update.  Conda packages were not updated.

[Rahul, Keita, Betsy, Koji]

Preparation work to extract the existing OMC has been completed. We will continue with the OMC extraction tomorrow morning.
The overall work procedure for the OMC replacement is summarized in G231106 https://dcc.ligo.org/LIGO-G231106.

= OMC shroud panel removal =

While waiting for the beam from the squeezer to come, we started the removal of the OMC shroud panel in parallel. The work was done along with the procedure E1600164.
The removed panels were placed on a stainless steel table in the HEPA booth of HAM6 (Attachment 1). The panels were not covered to prevent accidental placement of objects on them.

During the work, a beam dump was removed from the table to make the removal work possible. This beam dump is to kill one of the weak transmissions of the OMC.
Betsy took the photo record of the location, but it is safely trivial how it should be aligned.

= SQZ beam marking and alignment =

The beam was delivered to HAM6 and was pinned down with two irises on the ISI table.
The irises were placed just after the beam entered HAM6 (next to OM2) and just before OM1 (next to the fast shutter).
This means that these indicators are not affected by the alignment in HAM6.
They were placed by eyeballing, so their precision was as such. By default, both the irises were set to the maximum opening.

Next, the beam alignment was servoed towards the WFS heads using the DC centering ASC loops.
As soon as the control was applied, both QPDA and QPDB of OMC showed significant signals with total light level of ~1e-3 (Attachment 2).
When the light was blocked (at the squeezer?), the value dropped to almost zero, confirming that this was a real beam.
This is very good news as we'll be able to find the beam arrival using the OMC QPDs when we try to align the new OMC.

= Holding suspension mass =

Next, we proceeded to hold the suspension masses. Rahul and Koji worked in the chamber on the ISI table for the following operations.

To hold the intermediate mass:

• First, the top blade was fixed with stopper screws.
• Next, we tried to fix the middle mass with two 1/4-20 nuts, but this caused some wobbling of the suspension. So, we first decided to fix the middle mass with smaller side EQ-stops. This process has not been described in E1600164. (to be updated)
• Once the middle mass was fixed horizontally, the vertical dof was also fixed firmly with the small EQ-stops and the 1/4-20 hex nuts.

Then, moved onto fixing the OMC:

• The bottom EQ stop for the OMC was left as they could not touch the OMC. The side (long side) EQ stops were extended and are holding the OMC horizontally.
• The Top EQ stops for the OMC were removed by removing the L-shaped brackets on both sides.

= Removing the electronic cables from the OMC =

Upon removing the electronics cables, one person held the cable harness on the OMC breadboard to prevent the OMC from wobbling too much.
The removed cables were wrapped around the top part of the suspension frame to keep them out of the way of the further work.

At this point, it was just at 5pm, so we exited from the chamber.

Next Steps:

• Extraction of the OMC
• Migration of the balance masses to the new OMC
• Final cleaning of the new OMC
• New OMC installation

TITLE: 01/22 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC (covering for the latter half of the shift)
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY: HAM7 irises are in place, OMC work in HAM6 is ongoing.
LOG:                                                                                                     

WP 11635
WP 11637

The following high voltage power supplies were powered on this morning:

1. HAM7 - PZT and P-Sams
2. HAM6 - PZT and Fast Shutter

The pressure interlock system bypassed.

Camera 20 failed and was restarted.  The server runs on h1digivideo1, but was not being monitored by monit.  That's been corrected.

The Calibration group has been working hard to produce and release the LHO uncertainty budget for the first half of O4a. The case at LHO has proven to be significantly more involved than LLO's for a variety of reasons. 


LHO started the run at a much higher power, which led to a much more severe "thermalization" effect for the first hours of each lock stretch
the IFO was quite unstable at 76W, which meant that we had more locklosses & therefore spent more time "thermalizing"
the power was lowered to 60W in late June
there were signifcant periods during which we could not trust the online TDCFs
 


There are probably a few more reasons that I'm not recalling right now. The most challenge has been dealing with the thermalization periods as they contribute the most to our uncertainty at low frequencies. Moreover, the thermalization effect is very different between the time periods at which the IFO was operating at 76W compared to when it was operating at 60W.

As part of uncertainty generation we processed the high frequency roaming Pcal lines to measure the sensing function and inform the uncertainty budget from 1-5 kHz. More on the implementation details of this process will be shared in another alog and linked here as a comment. One detail worth noting here has to do with the fact that for O4 we're using a new report-based calibration infrastructure based on pyDARM. Each time a new set of calibration measurements are taken, the data gets processed (by either a member of the Calibration team or an LHO operator) using the pyDARM tools. The data processing step produces a report PDF file and a multitude of by-product intermediate data files. These files and the PDF are all collectively called a "report."

In December, I provided Lilli with a set of re-generated reports that included the newly processed high frequency roaming line data at LHO. This is similar to the work-flow the Calibration group employed for LLO earlier in the run. She then calculated uncertainty budgets for the first half of O4a, ending on October 1, 2023. However, all uncertainty envelopes before GPS 1371427218 were clearly wrong. As an example, the last "bad" GPS time is 1371394818 (calibration_uncertainty_H1_1371394818.png) and the first "good" GPS time is 1371427218 (calibration_uncertainty_H1_1371427218.png). 

As an additional check, Lilli used the systematic error monitoring lines to compare them against and overlay them over the uncertainty budget. The uncertainty checks can be found at: https://ldas-jobs.ligo-wa.caltech.edu/~ling.sun/lho_unc_v0.5/monitoring/. Looking specifically at the checks corresponding to the "last bad" and "first good" GPS times, we can see that at GPS 1371394818 (uncertainty_consistency_check_H1_13713948180_13713984180_GDS-CALIB_STRAIN.png), the envelope disagrees with the data taken directly using the systematic error lines. Meanwhile, the same check at GPS 1371427218 (uncertainty_consistency_check_H1_13714272180_13714308180_GDS-CALIB_STRAIN.png) does match the direct measurement much more closely. This indicates that 1.) the uncertainty envelope during the "bad" times is likely wrong (good news) and 2.) that there is probably a bug in how the data that is passed to the uncertainty envelope generation is processed (i.e. a bug or bad parameter in the report generation at LHO).

Over the past few weeks, I've been trying to find this bug. I first ruled out mismatches between the front end settings (filter files, FM slots, gains, etc.) between the CAL-CS copy of the DARM loop, the actual DARM loop, and the pyDARM parameter files that are meant to mirror the (actual) DARM loop (except, of course, for the 3.2kHz pole that we already knew was missing from CAL-CS at the time).

It turns out that our suspicion that there was a problem in the report generation was correct. This bug caused every report's pyDARM_H1.ini file to be populated with wrong MCMC-fitted parameters for both the sensing and actuation functions from the start of O4a until roughly June 22, 2023. There are four places that the pyDARM report system records fitted MCMC values: the PDF report, an MCMC JSON file dump, an MCMC HDF5 file dump (that includes the entire MCMC chain), and the pyDARM parameter file that has been populated with the new parameters. I was able to identify the issue by comparing these four different data products against each other to check for self-consistency. In the affected period, they all matched except for the pydarm_H1.ini files. The tools I wrote for this is attached as check_ini_vs_chain.py and its output is attached as out.txt. The output compares the fitted sensing and actuation parameters for all reports marked valid so far in O4a.

Fixing this bug for report 20230620T234012Z and regenerating the uncertainty envelope and the consistency check with the systematic error lines at GPS 1371394818 resolves the discrepancy. See uncertainty_consistency_check_H1_1371391218_1371394818_GDS-CALIB_STRAIN.png.

TITLE: 01/22 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:

Big Tasks Of The Day:  (1) HAM7 doors taken off, (2) HAM7 work begins, & (3) Laser Hazard in LVEA / EX is back to SAFE
LOG:

• Alarm Handler:
  • 1643 Zone 2A temperature
• 1520 Furniture moving work (randy)
• 1617-1956 Technical cleaning around HAM7 (LVEA) (karen & kim)
• 1632-1933 HAM7 doors morning (jordan, gerardo)
  • 1632jordan, 1652gerardo, 
  • HAM7 ISI tripped
• 1638 FARO system surveying (jason, ryanC)
• 1646 Cable search around CER & HAM6 for HAM7 alignment later (fil)
• 1652 Turning down purge air on output arm (gerardo)
• 1655 Prep & tool search in optics lab (camilla)
• 1700-1858 HAM6 SUS TFs (rahul)
• 1706-1715 LVEA & FARO team checks (tyler)
• 1721 Sealing up PCal & transitioning EX to laser SAFE (tony)
  • 1755 EX laser SAFE!
• 1735 SEI_ENV node work (tj)
• 1738-1741 Dropping off Contamination Control kit at HAM6/7 (mitch)
• 1754-1801 West Bay trip to grab tools for EX (mitch)
• 1759 Betsy beginning her in/out of LVEA for vent activities
  • 1759 Taking Eric O to check out H7 door work.
• 1801-1843 Dropping off EX kits for EX flange baffle work later (mitch)
• 1805 Ramped down the PZTs (or was it a P-SAMS thing?) to zero in prep for High Voltage being turned ON (sheila)
• 1825 Incoming 7.0EQ from Kyrgyzstan area.
• 1840 Locking HAM7 ISI (jim)
• 1847 High voltage (pzt/P-SAMS) turned ON (fil)
• HAM6 SQZ work
  • 1856 Prep/staging for HAM6 OMC work (koji)
  • 1935 Prep/staging for HAM6 OMC (rahul)
• HAM7 SQZ work
  • 1943 Moving ZMs around (austin)
  • HAM7 team beginning in-chamber work (sheila, julian, naoki, vicky, camilla)
  • Tried to find a Humidity sensor for in-chamber work....found some in Richard's office, Betsy grabbed them, and Betsy running a RH sensor out to the HAM7 team.
• 1906 Quick visit in the PCal lab (tony)
• 1932 Prep for Transitioning LVEA to Laser SAFE!!! (Camilla)
• 2057 Running equipment down for Wind Fence at EY (randy)
• (Handed off my shift to TJ at 1pm PST)

Ibrahim, TJ, Camilla, Naoki,

Looking at how the ZM4,5,6 alignment has shifted both with the vent and recent temperature changes in the LVEA.

Attached is ZM4/5 P/Y alignment since the last time we were SQZing to vented now,  there is large changes of ZM5 (470urad in Pit and 230urad in Yaw). Alignment sliders haven't changed but SQZ ASC would have been changing some alignment when the IFO was locked.

ZM6 has large changes (1300urad in Pit and 280urad in Yaw). Currently DAMPED but alignment sliders are the same. Edit: DAMPED turns off the alignment sliders, once Austin brought back to ALIGNED it had moved <100urad.

We expect some changes from bouyancy of air. The HAM7 SUS are currently  "aligned" with the doors being taken off HAM7. Jim hasn't locked the ISI yet. Looking at ZM4,5,6 alignment, last vent, IFO locked, and now.

Ibrahim is looking at temperatures and alignment since our last vent.

Camilla, Naoki, Sheila, Nutsinee

We did a repeat of the measurement set from 73621 with OM2 cold.  For a summary, Camilla's plot shows 200V/200V PSAMs setting with solid lines and 120V/120V as dashed lines. There is a stronger frequency dependence for the 120V/120V settings, which confirms what we saw with OM2 hot, that 200V/200V has better mode matching and less frequency dependent SQZ rotation. (This plot is a direct comparison to October's data. )

The third attachment is a plot that shows that the squeezing angle that maximizes the squeezing at 2kHz is not the same as the one that maximizes the squeezing at 200Hz, (green traces are optimized for 2kHz, blue traces are optimized for 200Hz, solid is 200V/200V and dashed is 120V/120V), you can see that the frequency dependence is larger for 120V/120V.

The fith attachment compares OM2 hot vs OM2 cold for antisqueeze and squeezing, with PSAMS at 200V/200V.  There is less anti-squeezing with OM2 hot, which could be due to a difference in nonlinear gain or reduced readout losses.  The green traces show that the squeezing level is similar, although the no sqz spectra is also different between the two times. 

times:

• NO SQZ: 2023/12/20 18:00:16- 18:20:40 UTC  (during this time we reset AS42 offsets see attached, and measured NLG 18.1) ref0
• SQZ: PSAMS 200/200 CLF RF6 203.85 deg 18:24:30- 18:31:33 (ASC running) ref19
• ASQZ:PSAMS 200/200 CLF RF6 270.22 deg 18:35:00-18:40:00 (ASC IFO and FC off) ref20
• MID SQZ+: PSAMS200/200 CLF RF6 237.04 deg 18:42:00-18:47:10 ref 21
• MID SQZ-: PSAMS 200/200 CLF RF 89.13 deg 18:50:40-18:56:00 ref 22
• repeat sqz slightly better at low F worse at high F: PSAMS 200/200 CLF RF6 194.37 deg 19:00:30-19:07:20 ref 23 (a couple of glitches happened)  (suggests we should be watching 100Hz to tune SQZ ANG instead of 1kHz)
• turned ASC back on, moved PSAMS to 120/120, waited about 3 minutes for the AS42 to converge. 
• SQZ PSAMs 120/120 CLF RF6 214.28 deg 19:18:30-19:24:00 ref 24(This is the DEMOD angle that gave the best sqz at 2kHz, changing the PSAMs changes which demod angle this best squeezing is at)
• SQZ PSAMs 120/120 CLF RF6 194.37 deg 19:27:40-19:33:20 ref 25  (better SQZ at 200Hz)
• ASQZ PSAMS 120/120 CLF RF6 100.5 deg CLF servo sign flipped 19:42:20-19:47:40 ref 26
• MID SQZ PSAMS 120/120 CLF RF6 237.04 deg 19:49:10- 19-54:50 ref 27
• MID SQZ PSAMS 120/120 CLF RF6 89.13 deg 19:56:10 - 20:01:40 ref 28

Since our ASQZ with PSAMS 200/200 was a little lower than with 120/120, and that seemed inconsistent with our sqz data and our previous measurement with OM2 hot, we went back to SQZ with PSAMS 200/200, ran ASC then turned it off, and checked the sqz angle carefully. This did give a little more anti-sqz to replace the reference 20 above:

• ASQZ PSAMS 200/200 CLF RF6 100.5 deg CLF servo flipped 20:13:15- 20:19:30 ref 29

Camilla saved these references in userapps/sqz/Templates/dtt/DARM/PSAMS_tests_Dec2023.xml