TITLE: 07/18 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Preventative Maintenance
SHIFT SUMMARY: Large earthquake caused a lockloss about halfway through the shift, then spent the remaining time relocking and damping violins until scheduled injections began.

Lock #1:

• Incoming 5.7 Mexico earthquake: EQ mode activated @ 10:31
• Lockloss @ 10:33 from quake: alog

Lock #2:

• Fully automatic lock once ground motion calmed down
• Reached OMC_WHITENING at 11:52 and never reached NLN due to high violins
  • Rahul assisted with damping remotely
• Magnetic injections started @ 14:20 (usual time; still in OMC_WHITENING so this didn't start automatically)
• Intentionally broke lock by flipping H1:IMC-REFL_SERVO_IN2EN @ 15:06

Handing off to Tony for the day.

LOG:

While we were waiting at OMC_Whitening, I took this opportunity to load the new settings for ETMY mode 20 in lscparams and then load the violin damping Guardian. I have also accepted it in the SDF. The latest settings have been tried for few locks and it works fine.

FM1 FM4 FM10 Gain -1.0

Current status of the IFO - we are waiting for the violins to come done (while gradually and safely ramping up the gains for the rung up modes) before moving to Nominal Low Noise. We have been sitting (OMC_Whitening) at this lock state for around 2 - 2.5hrs.

Workstations were updated and rebooted.  Only operating system packages were updated.  Packages in conda, including control room tools, were not updated.

Continuing Gabriele's investigation from alog 71406

While damping violin modes in OMC_WHITENING this morning, I ran a DHARD_Y noise injection with a higher amplitude of 1.5 from 12:16 to 12:46 UTC:

Lockloss @ 10:33 UTC - 5.7 magnitude earthquake off Mexico's west coast. EQ mode activated at 10:31 and SRM saturations started about a minute before lockloss (surprisingly held on longer than I expected). Will hold H1 in DOWN until ground motion calms down; the 100-300mHz band has spiked to over 1µm/s

FAMIS 19667, last checked in alog 71251

ITMX_ST2_CPSINF_H1 high freq noise is high!
ITMX_ST2_CPSINF_H3 high freq noise is high!
ITMX_ST2_CPSINF_V3 high freq noise is high!

FAMIS 19985

Laser outage 6 days ago from interlock system work: alog 71281

Following the outage, PMC Refl seems noisier and higher than before. The FSS TPD signal has been dropping, but Jason plans to fix the alignment with an upcoming incursion into the enclosure.

TITLE: 07/18 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 132Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 18mph Gusts, 15mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.05 μm/s
QUICK SUMMARY: Taking over from Ryan C. H1 has been locked and observing for 7 hours. I plan to turn off the violin damping at 7:45am when the in-lock charge measurements start to test a theory about the damping staying on during a lockloss potentially keeping the violins rung up.

• All systems look good, wind is coming down and other ground motion is low

TITLE: 07/18 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 132Mpc
SHIFT SUMMARY:

• Locked and Observing for 7:00, Handing off to RyanS
• Ground motion has been elevated along with high winds, but they've started to taper off in the last 2 hours of the shift

Lock#1:

No interventions, pretty quick aquisition, standard waiting at OMC_WHITENING to damp violins

While damping violins Sheila and I tested pausing the OMC and turned the gain off and on 3 times alog71422

Backing into NLN and Observing at 00:01UTC, 1 SDF diff was accepted alog71418

LOG:                                                                                                               

STATE of H1: Observing at 127Mpc

Wind: 37mph Gusts, 26mph 5min avg

We've been locked and Observing for 3:00, the wind is picking up and ground motion is elevated.

I've been looking at a few things in regards to the violin ringups we've been getting from locklosses recently.

1) I looked at the ITMs OPLEVS and OSEMs motion during the locklosses and lock aquisitions comparing to before June 26/27th to see if there's more motion, but they do not seem to be experiencing more motion than they were. Example LL before June 26/27th: ITMX, ITMY and after (July 14th): ITMX, ITMY

2) I looked at the ETMs OPLEVs and OSEMs as well during LLs and aquisitions. I didn't see anything unusual during LLs but in DHARD_WFS (state 305) the ETMs always get kicked but the kicks seem a lot stronger recently?

• On 6/15 here's ETMX, and ETMY
• On 6/23 ETMX, and ETMY. Now for after June 26/27
• On July 4th heres ETMX, and ETMY
• On July 14th here's ETMX, and ETMY

3) I took some spectra a half hour into locks of the violins, one over 10 days, and another over a few weeks. The first harmonics in the 1000Hz range seem to be getting higher as time goes on and we have repeated locklosses. These templates are saved at /ligo/home/ryan.crouch/Desktop/Violin_Damping/post_06-27_violins (10 days) and ""/violins_halfhourlocked (3 weeks)

Sheila, RyanC

We did 3 rounds of setting the H1:OMC-ASC_MASTERGAIN to zero waiting 5 minutes then setting it back to its nominal 0.02.

