TITLE: 07/05 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: An earthquake lockloss then a PI lockloss. Currently at MAX_POWER

Lock1:

• 23:25 UTC reacquired NLN, back in Observing at 23:28 after accepting some SDF diffs for ALSX
• 01:19, 01:37, and 02:12 UTC Dropped out of observing for a few seconds due to 2 SDF diffs on syscssqz (from DIAG_SDF log), I didn't catch what the channels were.
  • It seems like its a problem with the SQZ_FIBR_TRANS (Tagging SQZ)
  • It started happening again at 04:14 UTC and I was able to catch the channels, a trend of the {FAST,COM}GAINS. I unmonitored them for now
• 02:13 UTC lockloss from another earthquake, a 2.6 from Alaska?

Lock2:

• XARM is having fiber polarization issues now, H1:ALS-X_FIBR_LOCK_FIBER_POLARIZATIONPERCENT can't get below 14 (ALS_OVERVIEW -> POLARIZATION CORRECTION BOX), Sheila suggested H1:ALS-X_FIBR_LOCK_LOGIC_FORCE which did the trick for now until the root issue can be solved
• Lost it at ALS then I didn't have the issue the 2nd try
• 05:32 UTC superevents20240405at, didn;t get a verbal callout for this
• 06:37 UTC lockloss from a PI ringup

Lock3:

• ALSX fiber error is back, toggling force on the PLL doesn't do anything now. I toggled force on the PDH as well which locked it
• GRD couldnt get the POL below 22 after a bit of trying, I took over (paused ALS_XARM) and got it to 15 somehow, I unpaused it and it was finally able to get out of CHANGE_POL / FAULT
• 07:23 DRMI lockloss at CARM_150_PICO

To recap for SQZ, I have unmonitored 3 SQZ channels on syscssqz (H1:SQZ-FIBR_SERVO_COMGAIN, H1:SQZ-FIBR_SERVO_FASTGAIN, H1:SQZ-FIBR_LOCK_TEMPERATURECONTROLS_ON) that keep dropping us out of observing for now until their root issue can be fixed (Fiber trans PD error, too much power on FIBR_TRANS?). I noticed that each time the GAINS change it also drops our cleaned range

PI ring up lockloss? PI28 and 29 were unable to be damped down by the GRD and we eventually lost lock.

https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1404196646

Closes FAMIS25997, last checked in alog78550

ITMX_ST2_CPSINF_H1 has gotten noisier at high frequency

Everything else looks the same as previously.

Lost lock from an earthquake

It seems earthquakes causing similar magnitudes of movement on-site may or may not cause lockloss. Why is this happening? Should expect to always or never cause lockloss for similar events. One suspicion is that common or differential motion might lend itself better to keeping or breaking lock.

- Lockloss is defined as H1:DRD-ISC_LOCK_STATE_N going to 0 (or near 0).
- I correlated H1:DRD-ISC_LOCK_STATE_N with H1:ISI-GND_STS_CS_Z_EQ_PEAK_OUTMON peaks between 500 and 2500 μm/s.
- I manually scrolled through the data from present to 2 May 2024 to find events.
    - Manual, because 1) wanted to start with a small sample size and quickly see if there was a pattern, and 2) because I need to find events that caused loss, then go and find similarly sized events we kept lock.
- Channels I looked at include:
    - IMC-REFL_SERVO_SPLITMON
    - GRD-ISC_LOCK_STATE_N
    - ISI-GND_STS_CS_Z_EQ_PEAK_OUTMON ("CS_PEAK")
    - SEI-CARM_GNDBLRMS_30M_100M
    - SEI-DARM_GNDBLRMS_30M_100M
    - SEI-XARM_GNDBLRMS_30M_100M
    - SEI-YARM_GNDBLRMS_30M_100M
    - SEI-CARM_GNDBLRMS_100M_300M
    - SEI-DARM_GNDBLRMS_100M_300M
    - SEI-XARM_GNDBLRMS_100M_300M
    - SEI-YARM_GNDBLRMS_100M_300M
    - ISI-GND_STS_ITMY_X_BLRMS_30M_100M
    - ISI-GND_STS_ITMY_Y_BLRMS_30M_100M
    - ISI-GND_STS_ITMY_Z_BLRMS_30M_100M
    - ISI-GND_STS_ITMY_X_BLRMS_100M_300M
    - ISI-GND_STS_ITMY_Y_BLRMS_100M_300M
    - ISI-GND_STS_ITMY_Z_BLRMS_100M_300M
    - SUS-SRM_M3_COILOUTF_LL_INMON
    - SUS-SRM_M3_COILOUTF_LR_INMON
    - SUS-SRM_M3_COILOUTF_UL_INMON
    - SUS-SRM_M3_COILOUTF_UR_INMON
    - SUS-PRM_M3_COILOUTF_LL_INMON
    - SUS-PRM_M3_COILOUTF_LR_INMON
    - SUS-PRM_M3_COILOUTF_UL_INMON
    - SUS-PRM_M3_COILOUTF_UR_INMON

        - ndscope template saved as neil_eq_temp2.yaml

