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

21:04 UTC back to NLN, I'm going to see how squeezing is doing then go into observing or optimize squeezing then go into observing.

After finishing my 3rd Initial Alignment I went through another round of too small DRMI flashes and the same PRMI locking and the 20Hz buzz killing it over and over again till a lockloss, we lost it at ALIGN_RECYCLING_MIRRORS after this for some reason. For the next attempt I turned down to gains for PRMI, PRCL1 and MICH1 from 6 -> 4 and 2.8 -> 2.6 respectively in lscparams and reloading ISC_DRMI but DRMI was suddenly able to lock after a few seconds and we didn't even go through PRMI. I reverted my gain changes, I have no idea if they would have helped or not, turning the MICH1 gain down from 3.2 to 2.8 did help us to survive longer in PRMI but it still was not enough.

Sat May 18 10:12:26 2024 INFO: Fill completed in 12min 22secs

Still having alignment problems, I wasn't able to finish SRC in IA. PRMI won't stay locked for more than 2 seconds despite ok flashes. I'm thinking of trying to restore the alignment to right before we locked last night or doing another initial alignment.

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

• Lost lock right at 11 hours, at 14:40UTC
• Low wind
• EQ mode activated at 14:50 UTC

TITLE: 05/18 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
Winds and some light earthquakes made for difficult locking but H1 got there.
When we first locked the range was 142-ish Mpc, after about 2 hours of thermalizing and some fiddling with the SQZ_MAN  SCAN ALIGNMENT FDS & SQZ_SCANANG I was able to increase the range to the mid 150's. 

H1 has been locked for 4 and a half hours. and currently Observing.

LOG:
no log

TITLE: 05/18 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 142Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 32mph Gusts, 24mph 5min avg
    Primary useism: 0.11 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY:

After interviening to get better flashes on ALS Y arm
I tried to lock H1 and it failed at getting PRMI locked.
I started an Initial_Alinment.
Initial alignment took a long time to complete likely due to the wind.

Once the locking started H1 made it to Check_ALS_SHUTTERS and a 5.0 Mag Earthquake from the South Sandwhich Island hit and unlocked the IFO.
https://earthquake.usgs.gov/earthquakes/eventpage/us6000mzcb/
This earthquake was not announced on verbals.
Nor was this one https://earthquake.usgs.gov/earthquakes/eventpage/us6000mzcu/executive

After trying to relock and getting stuck in a PRMI loop again I requested another Initial_Alignment while waiting for the R wave to pass.
Relocking took a long time but we got back to OBSERVING at 3:38 UTC

The range isn't great so I started poking around the in the new Low Range Checks.
I have attached plots of diaggui & ndscope described on the ops wiki low range checks AND a picture of the bottom of the SQZr nuc33 .
Since I'm not really sure how these plots would normally look. I have no idea if I should adjust the squeeze angle or not. Everything I have read kinda suggests that perhaps the squeeze angle is fine maybe?

anthony.sanchez@cdsws29: caget H1:SQZ-CLF_REFL_RF6_PHASE_PHASEDEG
H1:SQZ-CLF_REFL_RF6_PHASE_PHASEDEG 212.115

All of these were taken before running the SQZ scan.

The IFO has now been locked for ~ 2 hours. I'm thinking that the perhaps I should try to run the SCAN_ALIGNMENT_FDS to see if better range can be reached.

GRB-SHORT  E484687 Standing down....
 

TITLE: 05/17 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: 25mph Gusts, 15mph 5min avg
    Primary useism: 0.09 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY:
When I inherited the IFO we were locked. 
I needed to accept the SQZ SDF Diffs to get into Observing.

I first ran a SQZ scan before accepfting those SDF Diffs. But I think I ran the wrong one. I likely should have ran SCAN_ALIGNMENT_FDS  instead of SCAN_SQZANG.
Took H1 to Observing at 23:55 UTC
LOCKLOSS 00:16 UTC Screen shot of lockloss tools attached.


 

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.

TITLE: 05/17 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Tony
SHIFT SUMMARY: We're almost relocked following troubles relocking from the initial lockloss in the morning. Back to NLN at 23:31

17:50  UTC - After getting no flashes on PRMI or DRMI, even after two runs of CHECK_MICH I started an Initial Alignment at 17:49. During this Shiela decided to revert the PR2 changes from yesterday through a manual IA. The winds stayed around 20/30 mph throughout the afternoon.

18:58 UTC - Back to locking, still windy out so there was a bunch of ALS locklosses

