Previously done 75898 - closes FAMIS#27784

Both TCSX and TCSY were at their max fill level, so I did not add any water. There was no leaking.

Patrick, Jonathan, Erik, Dave:

We are working on an issue with some cameras on the new video server (h1digivideo3) becoming unstable over the past few weeks, resulting in their images going blue-screen until their server process is restarted.

I've opened FRS30615 for this issue.

TITLE: 03/06 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 1mph Gusts, 0mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.16 μm/s
QUICK SUMMARY:

H1 still struggling with locking post vent. Troubleshooting continues, starting off the morning with an initial alignment.

Naoki, Daniel, Nutsinee

The newly installed squeezer (iLIGO) PMC took a while to lock so we investigated. Turned out the PMC had difficulty locking when the PZT was scanning from 0-100V but was able to lock reliably when the PZT turned around from 100-0V. We maybe seeing something we've seen before in the OPO where some element inside of the PMC heated up, expanded the cavity length against the PZT movement from 0-100V making it difficult to grab a lock. We triggered the PMC lock on the Refl diode and the channel we used has 2kHz sampling rate. Beckhoff trigger is running at 1kHz. The resonance passed by so quickly that sometimes if we're lucky the trigger would work but most of the time it didn't.

However, when scanning from 100-0V the cavity expansion help extended the period that light stored inside the cavity, making it easier to grab lock. Now that the PMC is better aligned, the effect became more severe.

The scan shows PMC refl and trans having a much narrower dip/peak when scaning from 0-100V compared to 100-0V.

We revert the scan from 0-100V to 100-0V so it starts from the top. Changes related to PMC scan has been accepted in the SDF.

In case of the OPO the cavity self-lock due to heating within the crystal. In case of PMC we have about ~100mW of light missing that can't be accounted for. We believe this amount of light maybe absorbed somewhere inside of the PMC. 

Elenna, Jenne, Gabriele, Matt, Trent, Louis, Georgia

- Jenne and I checked the fast shutter and ran the fast_shutter test (SYS -> AS port protection -> run)

- After the initial alignment (alog here) we got through green arms locking at up to CHECK_MICH_FRINGES. When we tried to do PRMI there was a timer that kept taking it back to MICH fringes since the POP90 buildups were so poor. On the AS_AIR camera the alignment looks bad in yaw.

- We edited ISC_LOCK line 1353 to lower the threshold for PRMI flashes on POPAIR_B_RF90 from 20 to 4.

- We ran the dark offsets script with the IMC offline and the ALS shuttered (sdf screenshots here), and started locking again.

- The Y arm was finicky, we struggled to get the flashes above 0.6... We lowered the PD threshold in the ALS Y PDH (H1:ALS-Y_REFL_LOCK_TRANSPDNORMTHRESH) from 0.7 to 0.6.

- We also lowered the threshold in ALS_ARM gen_INCREASE_FLASHES from 0.9 to 0.6.... feels like cheating, maybe the alignment onto ISCT1 is off? The camera alignment for ALS_Y also looks bad (see screenshot)

- Even though we did an initial alignment earlier today, the PRMI flashes are bad and the MICH fringes don't look great. PRMI_ASC caused a couple of locklosses, so we took the guardian to PRMI_LOCKED and tried aligning it by hand. Elenna aligned PRM and BS, but the buildups and camera indicated bad pitch alignment.

- We re-ran initial alignment, and then the guardian took us straight up to PRMI_ASC, DRMI also locked easily! POPAIR_RF18 was a little noisy.

- We started the CARM offset reduction sequence but lost lock at DHARD_WFS, the two arms were very different (higher build up for Y arm), when DHARD came on the arms were pulled closer together but we lost RF9, and we lost lock.

- We decided to stop at DARM_TO_RF, step the X arm (X hard) closer using the move_arm_dev script and fix PRM and SRM alignment to increase the buildups.

- While we stepped the arm and adjusted PRM, the green arms lost lock. We think we might be aligning the whole IFO to some bad ITM alignments (how accurately aligned are they after the baffle PD alignment script?)

We decided to call it a night at this point.

We lost dmt displays in the control room around 12:16 today.  John Zweizig and I have been working on this for the past few hours.

