We've been Observing since before the start of my shift and we have been Locked for 5 hours. Our range hasn't gotten better and I haven't had a chance to tune up the squeezing. Squeezing is pretty bad with both the 350Hz and the 1.7kHz bands being around -1.2, with the lowest they got to being ~-1.5 a couple of hours into the lock. Besides the abysmal range, everything is going well.

1. The average duty cycle for Hanford for this week was 69.25%, with a high of 95.6% on Friday
2. The BNS range fluctuated between 150-160 Mpc, the lower end 150 Mpc is due to high winds

3. Strain lines in h(t):
   Some of the strain lines especially lower frequency can be explained due to ground motion
   Noise lines in h(t) spectrogram every day at 500Hz most of them can be correlated to after H1 gets locked back, but some of these persist. I 
   have attached a plot highlighting it


4. Some glitch clusters happen right before losing lock and can be explained by comparing to alogs, others (the one tuesday) are unexplained

5. Lockloss:
   Some locklosses can be explained due to increased ground motion (eg: monday, wednesday and friday locklosses)
   First FSS_OSCILLATION lockloss from NLN in a year on wednesday 18th Sept
   Another lockloss that tagged FSS on Thursday
   Lockloss with FSS oscillation tag on Saturday

6. PEM tab:
   Most of the noise in corner BSCs happens when H1 is not observing
   Noise in acoustics can be related to environmental factors like wind
   Recurring noise line in BSC1 motion X and sometimes other BSCs too at ~11 Hz every day starting at 15:00 UTC

7. H1:ASC-DHARD_Y_OUT_DQ and H1:PEM-EX_EFM_BSC9_ETMX_Y_OUT_DQ are present multiple times in the hveto tab, there are also some new channels.
8. The fscan plots have appeared and the line count varies from 600 to ~850 with an average of 684.

TITLE: 09/30 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 137Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Planned commissioning time this morning, then a lockloss early afternoon with a simple relocking process afterwards made for a relatively light day.

• 14:30 - H1 locked and observing for 4 hours
• 15:35 - Dropped observing for planned commissioning time
• 18:37 - Back to observing
• 20:26 - Lockloss - alog80376
• 22:04 - Back to observing

H1 has now been locked and observing for 1.5 hours.

LOG:

TITLE: 09/30 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 139Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 8mph Gusts, 3mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.17 μm/s
QUICK SUMMARY:

Observing at 140 Mpc and have been Locked for 1.5 hours. Might drop out of Observing to run sqz align if Livingston loses lock or also drops out.

WP 12095

Damaged lightning rod and mounting bracket on the OSB viewing platform replaced.

Lockloss @ 20:26 UTC - link to lockloss tool

This would appear to be another FSS-related lockloss, as evidenced by the fact that the IMC and arms lost lock at the same time, we see some glitches in the FSS fast channel, and nothing else jumps out to me for another cause.

Sheila, Camilla

As Naoki/Vicky started, I moved ZM4,6,5 -50urad and then +50urad and recorded change in AS_A/B_AS42_PIT/YAW. It may have been easier if I'd changed AS_A/B AS42 offsets to have PIT/YAW outputs zero'ed to start with...  

Plot attached of ZM4, ZM5 and ZM6. 

There is a some cross coupling, and ZM5 gave very strange results in pitch and yaw with overshoot and the same direction of AS42 recorded with a different direction of alignment. This suggests we should use ZM4 and ZM6 as we do for our SCAN_SQZ_ALIGNMENT script.

Sensing/Input matrices calculated using /sqz/h1/scripts/ASC/AS42_sensing_matrix_cal.py

Using ZM4 and ZM6.
PIT Sensing Matrix is:
[[-0.0048 -0.0118]
 [ 0.0071  0.0016]]
PIT Input Matrix is:
[[ 21.02496715 155.05913272]
 [-93.29829172 -63.07490145]]
YAW Sensing Matrix is:
[[-0.00085 -0.009  ]
 [ 0.0059   0.0029 ]]
YAW Input Matrix is:
[[  57.2726375   177.74266811]
 [-116.52019354  -16.78680754]]

H1 went out of observing from 15:35 to 18:37 UTC for planned commissioning activities, which included PRCL FF testing, an update to the SQZ_PMC Guardian, shaker tests at HAM1, ITMY compensation plate sweeps, and measuring the AS42 sensing matrix by moving ZMs.

H1 has now been locked for 8 hours.

This is a late entry to list everything we checked on Friday afternoon (which spilled to roughly midnight CT).

-- Current Status --
LHO is currently running the same cal configuration as in 20240330T211519Z. The error reported over the weekend using the PCAL monitoring lines suggests that LHO is well within the 10% magnitude & 10 degree error window after about 15 minutes into each lock (attached image). Here is a link to the 'monitoring line' grafana page that we often look at to keep track of the PCALY/GDS_CALIB_STRAIN response at the monitoring line frequencies. The link covers Saturday to today. This still suggests the presence of calibration error near 33Hz that is not currently understood but, as mentioned earlier, it's now well within the 10%/10deg window. We think that the SRCL offset adjustment in LHO:80334 and LHO:80331 accounts for the largest contribution to the improvement of the calibration at LHO in the past week. 

-- What's Been Tried --
No attempts by CAL (me, JoeB, Vlad) to correct the 33Hz error have been successful. Many things were tried throughout the week (mostly on Tuesday & Friday) that went without being properly logged. Here's a non-exhaustive list of checks we've tried (in no particular order):


  
We cross-checked every single front end filter and gain parameter in the pyDARM model file against what's installed at LHO. Other than non-impacting foton file changes (e.g. out-of-path module changes) the only mismatch we identified is that the bias voltage in pyDARM was set to 3.3 instead of the IFO's 3.25.
  
