Continued from alog 73180.

IY mode 05/06 has been decreasing, although very slowly (after damping it for more than 12hrs with 50% of nominal gain value. i.e. -0.02).

Tony will ramp up the gain to nominal (-0.04) and watch over it for the next few hours. If it goes fine then the mode should be damped by tomorrow, else we will continue with reduced gain. I will check again in the morning.

I will switch ON damping gains for IY mode 04, 05, 07 and 08 tomorrow morning, once IY06 is under control.

03:48 UTC Changed the Gain on ITMY Mode 5 to -0.04 from -0.02, which is nomial. the goal is to determine if the nomial setting needs to change.
I'll continue to keep an Eye on ITMY mode 5 and 6 thoughout the night and if they start to trend back up I'll take the gain back to -0.02.

H1:SUS-ITMY_L2_DAMP_MODE5_RMSLP_LOG10_OUTMON = 3.32
H1:SUS-ITMY_L2_DAMP_MODE6_RMSLP_LOG10_OUTMON = 4.94

Rahul has advised me that until ITMY Mode 5&6 are under control ITMY Modes 3,4,7 and 8 should all be undamped aswell.

Famis 26254

Checking Fan Vibrometers

H0:VAC-MY_FAN2_270_1_ACC_INCHSEC which has a dip and then rises back up to 0.3.
H0:VAC-MX_FAN1_370_2_ACC_INCHSEC has a suble increase in it's trace.
But both are below the 0.7 threshhold.

 

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 154Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 11mph Gusts, 7mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY:
ITMY Mode6 Rung up far more than I thought it would have. Rahul and Corey Have been damping it all day and it has come down by only 0.5. I will continue to keep an eye on ITMY mode 6 for the rest of the shift. 
But we are still locked and Observing for 22+ hours!

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
INCOMING OPERATOR: Tony
SHIFT SUMMARY:

Arrived to 14hr-locked H1, but eventually noticed a slowly-ringing-up violin mode via OMC_DCPD ndscope & DARM FOM (this brought range down about 5Mpc over 12-ish hours).  Contacted Rahul and he found the culprit (the usual, ITMy Mode 5&6) and worked on restoring.  alarm1 computer had no apps running, so I needed to bring those back.  DARM FOM was glitching madly (christmas tree mode?) at the beginning of the shift.  It was huge for all live channels and occurred every few seconds rendering it useless.  Was not a CDS issue after Dave checked.  Did our rung out violins do this?  I don't remember that feature.)

ITMy violins continue to be monitored w/ no/low gain to allow them to continue to ring down (Can finally see the 500Hz violin peak below the legend on DARM FOM---it was hidden behind it all day!)

Access System says the OSB main & kitchen doors have issues, but they are both locked.
LOG:

• 1526 Verbal says incoming earthquake from Canada, but  I don't see that.  On USGS and other sites around that time there is a 4.7 in northern california at 1526...maybe this one?  At any rate we went to EARTHQUAKE mode and back to CALM while h1 rode it out.
  • 1717 Received another Verbal EQ from Canada, but it's the same one from Ferndale, CA.  

Violin modes continue their slow ring down (attached is the OMC DCPD ndscope for this 19hr lock showing the ring up & down thus far.) & H1 recovered last night's range drop after Rahul's violin mode work.  DARM FOM appears to have calmed down a little. Had a couple small Calif earthquakes (listed as Canada by Verbal/Seismon).

Sat Sep 30 10:15:28 2023 INFO: Fill completed in 15min 24secs

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.