TITLE: 08/17 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: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 21mph Gusts, 13mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:
Inherited H1 With a 17 hour lock in NOMINAL_LOW_NOISE && OBSERVING
HVAC turned back on, And I'll be watching the temps tonight.

Control room users have asked more than once to have some type of alert for when LLO goes into or out of Observing. I've made this, heavily based on our read only LLO medm command. This will create an epics connection to LLO after you input your ligo.org password and then it uses our text to speech program (picotts) to announce any changes to the L1:GRD-IFO_STATE (our intention bit). I put it in userscripts so:

Robert and I went into the Fan rooms to check on Supply Fan 4.  When we entered the hall between Fan rooms there was water on the floor.   The last time this happened it was a clogged condensate drain.  So we check the Fan 1 and 2 room and sure enough more water.

Starting at 2:30 PM until 3 PM PST we (Randy, Fil and Richard) ran a shop vac outside the Fan rooms where the condesate drains exit the enclosure.  We were able to drain the condensate pans so no additional water shoule run onto the floor. 

We have left the water on the floor in the fan rooms as a Tuesday activity.

Thank you Randy for your assistance.

Followed the usual instructions on wiki/TakingCalibrationMeasurements.

Simulines start GPS: 1376343784.859387
Simulines end GPS: 1376345111.425289
 

2023-08-17 22:04:53,037 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_
SS/DARMOLG_SS_20230817T214248Z.hdf5
2023-08-17 22:04:53,057 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DA
RM_SS/PCALY2DARM_SS_20230817T214248Z.hdf5
2023-08-17 22:04:53,068 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_
L1_SS/SUSETMX_L1_SS_20230817T214248Z.hdf5
2023-08-17 22:04:53,079 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_
L2_SS/SUSETMX_L2_SS_20230817T214248Z.hdf5
2023-08-17 22:04:53,089 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_
L3_SS/SUSETMX_L3_SS_20230817T214248Z.hdf5
 

Thu Aug 17 10:08:19 2023 INFO: Fill completed in 8min 15secs

Robert did an HVAC off test. Here is a comparison of GDS CALIB STRAIN NOLINES from earlier on in this lock and during the test. I picked both times off the range plot from a time with no glitches.

Improvement from removal of 120 Hz jitter peak, apparent reduction of 52 Hz peak, and broadband noise reduction at low frequency (scatter noise?).

I have attached a second plot showing the low frequency (1-10 Hz) spectrum of OMC DCPD SUM, showing no appreciable change in the low frequency portion of DARM from this test.

Fil informed me that the PSL chiller was alarming. Oli and I went out there and it had a low level alarm. We added 100mL and brought it back near the max level. Last log was from exactly a month ago.

Please disregard FMCS chiller alarms for the next hour while Robert runs his tests which require the chillers to be shut down for short periods.

TITLE: 08/17 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: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 8mph Gusts, 6mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY: Locked for 9 hours, range has a few points almost touching 160Mpc. Nice.

TITLE: 08/17 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:
Lockloss 23:29 UTC
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1376263782

A change was made to ISC_LOCK that will lead to an SDF Diff that will need to be accepted.

Trouble locking DRMI even after PRMI
Ran Initial Alignment.

Elevated Dust levels in Optics labs again.

locking process started at 00:31 UTC
1:16 UTC made it to NOMINAL_LOW_NOISE
1:35 UTC Made it to Observing

lockloss from NLN @ 2:22 UTC almost certainly because of a Pi ring up and a series of Locklosses at LOWNOISE_LENGTH_CONTROL Edit*: It wasn not certain at all infact.

relocking went smoothly until, Lost lock at LOWNOISE_LENGTH_CONTROL @ 3:11 UTC

relocking went through PRMI and took a while, Lost lock at LOWNOISE_LENGTH_CONTROL again at @ 4:14 UTC

I have lost lock twice at LOWNOISE_LENGTH_CONTROL tonight. I am concerned that it may be due to  alog https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=72262

Which is where there is a change to that state.
The counter argument to this is that I went past this earlier in my first lock of the night. Which was AFTER ISC_LOCK was loaded.
I'm doing an Initial Alignment again tonight to see if it's just poorly aligned instead, and to buy my self sometime to investigate.
I posted my findings in matter most and in the lock loss alog above . Then Called in the Commishoners to see if there was anything else I should look at.
Lines 5471 , 5472 were changed, and with the help of Danielle and Jenne pointing to line 5488 for another change that was reverted on ISC_LOCK.py, Locking went well from LOWNOISE_LENGTH_CONTROL all the way up to NLN

See comments in https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=72262 for Specifics

Made it to NOMINAL_LOW_NOISE @ 5:58 UTC
Made it to Observing @ 6:02 UTC

LOG: empty