We quickly implemented SRC detuning by copying the LLO setup. I did this by making on-the-fly changes to pyDARM on a local copy of the repo. I'll have to follow up with what these exact adjustments entailed. This seemed to do what we expected but it did not significantly impact the large 33Hz error.
  
Some GDS pipeline-affecting parameters made their way into the pydarm ini at LHO. These changes were made around the time of the Cal F2F over the summer. I reverted them, regenerated GSTLAL filters and installed them in the GDS pipeline. This didn't help. The commits in question are d2bfe349, 8717a9f5, and dc7208e0.
  
We don't believe the delays being reported by the pyDARM fits of the actuation delay on the PUM stage. We made adjustments to the fitting parameters for this stage to increase the fit range to roughly 400Hz in the hopes that pyDARM would produce a somewhat believable number. More details on this item as time allows; we are going to tune our injections to reduce uncertainty on these measurements in particular. This tuning will need to be done in tandem with other tunings (e.g. reducing PCAL at low frequencies to avoid leakage from polluting simultaneous higher frequency measurements).
  
We made similar adjustments to the sensing fit parameters. We extended the low end of the fit range to better capture the detuning near 10Hz in the fit.
  
Once it approached midnight on Friday night we reverted everything and left the IFO back in the state we found it in. This process is also not straightforward and requires creating a new 'fake' pyDARM report each time due recently-discovered bugs in the pyDARM infrastructure. This bug is being tracked here.


--What Changed?--
We think the SRC change(s) on September 5 (LHO:79929, also discussed in LHO:79903) line up well with the time frame at which the 33Hz error issue popped up. Here is a screenshot showing that the 33Hz error showed up on September 5. I've also attached a shot of ndscope showing the SRCL offset change on 09/05 from -175cts to -290cts here. cal_better_after_srcl_changed.png shows the error tracked by the monitoring lines before and after the SRCL offset was changed back to -190cts. The last image is a scope shot of that change (here).

FAMIS 31053

The NPRO power, amplifier powers, and a few of the laser diodes inside the amps look to have some drift over the past several days that follows each other, sometimes inversely. Looking at past checks, this relationship isn't new, but the NPRO power doesn't normally drift around this much. Since it's still not a huge difference, I'm mostly just noting it here and don't think it's a major issue.

The rise in PMC reflected power has definitely slowed down, and has even dropped noticeably in the past day or so by almost 0.5W.

The operator team has been noticing that we are dropping out of observing for the PMC PZT to relock (80368, 80214, 80206...).

There's already a PZT_checker() in SQZ_MANGER at FDS_READY_IFO and FIS_READY_IFO to check the OPO and SHG PZTs are not at their end of their range (OPO PZT re-locks if not between 50-110V and SHG PZT is 15-85V). If they are, it requests them to unlock and relock. This is to force them into a better place before we go into observing. 

I've added PMC to the PZT_checker, will relock if it's outside of 15-85V. Full range is 0-100V. SQZ_MANAGER reloaded. Plan to take GRD though DOWN and back to FDS. 

Annulus ion pump failed about 4:04 AM.  Since the annulus volume is shared by HAM1 and HAM2, the other pump is actively working on the system, noted on the attached trend plot.

System will be evaluated as soon as posible and determine if the pump or controller need replacing.

I tried Elenna's FM6 from 80287, this made the PRCL coupled noise worse, see first attached plot. 

Then Ryan turned off CAL lines and we retook to preshaping (PRCLFF_excitation_ETMYpum.xml) and PRCL injection (PRCL_excitation.xml) templates.  I took the PRCL_excitation.xml injection with the PRCL FF off and increased amplitude from 0.02 to 0.05 to increase coherence over 50Hz. Exported as prclff_coherence/tf.txt, and prcl_coherence/tf_FFoff.txt. All in /opt/rtcds/userapps/release/lsc/h1/scripts/feedforward

Mon Sep 30 08:11:07 2024 INFO: Fill completed in 11min 3secs

Jordan confirmed a good fill curbside.

Because of cold outside temps (8C, 46F) the TCs only just cleared the -130C trip. I have increased the trip temps to -110C, the early-winter setting.

I don't consider this a full investigative report into why we've been having these FSS_OSCILLATION tagged locklosses, but here are some of my quick initial findings:

• FSS_OSCILLATION tags are just glitches over the tag threshold in the lockloss tool that happen with high frequency at a lockloss; not actual oscillations
• When glitches happen, drive to the FSS EOM (H1:PSL-FSS_PC_MON_OUTPUT) rises. Frequent glitches cause the drive to keep rising (see 7min screenshot)
• Glitches are (probably) too fast to be responses of suspensions moving and changing cavity length
  • SUS not seen moving during these times
• Glitches happen while locked, although usually with lower frequency (see screenshot)
• Sometimes after lockloss, glitches can persist and cause actual oscillations, delaying IMC (and IFO) relocking time as the FSS is not ready, see screenshot from last week
• Non FSS_OSCILLATION tagged lockloss example: see screenshot

Please feel free to add comments of anything else anyone finds.

TITLE: 09/30 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.13 μm/s
QUICK SUMMARY: H1 has been locked and observing for almost 4 hours. One lockloss overnight, which doesn't have an obvious cause but looks to have a sizeable ETMX glitch. Commissioning time is scheduled today from 15:30 to 18:30 UTC.

• Wind and microseism low
• All other systems nominal

Lockloss @ 09/30 04:54UTC

We went out of Observing at 04:53:56, and then lost lock four seconds later at 04:54:01.