Attached is a look at the OMCs for this lock and the ring up starts about 8hrs ago.

Have sent a text to Rahul regarding violins.

TITLE: 09/30 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 12mph Gusts, 8mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY:

At first glance:  H1's been locked 14hrs w/ slow drift down of ~4Mpc over last 8-ish hrs (but turning around in last hour).  Otherwise fairly quite other than slight breezes of 10mph around the site. 

• Operator alarm1 computer has no apps running on it (i.e. verbal alarms, alarm handlers, teamspeak).  The speaker was also unmuted and at low volume---will need to start that back up.

At 2nd glance: 

• nuc30:  DARM FOM appears to have the issue where all the live channels get a big glitch about every minute. (attached #1)
• nuc31:  OMC dcpds (which we would use to gauge violins) is getting bigger (attached #2).  This led me to look back at DARM and yes, the violin fundamental mode is BIG (peak is behind the legend) [attached #3].

TITLE: 09/30 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:

Uknown Lockloss: 00:05 UTC
relocking started at 00:06 UTC

Nominal_LOW_NOISE reached and PI Mode 31 Spiked to 150! at 00:58 UTC

ITMY Mode 5 is increasing steadily since the beggining of the lock 3:08 UTC I changed the Damping setting from -0.04 to 0 to +0.04 to see If I could damp it. Channel name : H1:SUS-ITMY_L2_DAMP_MODE5_GAIN
3:31 UTC +0.04 gain is taking ITMY mode 5 back down.
The issue is that ITMY Mode 5 is coupled with ITMY mode 6 and while I have changed the gain setting for Mode5 and now mode 5 is slowly going down. Unfortunately Mode 6 is still ringing up and has been for the last 3 locks.
Next shift should keep an eye on those Violin modes. Plots for the mode 5 & mode 6  over the last 2 days attached.
Tagging SUS.
 

LOG:
no log

Trend the BRSs' DRIFTMON Famis 26435

BRS-X is trending into the red at the begginingof the month.

BRS-Y looks good in comparison.

ENDY Station Measurement:
During the Tuesday maintenace, the PCAL team(Rick Savage & Tony Sanchez) went to ENDY with Working Standard Hanford aka WSH(PS4) and took an End station measurement.
The ENDY Station Measurement was carried out according to the procedure outlined in Document LIGO-T1500062-v15, Pcal End Station Power Sensor Responsivity Ratio Measurements: Procedures and Log, and was completed by 11 am.

First thing we did is take a picture of the beam spot before anything is touched!

Martel:
We started by setting up a Martel Voltage source to apply some voltage into the PCAL Chassis's Input 1 channel and we record the times that a -4.000V, -2.000V and a 0.000V signal was sent to the Chassis. The analysis code that we run after we return, uses the GPS times, grabs the data and created the Martel_Voltage_Test.png graph. We also did a measurement of the Martel's voltages in the PCAL lab to calculate the ADC conversion factor, which is included on the document.

After the Martel measurement, the procedure walks us through the steps required to make a series of plots while the Working Standard(PS4) is in the Transmitter Module. These plots are shown in WS_at_TX.png.

Next steps include: The WS in the Receiver Module, These plots are shown in WS_at_RX.png.

Followed by TX_RX.png which are plots of the Tranmitter module and the receiver module operation without the WS in the beam path at all.
The last picture is of the Beam spot after we had finished the measurement.
All of this data is then used to generate LHO_ENDY_PD_ReportV2.pdf which is attached, and a work in progress in the form of a living document.

Special Notes:  Line 10 in the pcal_params.py needs to be changed from:
PCALPARAMS['WHG'] = 0.916985 # PS4_PS5 as of 2023/04/18
To:
PCALPARAMS['WHG'] = 0.9159 #PS4_PS5 as of 2023-08-22
This change would reflect the changes we have observed in the measurements of PS4_PS5 responsivity ratio measurements taken in the lab which affect the plots of Rx Calibration in sections 14 and 22 of the LHO_EndY_PD_ReportV2.pdf.
Investigations have shown that PS4 has changed but not PS5 OR Rx Calibration. There may also be another location where this change needs to be made to accuraetely depict the changes found in PS4.

All data and Analysis has been commited to the SVN.
https://svn.ligo.caltech.edu/svn/aligocalibration/trunk/Projects/PhotonCalibrator/measurements/LHO_EndY/tD20230926/

PCAL Lab Responsivity Ratio Measurement:
A WSH/GSHL (PS4/PS5)FrontBack Responsivity Ratio Measurement was ran, analyzed, and pushed to the SVN.
The analysis of this measurement produces 4 PDF files which we use to vet the data for problems.
raw_voltages.pdf
avg_voltages.pdf
raw_ratios.pdf
avg_ratios.pdf

All data and Analysis has been commited to the SVN.
https://svn.ligo.caltech.edu/svn/aligocalibration/trunk/Projects/PhotonCalibrator/measurements/LabData/PS4_PS5/

BackFront configuration PS4/PS5 Responsivity Ratio.
PCAL Lab Responsivity Ratio Measurement:
A WSH/GSHL (PS4/PS5)BF Responsivity Ratio measurement was ran, analyzed, and pushed to the SVN.
The analysis of this measurement produces 4 PDF files which we use to vet the data for problems.
BFraw_voltages.pdf
BFavg_voltages.pdf
BFraw_ratios.pdf
BFavg_ratios.pdf

This adventure has been brought to you by Rick Savage & Tony Sanchez.

Unknown Lockloss
Seismic, and Pi's looked fine during this lockloss.

Violins ITMY modes (5,6,8) and ETMY mode19 were all increaseing but not to an unreasonable amount that would have caused a lock loss. There weren't any saturation alerts it just happened out of the blue.
 

TITLE: 09/29 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 6mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.13 μm/s
QUICK SUMMARY:
H1 has been locak for just under an hour.
 

TITLE: 09/29 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY:

Started shift with H1 in OBSERVING.  2hr commissioning break (followed by an immediate lockloss)!
LOG:

• 1521-1547 Optics lab/vac prep cleaning (karen)
• 1704 (1004amPT) H1 takes a notable drop in range from 153 down to 140Mpc;  It slowly returned to normal over the following hour.  
  • There were no obvious environmental culprits 
  • But Oli found that it was related to the CP1 autofill (as seen over the summer in July)
• 1746-1806 EY HVAC checks--no VEA incursion (tyler)
• 1826-1853 MY run (camilla)
• 1902 Down for COMMISSIONING (camilla, naoki)
• 2013-2125 MX turbo pump work (jordan)
• 2025-2125 MX turbo pump work (travis)
• 2106 Back to COMMISSIONING
• 2109 LOCKLOSS after an 18.5hr lock
• 2113-2125 MY for parts (travis)
• 2226 Back to OBSERVING

There is a noticeable dip in today's range 09/29 at 17:00UTC (attachment1). Zoomed in(attachment2), it is two separate dips set next to each other, where each affected our range for about 20 minutes.

I found that the H1:PEM-CS_ACC_BEAMTUBE_YMAN_X accelerometer had measured a lot of movement at the time of the first dip and lowered our range by almost 10Mpc (excluding the glitches)(attachment3). We found that this dip was correlated to the CP1 fill(73169) that started at 17:00UTC and lasted 18 minutes(attachment4). This had been seen in the range previously by Marissa and Brina (71301).

With regards to the second range dip we have not found a cause for that yet - all we know is that it showed up the most distinctly in BLRMS bands 1(10-20Hz) and 5(100-450Hz)(attachment5). It is also possible that this dip would otherwise have been a small range fluctuation if not for the CP1 fill having just affected us.

After LLO's 67058 ring heater tests, we adjusted our ETM RHs, hoping to reduce our high frequency noise that LLO induced during their test.

We adjusted ETMX up from 0.9W to 1.1W and ETMY down from 1.0W to 0.9W/segment 19:02 to 21:05UTC.

No big changes seen, our range, circulating power and squeezing got worse and kappa_c slightly increased, plotted attached. No visible change in DARM. Our HOM peaks moved slightly towards each other as expected. We lost lock before we thermalized back to nominal RH powers and could check that the offloading of SQZ pointing Naoki was doing ( 73171) didn't have an effect on the IFO.

Interesting is that with our best low frequency noise in end of march 68491, our circulating powers with 60W input in were actually lowest they have been. Plot attached.

As reported in alog73105, the ZM6 looks more saturated recently so I offloaded the ZM6 by moving ZM4. The ZM5 and ZM6 follow the movement of ZM4 by SQZ ASC. The first attached figure shows that the ZM6 LL/UR output reduced from 32000 to 21000 by ZM4 change. The second/third attached figures show the saturation of ZMs before/after this offload. You can see that the ZM6 LL/UR output reduced from red to orange region, while the ZM4 output increased from green to orange region. I have not seen the obvious SQZ BLRMS change by this offload.

I have updated the picket fence code in an intermediate step towards a better GUI. The details are in SEI log 2281.

The current set of stations for LHO can be seen in the attached images. The red lines in the plot represent the direction of incoming earthquakes on the database.

Fri Sep 29 10:18:06 2023 INFO: Fill completed in 18min 1secs

Gerardo confirmed a good fill curbside.

PSL Report FAMIS report:
Laser Status:
    NPRO output power is 1.829W (nominal ~2W)
    AMP1 output power is 67.04W (nominal ~70W)
    AMP2 output power is 134.8W (nominal 135-140W)
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN

PMC:
    It has been locked 7 days, 1 hr 3 minutes
    Reflected power = 16.23W
    Transmitted power = 109.0W
    PowerSum = 125.2W

FSS:
    It has been locked for 0 days 13 hr and 30 min
    TPD[V] = 0.7832V

ISS:
    The diffracted power is around 2.6%
    Last saturation event was 0 days 13 hours and 30 minutes ago

Possible Issues: None

TITLE: 09/29 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 5mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.13 μm/s
QUICK SUMMARY:

H1's been locked 12.5hrs, useism continues drifting down, and winds are calm, and overnight all looks well from the Control Room this morning (L1's range is lower than H1 due to No Squeezer.).

TITLE: 09/29 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Mostly quiet shift with just one lockloss and a straightforward recovery. H1 has now been locked and observing for 4.5 hours.

• 00:37 Lockloss - alog
• 01:21 Alignment too poor to get PRMI (MICH_FRINGES didn't help), starting initial alignment
• 01:41 Alignment complete, starting lock acquisition
• 02:34 Reached NLN, fully automated acquisition
• 02:53 Started observing

LOG:

No log for this shift.