What seems to have happened is after a reboot h1dmt1 is having problems with redundant data streams (for reference the identically configured h1dmt2 has no issue).  When we disable one of the input streams it is able to receive data.  At this point we have disabled one of the streams and will look at it more in the morning.

Trent, Matt, Georgia, Jennie W

fit_peak.py takes a chosen field and mode peak and fits a lorentzian curve to it. The problem with it was that all important arguments like gps_time, duration, field, and mode were all hard coded. We wanted to edit this code so that you can input these values as command line arguments. This new file fit_peak_w_args.py lives in my forked branch of labutils tgayer.

This code also calculates the finesse of the cavity from the calculated full width half max and prints it out to the command line.

We would also like to further improve this code by changing the fit so that we factor in the baseline of the data so that the tails of the fit better match the baseline.

An example of what you run on the command line [python3 /ligo/gitcommon/labutils/omc_scan/fit_peak_w_args.py 1393542033 80 "two watt single bounce side bands nominal" "single bounce" "carrier" "00"]

[/ligo/gitcommon/labutils/omc_scan/fit_peak.py]

[/ligo/gitcommon/labutils/omc_scan/fit_peak_w_args.py]

Matthew, Jennie W, Gabriele

In the initialization of the OMCscan code (which gets OMC scan data, analyzes it and then plots it), I updated several values to reflect the transition from OMC003 to OMC001, so that omc analyses are accurately done. For example, several small changes include:

• FSR -> 264.97 MHz
• Finesse --> 426.96
• TMSv --> 58.05 MHz
• TMSh --> 57.94 MHz
• PZT2response --> 6.435 MHz/V (this change is from 5.9 MHz/V, which is puzzling because the previous PZT2response [12.73 nm/V] is quite close to the new one [12.92 nm/V])

The values were obtained from T1500060 Table 19, which report the OMC optical test results for OMC001; note: the conversion from nm/V to MHz/V is found by the relation delta(f)/f = delta(L)/L, where delta(L) is 2*PZTresponse in nm/V, L is the round-trip cavity length, and f is 1064nm converted to MHz

Georgia, Jenne, Gabriele, Elenna

We ran the dark offset script, but this time made sure to SDF everything appropriately. Screenshots attached.

TITLE: 03/05 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 8mph Gusts, 6mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY:

Since Lunch time the control room has been enthralled with trying to relock H1 for the first time since Jan16th!
FIlter Tube Cavity is still closed.

LOCKING Notes:
TMS Alignment was tampered with before we realized that the Shutters were closed.
Using Camilla's alog with instructions on dithering alog 62024.
ALS Trouble Shooting before running TMS ITM and ETM Baffle Scripts.
ITMY Baffle PD4 was "Broken?"
Got light onto ETMY Baffle 1 and turned OFF the offsets to bring the light back to center then realigned ETMY via Guardian.

TMSX Baffle align script worked fine.
ITMX Baffle align Script failed to find any light.
But we didn't notice this and continued onto ETMX Baffle Align  which found light.
Unfortunately this was NOT ALS light that we saw on ETMX. Sheila and I decided to Shutter ALS and the light we found on ETMX Baffle 1 did not go away when shuttering ALS shutter on X arm.
Troubleshooting ALS X some more: We then used the Oplevs from January to find a good spot to take ETMX. 
First Light on ASLX 22:44 UTC
TroubleShooting PLL Problems that are making the X arm hard to lock. Eventually I got the ALSX beam spot looking as good as I could and then paused while Ryan S checked out the PLL.
Ryan S found out that the Beckhoff reboot turned off ALSX fiber Servo compensation. Checking out the SDF there was a dead give away that the problem was caused by a Beckhoff reboot. The date of the Change was Sun Dec 31 16:00:00 1989 which was the big clue.

DigiVideo3 Needed to be rebooted again.

Technical Notes:

ETMX Oplev positions AFTER we have good ALSX beam Spot:
H1:SUS-ETMX_L3_OPLEV_PIT_OUTPUT = -5
H1:SUS-ETMX_L3_OPLEV_YAW_OUTPUT = -12

ITMX Oplev positions AFTER we have good ALSX beam Spot:
H1:SUS-ITMX_L3_OPLEV_PIT_OUTPUT = -7
H1:SUS-ITMX_L3_OPLEV_YAW_OUTPUT = -1