23:31:39 H1:OMC-ASC_MASTERGAIN = 0

23:36:55 H1:OMC-ASC_MASTERGAIN = 0.02

We noticed that ADS turned off during this test, specifically H1:ASC-ADS_PIT4_OSC_CLKGAIN = 0 at 23:37:11 UTC

23:41:53 H1:OMC-ASC_MASTERGAIN = 0

23:47:09 H1:OMC-ASC_MASTERGAIN = 0.02

23:52:23 H1:OMC-ASC_MASTERGAIN = 0

23:58:01 H1:OMC-ASC_MASTERGAIN = 0.02

WP 11320

Multimode fiber pulled from the MSR to the Computer Users Room. Fiber will be patched in the MSR to the VPW. This will allow the fire panel in VPW to communicate with panel in cornerstation. Work finished around 3:30PM. Floor tiles had to be lifted to access floor cable tray and floor penetration from computer users room to control room.

F. Clara, M. Pirello

Marissa, Camilla

We edited the filters in H1:OAF-RANGE_RBP_9 to be a bandpass for the 52Hz noise (70950, 70250) we've been seeing. Hopefully it will be easier to monitor this peak. Can be monitored as H1:OAF-RANGE_BAND_9 from 22:50UTC. Filters attached.

TITLE: 07/17 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
SHIFT SUMMARY: Two locklosses during today's shift. There is some wind picking up now.
LOG:

• 17:42 UTC Lockloss, unknown why 71401
  • Fully automatic reacquire with injections from Gabriele while at OMC_WHITENING
• 19:49UTC NLN
• 22:28UTC Commissioning 71413
• 22:43UTC Lockloss alog 71415, cause wind?

TITLE: 07/17 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 22mph Gusts, 15mph 5min avg
    Primary useism: 0.14 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY:

• Taking over from Camilla
• Lockloss at 22:43 soon after I arrived, currently relocked at ENGAGE_ASC_FOR_FULL_IFO
• CDS/Vac/SUS/Dust/SEI looks good

This mornng we found that the CP1 thermocouples were out of range. The original CP1 fill code only checked the TCs on code startup and as part of each overfill pre-checks. It wasn't until I loaded my latest code this morning that the overnight TC issues became noticable.

I have made a second change to cp_overfill_ioc.py which now performs additional TC checks: hourly (GPS modulo 3600) and when the YAML file is read in (which defines the TC nominal range).

I have commandeered the vacuum SDF as a way of bringing out-of-bounds TCs to the overview. The channel H1:VAC-CP1_OVERFILL_TC_STATE was added to the h1vacuumsdf monitor.req and safe.snap. Its value should be 0x3 (bit0=TCA, bit1=TCB).

Attachment shows a test case where TCA nominal min was raised to -50C.

Carried out some noise injections while violin modes were being damped. Analysis will follow. Times below

ASC-DC3_Y_EXC
    butter("BandPass",8,0.5,5)zpk([],[1.5+i*2.59808;1.5-i*2.59808;1.5+i*2.59808;1.5-i*2.59808;1.5+i*2.59808;1.5-i*2.59808],1,"n")
   
ampl 10
start    PDT: 2023-07-17 12:12:25.248450 PDT
         UTC: 2023-07-17 19:12:25.248450 UTC
         GPS: 1373656363.248450
stop     PDT: 2023-07-17 12:14:28.217030 PDT
         UTC: 2023-07-17 19:14:28.217030 UTC
         GPS: 1373656486.217030

ampl 30
start   PDT: 2023-07-17 12:15:09.156033 PDT
        UTC: 2023-07-17 19:15:09.156033 UTC
        GPS: 1373656527.156033
stop    PDT: 2023-07-17 12:19:34.343574 PDT
        UTC: 2023-07-17 19:19:34.343574 UTC
        GPS: 1373656792.343574

DHARD_Y_EXC 
resgain(0.22, 2,14)resgain(0.48,3,20)resgain(2.5,8,15)cheby1("BandPass", 6,1, 0.05,3)gain(2000)zpk([1],[0.1],1,"n")

ampl 0.6
start   PDT: 2023-07-17 12:25:39.173166 PDT
        UTC: 2023-07-17 19:25:39.173166 UTC
        GPS: 1373657157.173166
stop    PDT: 2023-07-17 12:30:06.552000 PDT
        UTC: 2023-07-17 19:30:06.552000 UTC
        GPS: 1373657424.552000

ampl 1.0
start   PDT: 2023-07-17 12:30:58.643632 PDT
        UTC: 2023-07-17 19:30:58.643632 UTC
        GPS: 1373657476.643632

resgain(1.2,5,10)resgain(0.22,3,20)resgain(0.45,2,22)resgain(2.2, 1.5,23)
cheby1("BandPass",6,1,0.08,3)gain(1000)zpk([1],[0.1],1,"n")
ampl 1.0

start PDT: 2023-07-17 12:37:54.797826 PDT
      UTC: 2023-07-17 19:37:54.797826 UTC
      GPS: 1373657892.797826