- 26 events; 14 lockloss, 12 locked (3 or 4 lockloss event may have non-seismic causes)

- After, usiing CS_PEAK to find the events, I, so far, used the ISI channels to analyse the events.
    - The SEI channels were created last week (only 2 events captured in these channels, so far).

- Conclusions:
    - There are 6, CS_PEAK events above 1,000 μm/s in which we *lost* lock;
        - In SEI 30M-100M
            - 4 have z-axis dominant motion with no motion or strong z-motion or no motion in SEI 100M-300M
            - 2 have y-axis dominated motion with a lot of activity in SEI 100M-300M and y-motion dominating some of the time.
    - There are 6, CS_PEAK events above 1,000 μm/s in which we *kept* lock;
        - In SEI 30M-100M
            - 5 have z-axis dominant motion with only general noise in SEI 100M-300M
            - 1 has z-axis dominant noise near the peak in CS_PEAK and strong y-axis domaniated motion starting 4 min prior to the CS_PEAK peak; it too only has general noise in SEI 100M-300M. This x- or y-motion which starts about 4 min before the peak in CS_PEAK has been observed in 5 events -- Love waves precede Rayleigh waves, could be Love waves?
    - All events below 1000 μm/s which lose lock seem to have a dominant y-motion in either/both SEI 30M-100M / 100M-300M. However, the sample size is not large enough to convince me that shear motion is what is causing lockloss. But it is large enough to convince me to find more events and verify. (Some plots attached.)

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

Today H1 was down for ALS maintenance and replacement of ALS X PD as described in Daniel's alog (78864) . 
once they returned I started an Initial_Alignment and then started locking.
Observing was reached at 23:28 UTC.
There have been a number of earthquakes right off the coast of Victoria Island B.C. today.

LOG:                                                                                                                                                                                                                                                                                                 

TITLE: 07/04 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 10mph Gusts, 4mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.08 μm/s 
QUICK SUMMARY:

• Relocking at POWER_25W
• We just finished a IA before this lock attempt and everything seems to be going well
• 2nd order violins look a little high

Keita Daniel

We found that the transimpedance gain of the ALS-X_FIBR_A_DC PD was wrong (changed it from 20k to 2k). In turn, this meant that 20mW of light was on this PD.

After looking at the beatnote amplitude directly at the PD and found it to be way too small, we decided to swap the PD with a spare (new PD S/N S1200248, old PD S/N S1200251). However, this did not improve the beatnote amplitude. (The removed PD was put back into the spares cabinet.)

We then looked for clipping and found that the beam on the first beam sampler after the fiber port was close to the side. We moved the sampler so the beam is closer to the center of the optics. We also found the beam on the polarizing cube in the fiber path to be low. We moved the cube downwards to center the beam. After aligning the beam back to the broadband PD, the beatnote amplitude improved drastically. This alignment seems very sensitive.

We had to turn the power from the laser in the beat note path down from 20mW to about 6mW on the broadband PD.

This required a recalibration of the ALS-X_LASER_IR_PD photodiode. The laser output power in IR is about 60mW.

The beatnote strength as read by the medm screens is now 4-7dBm. Still seems to vary.

6 channels were accepted in the SDF diffs after the ALS adjustments done today.

TITLE: 07/04 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Earthquake
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 6mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY:
Kieta and Daniel have come to site and gone to EX to adjust the H1:ALS-X_FIBR_A_DEMOD_RFMON. which should allow a better bat note. Work Permit : 11962

I was looking at verbals an noticed that Intention bit was flipped back and forth from 12:02 UTC until 12:57 UTC  a large number of times.
I checked the SQZ manager during that time and I didnt see much motion, so i'm still not sure what caused this..

Kieta & Daniel have come back from End X for a snack, and let me kno wthat the Photo Diode is likely busted and they are gonna go back out there and swap it.
I have accepted some ALS SDF Diffs.

Hopefully they can swap it out today and we can get locked sometime today.
 

The CDS HW STAT ioc was restarted this morning, the new code checks the status of the LIGO Timing Card in the IO Chassis.

Thu Jul 04 10:17:39 2024 INFO: Fill completed in 17min 35secs

TITLE: 07/04 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Aligning
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 6mph Gusts, 4mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY:
We had been locked for 7 + hours until an Earthquake unlocked us. 
When I arrived the IFO was Unlocked and ALS_XARM was stuck on CHECK_CRYSTAL_FREQ.
I'm still trying to figure out how to make the H1:ALS-X_FIBR_LOCK_BEAT_FREQUENCY better.

TITLE: 07/04 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:

Lock1: ISS 2nd loop issues, possible EndX issues, and the classic input align issues