Initial Unknown Lockloss from NLN (Maybe PI related?) :
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1376274187
ScreenShot 1 ScreenShot 2 ScreenShot 3
23-08-17_02:05:06.841133Z ISC_LOCK [NOMINAL_LOW_NOISE.run] USERMSG 0: SUS_PI: has notification
2023-08-17_02:05:12.031195Z ISC_LOCK [NOMINAL_LOW_NOISE.run] USERMSG 0: SUS_PI: has notification
2023-08-17_02:05:22.397983Z ISC_LOCK [NOMINAL_LOW_NOISE.run] USERMSG 0: SUS_PI: has notification
2023-08-17_02:15:15.962160Z ISC_LOCK [NOMINAL_LOW_NOISE.run] USERMSG 0: SUS_PI: has notification
2023-08-17_02:15:21.158619Z ISC_LOCK [NOMINAL_LOW_NOISE.run] USERMSG 0: SUS_PI: has notification
2023-08-17_02:22:49.089168Z ISC_LOCK [NOMINAL_LOW_NOISE.run] USERMSG 0: SQZ_MANAGER: has notification
2023-08-17_02:22:49.343171Z ISC_LOCK [NOMINAL_LOW_NOISE.run] Unstalling IMC_LOCK
2023-08-17_02:22:49.571864Z ISC_LOCK JUMP target: LOCKLOSS
2023-08-17_02:22:49.578399Z ISC_LOCK [NOMINAL_LOW_NOISE.exit]
2023-08-17_02:22:49.629938Z ISC_LOCK JUMP: NOMINAL_LOW_NOISE->LOCKLOSS
2023-08-17_02:22:49.629938Z ISC_LOCK calculating path: LOCKLOSS->NOMINAL_LOW_NOISE
2023-08-17_02:22:49.632228Z ISC_LOCK new target: DOWN
2023-08-17_02:22:49.636266Z ISC_LOCK executing state: LOCKLOSS (2)
2023-08-17_02:22:49.647637Z ISC_LOCK [LOCKLOSS.enter]


Followed by a Lockloss at LOWNOISE_LENGHT_CONTROL

https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1376277430


2023-08-17_03:16:40.676453Z ISC_LOCK [LOWNOISE_LENGTH_CONTROL.main] ezca: H1:LSC-OUTPUT_MTRX_2_13 => -1
2023-08-17_03:16:40.676886Z ISC_LOCK [LOWNOISE_LENGTH_CONTROL.main] ezca: H1:LSC-SRCL1_OFFSET => 0
2023-08-17_03:16:40.677417Z ISC_LOCK [LOWNOISE_LENGTH_CONTROL.main] ezca: H1:LSC-MICHFF_TRAMP => 10
2023-08-17_03:16:40.677727Z ISC_LOCK [LOWNOISE_LENGTH_CONTROL.main] ezca: H1:LSC-SRCLFF1_TRAMP => 10
2023-08-17_03:16:40.677943Z ISC_LOCK [LOWNOISE_LENGTH_CONTROL.main] timer['wait'] = 10
2023-08-17_03:16:50.678146Z ISC_LOCK [LOWNOISE_LENGTH_CONTROL.run] timer['wait'] done
2023-08-17_03:16:50.717927Z ISC_LOCK [LOWNOISE_LENGTH_CONTROL.run] ezca: H1:LSC-MICHFF_GAIN => 1
2023-08-17_03:16:50.718315Z ISC_LOCK [LOWNOISE_LENGTH_CONTROL.run] ezca: H1:LSC-SRCLFF1_GAIN => 1
2023-08-17_03:16:50.718524Z ISC_LOCK [LOWNOISE_LENGTH_CONTROL.run] timer['wait'] = 10
2023-08-17_03:16:52.342688Z ISC_LOCK [LOWNOISE_LENGTH_CONTROL.run] Unstalling OMC_LOCK
2023-08-17_03:16:52.344038Z ISC_LOCK [LOWNOISE_LENGTH_CONTROL.run] Unstalling IMC_LOCK
2023-08-17_03:16:52.576674Z ISC_LOCK JUMP target: LOCKLOSS
2023-08-17_03:16:52.576674Z ISC_LOCK [LOWNOISE_LENGTH_CONTROL.exit]
2023-08-17_03:16:52.634809Z ISC_LOCK JUMP: LOWNOISE_LENGTH_CONTROL->LOCKLOSS
2023-08-17_03:16:52.634809Z ISC_LOCK calculating path: LOCKLOSS->NOMINAL_LOW_NOISE
2023-08-17_03:16:52.635554Z ISC_LOCK new target: DOWN
2023-08-17_03:16:52.674469Z ISC_LOCK executing state: LOCKLOSS (2)
2023-08-17_03:16:52.674675Z ISC_LOCK [LOCKLOSS.enter]

Despite some great efforts to track down the source from Jenne and Jeff, we are still seeing a 102 Hz line rung up right at the end of the lownoise_length_control state. Since we had a random lockloss, I asked Tony to take us to lownoise_esd_etmx and I tried walking through lownoise length control by hand (copying the guardian code line by line into the shell).

