TITLE: 08/28 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: A few lock losses during commissioning time and from an earthquake. We are recovering now and through DRMI.
LOG:

• 1600 Out of Observing for planned commissioning
• 1616 Lock loss
  • Relock consisted of an initial alignment and then back up without issue
• 1802 Back to low noise, commissioning resumes
• 1825 Lock loss
  • I tried to avoid an initial alignment by adjusting SRM and BS during DRMI locking. PRMI and Check_MICH_Fringes would trigger and slow the process down, so I'm not sure I saved any time at all.
• 1953 Observing
• 2222 Lock loss from 6.0 in El Salvador                                                                                                     

TITLE: 08/28 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 11mph Gusts, 9mph 5min avg
    Primary useism: 0.08 μm/s
    Secondary useism: 0.14 μm/s
QUICK SUMMARY:

• We're relocking following a big earthquake
  • At ENGAGE_ASC
• Wind isn't too bad

Closes FAMIS 28368
 

The processing and plotting code were both giving me some trouble, from not creating the coefficient files in /opt/rtcds/userapps/release/sus/common/scripts/quad/InLockChargeMeasurements/rec_LHO_charge_coeff/, and a bad ITMX measurement from July making shapes not match.

ITMXs measurement is also possibly not good, as it was complaining about its data structure and I was not able to process it.

raise ValueError("no Fr{{Adc,Proc,Sim}}Data structures with the "
ValueError: no Fr{Adc,Proc,Sim}Data structures with the name H1:SUS-ITMX_L3_ESDAMON_DC_OUT_DQ

The charges seem stagnant

Just lost lock from a 6.0 in El Salvador. We will begin relocking as soon as it settles down a bit.

Closes FAMIS 26005 , last checked in alog79586

HAMs:

Things look much calmer now, except for HAMs 7 & 8 still look as they did previously.

BSCs:

Things again are much calmer.

We have a preliminary report for the calibration status of LHO after the vent recovery, based on the measurement taken in LHO:79691. The report can be found here.

Taking a look at the PCALY to (GDS-CALIB_STRAIN_CLEAN) DARM broadband injection, there is an elevated amount of error between 30 and 60Hz. It would be worth considering to update the calibration at the next available opportunity, but it isn't pushing us beyond 10% mag/10deg phase yet. This is also corroborated by the monitoring page here.

N.B. I used pcal to GDS instead of to DELTAL_EXTERNAL because the GDS channel is already calibrated to meters for us. 

Since the ZM4 DAC output was close to saturation, I offloaded ZM4 yaw with SQZ ASC ON. The SQZ ASC seems to work and keeps good squeezing level. I reduced ZM4 yaw from -1408 to -1108 and the SQZ ASC moved ZM5 and ZM6. Then I offloaded AS42 ASC. I could reduce ZM4 yaw more, but lockloss happened. I accepted the attached SDF.

We are now running an initial alignment and will start main locking shortly.

We took some no SQZ time from 1600-1610 UTC today. Attached are comparisons of that time against 1455UTC today when we had 120Mpc range, and from yesterday with a better 140Mpc.

Latest output of the 'o4' script, TJ requested I add the GPS times.

Yesterday evening during some high wind time, Ryan C added some code to ISC_LOCK that he has been testing out in our TEST guardian node (mentioned in his summary alog79749). While successful in that node, ISC_LOCK started having connection issues for channels that exsist in the SDF. Stopping and starting the node resulted in different channels that it couldn't connect to each time. I've removed this from ISC_LOCK for now, but kept the main function in ISC_library.py. Ryan and I will try to figure out some different testing to be done before implementing again.

The well pump is currently running to replenish the fire water tank as we are bordering on the low-limit threshold. Coordination with the operator did take place ahead of the start command. Pump will run for four hours beginning at 9:28 pst.

C. Soike T. Guidry

Wed Aug 28 08:10:00 2024 INFO: Fill completed in 9min 56secs

Richard confirmed a good fill via camera.

TITLE: 08/28 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 137Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 4mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY: Locked for 8 hours, calm environment so far. Verbal has record of PI31 ringing up 30min ago, but it must have damped. I wonder if this gain also needs to be changed though. Our range is quite erradic for this lock. It sounds like this is due to the SQZ whistles that Sheila mentioned in her alog79757. Planned commissioning today from 9-12 PST.

I was able to new SRCL and MICH feedforward using the iterative method. Measurements were taken in alog 79693.

The current MICH FF is performing well except for below 30 Hz, so that's where I targeted in my fit. SRCL needed some improvement everywhere.

The new MICH filter is saved and loaded in FM8 and the new SRCL filter is saved and loaded in FM5. They are both labeled with the date '8-27-24'.

To compare how these filters are performing, I would use the templates Oli saved in the above alog, but first save the live trace as a reference to compare against.

I have not yet done the PRCL fit because I want to see how SRCL performs, and maybe redo the PRCL injections before trying the fit.

WP12061 Upgrade RCG h1susex, remove LIGO-DAC delays

EJ, Erik, Jonathan, Dave, Daniel, Marc:

h1susex RCG was upgraded to a custom 5.3.0 specifically for the IOP to remove a delay in the new LIGO 28AO32 DAC. We compliled all of the user models with this RCG as well.

Our first restart was a simple model restart, but we got Dolphin errors. So our second restart was to fence h1susex from the Dolphin fabric and power cycle h1susex via IPMI. After this the models started with no issues.

No DAQ restart was required.

Code path is /opt/rtcds/rtscore/advLigoRTS-5.3.0_dacfix

WP12063 Alert System

Dave:

The locklossalert system code was modified to permit an alert window which spans over midnight, needed for the new owl shift hours.

Note that the business/every day filter is applied after the minute-in-day filter, so a window starting Friday evening and extending into Saturday morning will cut off at midnight if business days only is selected.

One other change:

For everyone subscribed to Guardian alerts, if for any reason the Guardian EPICS record cannot be read (node down, h1guardian1 down) the alert will now default to SEND.

Guardian Reboot

TJ:

h1guardian1 was rebooted at 08:21 PDT. All nodes except TEST came back automatically. TJ worked on TEST and got it going.

MSR Rack Cleanup

Jonathan:

Jonathan removed two test switches from the MSR racks which are no longer needed.

I ran A2L while we were still thermalizing, might run again later. No change for ETMY but the ITMs had large changes. I've accepted these in SDF, I reverted the tramps that the picture shows I accepted. I didn't notice much of a change in DARM or on the DARM blrms.

         ETMX P
Initial:  3.12
Final:    3.13
Diff:     0.01

         ETMX Y
Initial:  4.79
Final:    4.87
Diff:     0.08

         ETMY P
Initial:  4.48
Final:    4.48
Diff:     0.0

         ETMY Y
Initial:  1.13
Final:    1.13
Diff:     0.0

         ITMX P
Initial:  -1.07
Final:    -0.98
Diff:     0.09

         ITMX Y
Initial:  2.72
Final:    2.87
Diff:     0.15

         ITMY P
Initial:  -0.47
Final:    -0.37
Diff:     0.1

         ITMY Y
Initial:  -2.3
Final:    -2.48
Diff:     -0.18