• 22:58 UTC Started IA where we couldn't get XARM IR during INPUT_ALIGN, we reverted the moves from earlier alog78831 then it locked. I also had to intervene to help PRC by moving PRM in pitch quite a bit.
• 01:38 UTC Lockloss at LASER_NOISE_SUPPRESION
• ALS_XARM looks very fuzzy during GREEN_ARMS now due to the PDH constantly locking and unlocking
• 02:01 UTC After a bit of trying I went into a MANUAL_IA to try some things. I tried adjusting IM3 & IM4 to recenter it on POP_A QPD (LSC->Photo_detector ->POP_A) which helped, it was then less fuzzy and the XARM PDH was able to stay locked. I then looked at AS_AIR and adjusted PR2 & PR3 (I reverted the PR3 moves since they didn't seem to help) in PIT & YAW a small amount (less than a microradian) based on the camera, when I went smaller in YAW the PDH unlocking started again and the other direction made AS AIR look a bit better.
  • I still couldn't get XARM to converge its WFS so I skipped ahead to see if the INPUT_ALIGN was off and it was and it couldn't acquire XARM IR, I had to further touch IM4 then it went right along. I went through the rest of IA with no issues
• 02:56 UTC Back into locking and XARM was still fuzzy but not nearly as much and PDH seemed to be holding, hopefully its good enough to get past ALS. DRMI locked in literally 3 seconds, fastest I've ever seen it.
• 03:53 Lockloss at LASER_NOISE_SUPPRESION again
  • Now the PLL and PDH both won't lock for XARM, I again had to move IM4 (in YAW by like 50 microradians) to get them to stay locked and reduce the fuzz.
• 04:15 UTC Sheila hopped on to help, she thinks there might be an issue out at the end station (due to the XARM fuzz) and it seems we have fallen off of the ISS 2ndL pd alog78856
•  04:30 UTC We dropped to do another IA, skipping GREEN_ARMS and reverted the IMs (3,4) and PRs (2,3,M) to where they were this morning before the adjustments. I moved PRM by about 300 microrads in YAW. We got stuck in SRC align and Sheila lowered the trigger threshold to get us by.
  • XARM still looks bad but hopefully we can get past LASER_NOISE now as we have light on the ISS 2L pd now.
  • 05:56 Observing, 2 SDF diffs, SQZ and EXISC
  • 06:14 - 06:15 and 06:41 - 06:42 UTC dropped out due to a SQZ SDF diff for FIBR_TEMPCONTROLS

The SQZ-FIBR_TRANS_DC is just barely over the high power limit (Tagging SQZ)

I unmonitored the CSSQZ channel H1:SQZ-FIBR_LOCK_TEMPERATURECONTROLS_ON as it would periodically turn off and on at a high frequency without seemingly doing anything to the BEAT_FREQ, so this won't keep dropping us out of observing tonight

Ryan C, Sheila D

Summary:  The input beam moved after the PSL incursion, alinging the IMC doesn't completely restore the input beam alignment to the IFO.  Using IM4 QPD as a reference to move IM3 resulted in no beam on the ISS second loop, so we have reverted that for now.

Before Tuesday's PSL incursion, when the IMC was locked at 2W IM4 trans QPD was fairly well centered, we had 1.5 or 1.6 counts on the ISS second loop inner and outer loop sums, 310 counts on MC2 trans QPD, and 95 counts on the ISS second loop QPD.  After Jenne relocked the IMC yesterday, we had 2W on IM4 trans, but the QPD was off center with ~0.3 pit and 1 in yaw, the second loop inner and outer sums were 1.46 and 1.6, 305 counts on MC2 trans, and 94 on ISS second loop QPD. 

This morning Camilla and company moved IM3 to re-center the beam on IM4 trans, 78831,  After our struggles with input alignment after the vent earlier this year, we learned that LLO uses IM4 QPD as a reference to adjust IM3 trans when needed, so we had centered IM4 hoping to use it as a reference in this way.  However, doing this made the beam completely fall off the ISS second loop, with no power on it's QPD or the two PD sum channels.  This may mean that we were close to clipping in the second loop before, so we should come back to this another day to think about how we can restore the input alignment to what it previously was, and make sure we don't clip on the ISS. 

For now I reverted IM3 sliders to this morning, and Ryan is working his way through the initial alignment. 

Along the way he also showed me that the X arm green transmission is extremely noisy, with high frequency fuzz.  This might mean that we still have some electronics problems at EX after today's work.  Sicne Ryan has been able to get past ALS locking tonight, we won't try to address this issue tonight.

Built a second SHG with the PPKTP crystal from MIT, did a measurement on the conversion efficiency and fit for the single pass nonlinear conversion efficiency E_nl = 0.0055W^-1. The single pass measurement of the PPKTP crystal give a nonlinearity d_eff = 5.41 pm/V. Generally d_eff of PPKTP is quoted around 9.3pm/V (Table 5.1 of Georgia's thesis)

Measurement of the phase matching curve with input power of 60 mW shows a dip around 35 celcius. The temperature controller reads in kOhm and is converted into celcius via the Steinhart-Hart equation:

A1 = 0.003354016
B1 = 0.0002569850
C1 = 2.620131e-6
D1 = 6.383091e-8

R25 = 10000
R = R_meas / R25
T = ( 1 / (A1 + (B1 * np.log(R)) + (C1 * np.log(R)**2) + (D1 * np.log(R)**3) ) ) - 273.15

Phase matching curve is plotted by using Equation 3.14, 3.20 and Table 3.2 from Sheila's thesis. I have fitted the sinc curve with T₀ = 34.9 and i_max = 11.79 , 18.00 and 32.00.