The lines 5427-5468 ramp various gains to zero, set up the filters and drive matrix for the LSC feedforward, and prepare for the SRCL offset. These lines run fine and do not ring up the 102 Hz line.

I am able to run the first action line of the run state, which sets the MICH FF gain to 1 (line 5480). This runs fine, no 102 Hz line. Then, I ran the next line to turn on the SRCL FF gain (line 5481). This caused an immediate lockloss (huh?), despite the fact that this code has run many times just fine.

On the next lock attempt, I tried running the MICH and SRCL gain lines at the exact same time. Also immediate lockloss.

I have no idea why this is such an issue. All it does it ramp the gains to 1 (the tramps are set on a previous line to 3 seconds).

Both of these locklosses seem to ring up a test mass bounce mode, suggesting that the SRCL FF (I assume) is kicking a test mass pretty hard.

This might be a red herring, or maybe it's a clue. I don't see any 102 Hz line during these locklosses though.

The offending lines:

As a followup of alog 72061, a batter-operated voltage reference was connected to the OM2 heater chassis. Beckhoff cable was disconnected for now.

Please check if the 1.66Hz comb is still there.

Julianna Lewis, TonyS, RickS

This morning we moved the upper (inner) Pcal beam at X-end down by 5 mm at the entrance aperture of the Pcal Rx sensor to test the impact on the calibration of the Pcal system at X-end.

We expect that the impact on the calibration of the Xend Pcal will be given by the dot product of the 

The work proceedes as follows:

• Disabled all excitations for the Xend Pcal system. Rx PD output ~0.443 W. (GPS time 1375545485)
• Blocked the lower (outer) beam in the transmitter module. Rx output ~0.2206 W.  (GPS time 137554600)
• Assessed the position of the upper Pcal beam at the entrance aperture of the Rx integrating sphere.  It appeared to be well centered (see first attached photo).
• Installed a target at the entrance aperture of the Rx sensor and adjusted the roll angle so that the rows of holes in the target were aligned with the vertical and horizontal directions (see third and second attached photos.).
• Increased the Pcal AOM offset in the OFS servo from 3.33 to 5.0. (GPS time 1375547403)
• Adjusted the beam position at the Rx sensor aperture (and on the ETM) using the last steering mirror in the Tx module to optimize the sensor output voltage (and thus center the beam at the center of the Rx sensor aperture). (GPS time 1375547610)
  • The Rx sensor output level increased to about 0.301 W from about 0.295 W by tweaking the aligment. (see fourth attached photo)
• We initially moved the Pcal beam up by 5 mm, but became concerned that we might be getting close to the edge of the coating on the output vacuum window because the transmitted light level was significantly lower (few percent).
• We moved the beam down to the lower hole in the target and aligned it to optimize the transmitted level at about 0.300 W (GPS time 137549300) (see fifth attached photo).
• Removed the target from the Rx sensor.  Rx sensor level 0.33 W. With OFS offset at 5.0.  (GPS time 1375549520)
• Reduced the OFS offset to 3.33 from 5.0.  Rx sensor level 0.221 W.  (GPS time 1375549950)
• Removed block from lower (outer) beam in the Tx module.  Rx sensor level 0.4438 W. (GPS time 1375551330) (See last attached photo)

We expect that this upper beam movement will change the unintended rotation of the test mass and change the calibration of the Rx output by about 0.2 % This assumes that we have moved at roughly 45 deg. with respect to the roughly 22 mm interferometer beam offset and that the offset on the surface of the ETM is roughly half of that seen at the Rx module: - 2.5 mm / 2 x 22 mm x 0.707 x 0.94 hop / mm^2 = -18 hop (hundreths of one percent).  So we expect to see that X/Y comparison factor will change from about 1.000 to 0.9982.

First observed as a persistent mis-calibration in systematic error monitoring Pcal lines which measure PCAL / GDS-CALIB_STRAIN affecting both LLO and LHO, [LLO Link] [LHO Link], characterised by these measurements consistently disagreeing with the uncertainty envelope.
It us presently understood that this arises from bugs in the code producing the GDS FIR filters there exists a sizeable discrepancy, which Joseph Betzwieser is spear-heading a thorough investigation to correct,

I make a direct measurement of this systematic error by dividing CAL-DARM_ERR_DBL_DQ / GDS-CALIB_STRAIN , where the numerator is further corrected for kappa values of the sensing, cavity pole, and the 3 actuation stages (GDS does the same corrections internally). This gives a transfer function of the difference induced from errors in the GDS filters.

Attached in this aLog, and its sibling aLog in LLO, is this measurement in blue, the PCAL / GDS-CALIB_STRAIN measurement in orange, and the smoothed uncertainty correction vector in red. Attached also is a text file of this uncertainty correction for application in pyDARM to produce the final uncertainty, in the format of [Frequency, Real, Imaginary].