Sheila, Camilla, Andrei

Time-traces from aLOG's 77133, 77268 and 77710 were used to deduce the systems parameters. Three types of measurements were acquired: without the squeezer beam, without the Filter Cavity, and with both. The data was normalized, therefore, we analyzed the value in decibels of quantum noise reduction compared to no squeezing rather than the PSD of the signal.

Budget module QuantumRelGamma was used for fiting.

To fit the measurements without the Filter Cavity, we assumed the Filter Cavity Mismatch parameter to be 1 (equivalent to ifo.Squeezer.Type = 'Freq Independent').

After inferring the quantum noise by adjusting the arm power and optical gain parameters, we then adjusted all other parameters, mainly focusing on phase, Filter Cavity detuning, injected squeezing, SEC detuning, and IFO-OMC mismatch.

The code was primarily based on Dhruva's interactive-sqz-main.

Mon May 20 10:08:12 2024 INFO: Fill completed in 8min 8secs

Jordan confirmed a good fill curbside.

I've moved the offsets on the FS green QPD A to improve the spot centering on FC2, following 69276 and 73777.  The centering is better, as shown by the attached screenshot. This hasn't had much of an impact on the green build up in the filter cavity, and seems to have redcued the IR build up.   This didn't have much of an impact on the couple of months of downward trend on the FC build ups.

We started comissioning at 16:00 UTC and will continue till 19:00 UTC, starting with some SQZ optimization.

TITLE: 05/20 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:

• We've been locked for 7:45, in observing since 14:09
• Low wind
• Comissioning time is planned for 16:00 to 19:00 UTC? 09:00 to 12:00 PST

I had to pop on to help the ifo because we had been taken out of Observing due to the SQZ OPO lockloss limit counter having reached its max. I followed 73053, skipping over the adjustment of the OPO temp, and the filter cavity eventually locked and we were able to get back into Observing.

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

Unknown lockloss @ 5:50 UTC
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1400219473

Relocking: happened automagically, and H1 was back to OBSERVING at 6:49 UTC
Survived a few more quakes tonight including a 5.1M . 

I have not seen any more deviations in the ISI HAM 3 BLRMS since the I power cycled them so hopefully they last until tomorrow morning.

H1 is now currently locked for 1 hour and a half.
 

LOG:
Tony went to the CER to reboot ISI interface Chassis around 3 UTC for 5 minutes.

TITLE: 05/20 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 19mph Gusts, 14mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

Unkown Lockloss
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1400201888
I did go back to check if this lockloss was caused by the smaller ISI glitches that jim and I saw that did not trip the watchdog. This is not the case for this Lockloss It is still of unknown origin.

Relocking:
I had to slightly touch up the Beam Splitter and PRM  both in pitch to get DRMI locked but other than that it went well.
We are still saturating SUS in Power 10 & 25 Watts and in Move Spots.

HAM3 ISI tripped watchdog Lockloss
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1400207843
Contacted Jim, took IMC_LOCK to Offline and went to the CER to power cycle the HAM3 ISI Chassis found in rack SEI-C2  - rack slots 30 & 31 . Once the ISI interface chassies came back on, Jim gave me a green light to start locking again.
He noted that there are some ndscopes I can use to watch for more glitches, which are identified by spikes above 20:
ndscope H1:ISI-HAM3_CPSINF_H{1,2,3}_BLRMS_65_100 H1:ISI-HAM3_CPSINF_V{1,2,3}_BLRMS_65_100  H1:ISI-HAM3_CPSINF_H{1,2,3}_BLRMS_130_200


Relocking 2:
I clicked on Nominal_Low_Noise and It went to it with out much fuss at all.

Observing reached at 4:13 UTC
Dropped to commissioning for some SQZ Scans to increase the range.

 PI 31 has been ringing up a fair amount this lock but every time it's been solved by the PI system.

Currentlt H1 has been locked and in Observing for over 1 hour.

TITLE: 05/19 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 8mph Gusts, 4mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

IFO is now at Laser Noise Suppression and going up! Ryan was able to get H1 the IFO past PRMI.
If we lose lock and get back into PRMI, 2 OLG measurements to take :
/opt/rtcds/userapps/release/lsc/h1/templates/PRCL/PRCL/PRCL_OLG_PRMI.xml
&
/opt/rtcds/userapps/release/lsc/h1/templates/MICH/MICH/MICH_OLG_PRMI.xml

and for DRMI :
/opt/rtcds/userapps/release/lsc/h1/templates/PRCL/PRCL/PRCL_OLG_DRMI.xml
&
/opt/rtcds/userapps/release/lsc/h1/templates/MICH/MICH/MICH_OLG_DRMI.xml

Hopefully we wont have to relock at all.

Ryans Changed made to the Gains in lcsparams.py  and Timers in ISC_DRMI.py have Not been Reverted.
 

SDF diff that had to be accepted to get into OBSERVING:
H1:SYS-MOTION_C_PICO_A_CURRENT_ENABLE

TITLE: 05/19 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Tony
SHIFT SUMMARY: More progress than yesterday in terms of the PRMI oscillation as I seem to have solved it for now by adjusting loop gains and ramps and can hold it locked, then I was back to DRMI not being able to lock but after Sheila restored PR3 to a previous spot we were able to lock DRMI no problem. Currently a few minutes away from NLN

15:00 UTC Initial Alignment as there weren't really any flashes on PRMI

After some more fiddling with gains/ramp times and talking to Sheila I was able to stop the PRMI 20ish Hz buzz by reducing PRMI-MICH to 2.2 from 2.8 and increasing PRMI_PRCL to 8 from 6 and set the ramp time sof both to 5 alog77928