ETMY Oplev positions AFTER we have good ALSY beam Spot:
H1:SUS-ETMY_L3_OPLEV_PIT_OUTPUT = -16
H1:SUS-ETMY_L3_OPLEV_YAW_OUTPUT = -13

ITMY Oplev positions AFTER we have good ALSY beam Spot:
H1:SUS-ITMY_L3_OPLEV_PIT_OUTPUT = -13
H1:SUS-ITMY_L3_OPLEV_YAW_OUTPUT = 9

Comm Beat note: 1.5
Diff beatnote : -14

The Beam splitter was touched up as well.
BeamSplitter Oplevs as they currently Stand:
H1:SUS-BS_M3_OPLEV_PIT_OUTPUT = 7
H1:SUS-BS_M3_OPLEV_YAW_OUTPUT = -9

Dark offsets by hand , for AS_C.

PR2 and IM4 were just touched up and then did Dark Offsets by hand for POP 45.
PR2  Witness sensors positions:
H1:SUS-PR2_M3_WIT_LMON = -29
H1:SUS-PR2_M3_WIT_PMON = 614

IM4 Witness Sensors postions:
H1:SUS-IM4_M1_DAMP_L_INMON = -41
H1:SUS-IM4_M1_DAMP_P_INMON =-2803

X ARM Sensor Correction has been turned off the Entire time due to Jim's BRS being rung up by him working on it.

Input Align Offloaded Successfully!!!
PRC_ALIGN OFFLOADED!!!
MICH_BRIGHT OFFLOADED!!!
INITIAL_ALIGNMENT COMPLETE!!!

Naoki, Nutsinee, Daniel

While scanning PMC, we noticed a large higher order mode. We went to SQZT0 and found that it was due to yaw misalignment. After we aligned PMC, we measured PMC input and transmission power. The PMC input power is 820mW and the transmission power is 680mW so the PMC transmissivity is 83%, which is much higher than before. We calibrated the SQZ-LASER_IR_DC_POWERMON and the SQZ-PMC_TRANS_DC_POWERMON to 820mW and 680mW, respectively. After we locked SHG, the SHG GR power reached 100mW.

We also put some beam dumps in SQZT0.

From Minhyo & Preet 
After changing of OMC control, it might be good to check the signals.
(Refer to Jennie's alog: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=76126, https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=76103)

Figures are comparison between Mar. 5 and one of the date in O4a (Jan. 2. 2024): 
1) SUS-OM3_LOCK comparison with both PIT and YAW
2) SUS-OMC_ASC comparison with both PIT and YAW
3) OMC-ASC_QPD A comparison with both PIT and YAW
4) OMC-ASC_QPD B comparison with both PIT and YAW

Seems that the signal went up in high frequency (4 ~ 10 Hz), which is pretty similar with QPD signals.

Today's activities:
- EX gate valve (GV20) was OPENED. The pressure there is already 7.8E-9

- At the Corner, after the large IP controllers were replaced yesterday, the pressure was dropping continuously. As the IP data is not in the CDS (yet, because of swapping the controllers), see the attached pictures of the pressures directly at the IP orifices, at different times
- The main GVs (GV5; GV7) have been OPENED. The pressure is dropping nicely, it is currently at 7.5E-8 at the center
- All the turbo pumps (HAM6, OMC, Y-manifold, X-manifold) were valved out before/during GV openings

- HAM8 RGA will be ready for taking scans tomorrow
- HAM7 turbo was valved out, and it was also valved together with the short FCT section between BSC3 and HAM7 (FCV1 OPENED). The pressure rose a bit, but it is still at ~3.2E-7
- The pumping of HAM7 RGA was stopped, the cart was taken away
- FCT further schedule: after HAM8 RGA scan was done - and it is satisfactory - the whole relay tube - HAM7 - HAM8 line will be valved together and into the main volume (opening RV1, FCV2, FCV3, FCV4, FCV7, FCV8), and HAM8 turbo will be valved out. This will happen tomorrow (3-6)

In the rest of the day, the vacuum team will switch off turbos and clean up in the LVEA.
And, there will be some pumpdown statistics and summary posted to aLog later on.