XARM is not able to stay locked, We were only able to keep it locked by during off the WFS but even then it was still unstable. Yarm was stable throughout the whole ordeal, so the wind might not have been that big of a factor?

I was able to keep Xarm locked by holding in NO_WFS for a bit then turning them on and slowly stepping through ALS to IR. I was then not able to get any flashes on DRMI and they weren't great on PRMI, we lost it while I was adjusting PRM

Sheila went out to the floor to adjust the COMM beatenote on ISCT1 to see if that would help us to be more stable (~ -10.5 to ~ -1.6). The wind was only getting worse as the afternoon went on.

22:30 UTC - I started another IA after we still couldnt not get any flashes on PRMI or DRMI after Sheilas table adjustment.

After this last alignment I've been able to relock without any difficulty

LOG:                                                                                                                                                                                                                                                                                                

Genevieve, Dave:

The PEM RF Scanner produces static png images of frequency-time plots every 10 minutes. These can be viewed at https://badger.ligo-wa.caltech.edu/rfscan/pngs/

I have created a daily cronjob, which collates the previous day's worth of 144 png files and produces two MP4 movie files. One has a frame rate of 8 frames per seconds with a run time of 18 seconds for a quick view. The second has a frame rate of 2fps and a run time of 72 seconds (attachment shows the web listing of these files).

For ease of access I have added a "RF Scanner" link to the CDS Web Page

I don't have time to implement this this afternoon, but it would be better for the fine_tune_Better state to look at the maximum IR, rather than the average. 

In times of high ground motion, we want to move through the ALS states quickly because we will be more stable once we are locked on IR.  The ALS is also not holding the arms stably on resonance, so the transmitted IR fluctuates a lot.  In the screenshot attached this is a case where the IR resonance has been found well, but because there is a lot of fluctation it is failing the test.  Replacing the cdu.avg on line 217 of ISC_GEN_STATES with a max would solve this, but since there isn't a function like that we need to write something.

MInhyo, Sheila, Ryan Crouch

After lossing lock this morning we decided to revert the move of PR3 (to move the spot on PR2) that we did yesterday.  We believe that the issues with our range may be due to the squeezing problem, which may have started before our move of PR3.  Still, we think it's best to try to revert before the weekend on the chance that that restores the range of H1.  High winds have made locking difficult since our lockloss this morning.

We realized yesterday that the PR2 spot move guardian state hasn't been updated since the IM sliders were calibrated in 77211, I've tried to scale the scale factors correctly for those changes.  We commented out all of the decorators from the PR2_SPOT_move guardian state so that we could use it without the full IFO locked, and we have now put them back in and reloaded the guardian.  We moved PR3 using this script while we had the X arm locked in IR, this lock uses the LSC POP diode for an error signal so we lost lock when we fell off that diode.  We then just used osems to restore optics to before yesterday's move, and set the pico back to it's starting point.  After setting the pico back in this way the Y arm green light was on the X arm diodes.   Once we understood that we moved the pico so that Y was on the Y camera and diode and X was on X, then optimized the beatnote.  We ran an initial alignment without much issue once the pico was set so that we had an error signal for the X arm IR. 

This resulted in a COMM beatnote of -10dBm, which had been closer to 0 before our moves.  We double checked that the test masses, BS, and PR3 were in the same location as before our move, and that we couldn't adjust the pico to increase the beatnote anymore.  While this should be OK for locking, we've been struggling with the high winds and in the past we've seen that when the ground motion is high we have better locking if the beatnotes are good.  So Minhyo, KarMeng and I went to the table to adjust the comm beatnote, we adjusted both pitch and yaw on the beatnote  beamsplitter and the steering beamsplitter directly in front of it. This brought the beatnote to -2dBm.  We are still having difficulty locking ALS, presumably because of the wind.

The Y arm seems able to hold lock for long periods of time, while the X arm green lock doesn't last more than a few minutes.  The VCO control signal has plenty of range, and the alingment seems stable, so I'm not sure what the problem is with the X arm.

Minhyo, Sheila

Checked for the reason of large BNS range drop (Sheila's alog: 77870), with comparing DARM plots (screenshot).
From the DARM comparison, it seems that the low frequency noise went worse right before PR3 alignment change, which correlated to the range drop before yesterday's commissioning (156 Mpc -> 142 Mpc). On the other hand, high frequency noise went worse after relocking using PR2 changed alignment. Seems that at both frequency range got worse with unknown reason (maybe SQZ).

While Sheila tried to fix SQZ, she suggested adjusting A2L gain value of ITM and ETM. After I finished with P2L decoupling of ITM, we had lockloss.