20:25 UTC - No matter how much adjusting I did with the sliders (BS, PRM, SRM) I couldn't get AS AIR looking good enough so I thought there must be an alignment issue somewhere after a few mores tries I dropped to do another Initial Alignment, after this I still had DRMI issues.

I further decreased the gain of PRMI-MICH to 2.0 after Sheila looked at my OLG measurement, PRMI locked pretty easily after this. We're not sure why my PRCL OLG measurement looked the way it did alog77929

22:35 UTC Sheila adjusted PR3 to where it used to be, after which I did another Initial Alignment so we could try locking PRMI. I may need to revert my PRMI loop changes? I have not reverted them as of now

After finishing IA we locked DRMI immediately

There were a lot of IFO_OUT saturations during POWER_25W and MOVE_STOPS

After Ryan was able to lock PRMI by adjusting both the MICH and PRCL gains (77926) , he mentioned to me that the build ups didn't look good.  Indeed, POP18 was around 26 counts after PRMI ASC ran, before our PR3 moves this week it would be around 50 counts in PRMI.  I looked back and it hasn't been 50 since I put PR3 back on Friday.  I was able to walk PR2, PRM and BS to improve the build up a little, but decided to move PR3.  We did this at LOCKING_ARM_GREEN, and saw that putting PR3 back according to the slider values (rather than top mass osems), did improve the COMM beatnote from around -10 to around 0dBm. 

Ryan is going to run an initial alignment skipping the green arms, and try to relock PRMI.  Then we will see if this PR3 move solves the low POP18 power, if the PRMI gain changes can be reverted. 

Also note that Ryan posted a PRCL UGF measurement that seems very strange. 

I spent a bit trying to align everything by hand with ISC_LOCK paused in DRMI, misaligning PRM and SRM to adjust the BS then aligning PRM to adjust it then SRM. Still the same behaviour on PRMI as yesterday even with turning down the MICH and PRCL gains, and despite good flashes on DRMI it wasn't able to lock after my adjustments, I had to move SRM a lot. The wind is also picking up which is not helping ALS.

TITLE: 05/18 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Lost lock at the end of the shift, DRMI alignment issues and PRMI was plagued by a ~20Hz buzz that kept killing it after 2 seconds, the mode cleaner was slow to lock in each attempt today. After the 3rd IA DRMI was finally in the mood to lock and I didn't have to go through PRMI and I returned to Observing at 21:15UTC. I was not able to take the calibration measurement this afternoon as planned.

15:25 UTC HAM3 ISI CPS trip while doing green arms in IA. I could not finish SRC align, as SRM was continually saturating. There was also a couple of IY saturations, and there was an earthquake shaking everything at the time.

16:02 UTC HAM3 ISI CPS trip during FIND_IR? I couldn't get PRMI to stay locked for more than 2 seconds.

17:00 UTC I restored the alignments to 05/18/24 03:00 UTC which was right before we locked last night for the 11 hour lock. After locking ALS I could immediately see the beatnotes were better, but DRMI only had small flashes. A few rounds of CHECK_MICH and still bad flashes, 13:31 I started a 2nd IA skipping GREEN_ARMs, there were no saturations during this IA and I was able to finish SRC_ALIGN.

I'm still not able to get PRMI to stay locked for more than 2 seconds, theres a 20ish Hz oscillation that kills it when the MICH1 filter is ramped on? I tried lowering the PRMI-MICH gain from 3.2 to 2.8 in lscparams as Sheila suggested the other day. It lasted longer but was still ultimately killed by the 20Hz buzzing, I lowered it more to 2.6 and it lasted even longer but was killed when PRCL1 turned on? AS AIR was still clearly misaligned so I went through CHECK_MICH which made things worse?  I now had worse PRMI flashes and still a clearly misaligned AS AIR. During this I was also trying to help adjust PRM/BS while in PRMI to fix AS AIR.

19:37UTC After some more seemingly fruitless adjusting of PRM and BS I started a 3rd IA... it looks centered on AS-AS_C during SRC and PRC alignment?

Same behavior as before, bad DRMI then PRMI gets killed after a few seconds from the 20Hz, its also always right after the BS_M1_L filter is turned on. Lockloss after a few rounds of PRMI.

For the next attempt I tried turning down the PRMI-PRCL gain from 6 to 4 but then it was able to lock DRMI all of a sudden and we didn't even go through PRMI... so I'll revert these changes. I have no idea whats different this attempt from the last or why it decided now it wants to work but I'll take it. The alignment was just finally good enough, even though it wasn't on the first attempt after the IA finished?

21:15 UTC back to Observing

23:21 UTC lockloss from a HAM3 ISI trip, same as before, CPS sensor tagging SEI

fmscan is a program which, for a given filter module and time period, reports when filters were switched on/off.

It is designed to be ran from MEDM as an MEDM_EXEC_LIST program. To set this up, add the following to your MEDM_EXEC_LIST environmental variable:

    :fmscan;/ligo/gitcommon/fmscan/fmscan.py &P &

The first attachment shows the fmscan option being selected in the Execute pull down menu, opened from MEDM with the right-mouse-button. You can select any EPICS PV channel associated with the filter module (e.g. GAIN, OFFSET, SWI, etc)

Second attachment shows the time-selector GUI with the default time range of the past 24 hours. Any gpstime format can be used (e.g. GPS seconds, "1 month ago", etc.)

The third attachment shows the filters activity for H1:LSC-SRCL1 for the past day. Filter changes are shown in bold. First and last rows show the start/stop times respectively.

At LLO, Aidan and Karla found the ISCTEX/Y tables (ALS/HWS) tables were further from the BSC viewport than designed which would change Aidan's T1000717  mode-matching calculations. Ours are also different, EY more than EX.