Sheila, Camilla.

New SQZ ASC using AS42 signals with feedback to ZM4 and ZM6 tested and implemented.  We still need to watch that this can keep a good SQZ alignment during thermalization. In O4a we used a SQZ ASC with  ZM5/6, we have not had a SQZ ASC for the majority of O4b.

Prep to improve SQZ:

• No squeezing from 15:31:30 to 15:41:30UTC.
• Adjusted OPO temperature following no observing instructions in 80461. Measured NLG to be 12.8. (0.1165/0.0091) following 76542.
• This improved the squeezing from 2.5dB above 300Hz to 3dB at 300Hz and 4.2bD above 1kHz.

Testing ASC from 80373:

• Ran the "reset as42 nosqz" offsets script while in no sqz. SDF accepted.
• Put the input matrices form 80373 into SQZ ASC and checked they were diagonalized correctly by moving ZM4/6 in turn and watching ASC_POZ/ANG input signals. ZM4 pitch wasn't completely diagonalized but that others looked good.
• Reduced ASC_WFS gain from 0.1 to 0.05, cleared histories, set all ASC_POS/ANG gains to 1 and one at a time turned on the inputs. We had some troubleshooting with POS_Y but there was a minus sign inside one of the filter banks we hadn't seen. In this troubleshooting we found the matrix was mostly diagonal so removed the cross-coupling terms for the YAW input matrix.
• Found WFS gain is better with lower WFS gain to 0.01 so we took a factor of 100 for the input matrix and left H1:SQZ-ASC_WFS_GAIN at 0.5. Accepted all in sdf. And edited sqzparams and reloaded SQZ_MANAGERT to turn on SQZ ASC.
• To test, we tried the "offload AS42 ASC" script with the plan to compare the AS42 alignment with the alignment from the guardians scan SQZ alignment. The script didn't work as expected, it's hard-coded to offload ZM45/6 rather than ZM4/6 that we are now using, we should fix this or go back to using ther guardian states. After turning off the ASC and running again to clear histories, this caused a lockloss, probably as ZM6 P moved 60urad in 0.3s. See attached lockloss plot.

starting at 16:48 UTC, we have the IMC locked with the NPRO temperature at 0.3, compared to -0.18 for the last 1.5 years (the medm screen says this is in units of K).  This was a suggestion from the PSL team to see if our problem is that the laser is near mode hopping. 

Mon Oct 07 08:08:32 2024 INFO: Fill completed in 8min 28secs

Jordan confirmed a good fill curbside.

TITLE: 10/07 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 3mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.28 μm/s
QUICK SUMMARY:

H1's currently observing w/ a 3.5hr lock and range at 160Mpc.  useism has slowly been inching up the last 12hrs; winds are calm.

Two locklosses overnight with NO FSS tags.  One was from a Tonga earthquake (which required an automated Initial Alignment).

TITLE: 10/07 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: 1 lockloss, relocking took a little wihle but we've been locked for just over 4 hours now.
LOG: No log.

• 21:31 UTC Observing
• 21:59 UTC Lockloss (28 minute lock), no PSL glitching seen
  • Adjusted the OPO temp following alog80461 as we were locking
  • 22:23 UTC AS_SHUTTERS lockloss, no PSL glitching seen
  • 23:33 UTC MAX_POWER lockloss, no PSL glitching seen
  • 00:29 Damped violins in OMC_WHITENING
  • 00:48 Observing
  • Range check shows same as last time, SRCL, some PRCL and CHARD_Y coherence

Genevieve and Sam identified the sources of many of the peaks that were vibrationally coherent with DARM in the 20 to 40 Hz region (8012 ). We suspected coupling at HAM1 and I tested this recently using local injections and the beating shaker technique.

With local injections at HAM1 using shakers and HEPI, we can produce much larger  signals at the HAM1 table top then at the PSL or HAM2. The coupling site will likely have the same ratio of locally injected peaks to distant equipment peaks in its vibration sensors as the ratio of these peaks in DARM. The figure shows that the ratio of the injected peak at 25 Hz to the Air Handler peak at 26.35 Hz is consistent with coupling at HAM1 but not HAM2 (or any place else – most other potential coupling sites don’t even detect the peak injected locally at HAM1)

The figure also shows that the beats from the beating shakers matched DARM at the HAM1 table top, but could also be consistent with coupling at HAM2, so this technique, as implemented, gave a consistency check but did not discrimate well between HAM1 and 2.

After August’s work, we wanted to check the ITMY compensation plate yaw setting. I did this last week using an input arm shaker injection at 12.6 Hz while sweeping the ITMY compensation plate in yaw, as I had done several times in the past (e.g. 76969, Figure 3).

The figure shows that scattering noise continues to be quite sensitive to the CP yaw on a 20 microradian scale. While re-checks did not previously suggest the need for a change after the initial setting (76969), the figure shows that this time the check suggests a new setting. The original setting, -250,  is now in a coupling peak. I suggest changing it to -325 (see figure).

The second page of the figure shows that the coupling peaks are very repeatable.

TITLE: 10/06 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Aquisition
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 11mph Gusts, 7mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.17 μm/s
QUICK SUMMARY:

• Lost lock after 28 minutes (doesn't look FSS/PSL related), lost it again at CHECK_AS_SHUTTERS on the relock from an earthquake
• Just lost it again at MAX_POWER

TITLE: 10/06 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:

Observing for almost half of the shift.  With one EQ lockloss in the afternoon which we are recovering from now.
LOG:

• 1910 Lockloss (after 4hr lock)
  • Did some OPO temperature touch ups during locking.
• 2159 Lockloss (after 28min lock)
  • This is probably due to south pacific earthquakes

• H1 had an average duty cycle of 69.24% for the week.

• Low and high frequency noise can be seen in the h(t) plots on most days of the week.

• The BNS range did not plot from 9/10 @ 6:00UTC until 9/12 @ 20:00UTC

• The average range can likely be found for the missing sections by plotting it manually (I have not done this, but will if it's helpful)

• Very loud ground motion seen at two different times below: alog_80103 at the end of the day Sunday 9/15.

• FScan Plots appeared everyday, and the most significant change in line count was around 200 from Wednesday to Thursday.

• Hveto: Some channels appeared repeatedly this week, some appeared for the first time in over a month. Example of a common channel of late: H1:LSC-DARM1_IN2_DQ

Link to report here

Smooth sailing this morning with H1 locked most of the time, but it just lost lock after a 4hr lock (managed to make it through which took down L1 30min ago).  Other than that, environmentals are decent.  Off to make lunch.

About Last Night:  737 - 1401utc (1237am-701am PDT)

Only looking at locklosses at ISC LOCK states from 500 and above (i.e. with ASC Full IFO);  a lot of the other locklosses were at early states (and quite a bit have the FSS Oscillation tag)

• 2024-10-06 07:37:40.716797 UTC (@OBSERVE, see attachement 01)
  • No FSS Oscillation tag.  Don't see oscilation in Sheila's template.
  • However IMC loses lock at same time as ASC-AS
• 2024-10-06 10:09:09.306152 UTC (@OBSERVE, see attachement 02)
  • (very similar to above/737utc)
  • No FSS Oscillation tag.  Don't see oscilation in Sheila's template.
  • However IMC loses lock at same time as ASC-AS
• 2024-10-06 11:10:14.523438 UTC (@OBSERVE + FSS OSCILLATION tag, see attachement 03 & 03b (zoom in))
  • FSS Oscillation tag.
  • Also see on Sheila's template that the FSS starts having glitches for 2min before the lockloss
    • AND:  NPRO takes a jump at the same time as the FSS glitches start.
  • IMC loses lock at same time as ASC-AS
• 2024-10-06 14:01:17.718750 UTC (@OBSERVE, see attachement 04)
  • No FSS Oscillation tag.  Don't see oscilation in Sheila's template.
  • However IMC loses lock at same time as ASC-AS

Sun Oct 06 08:09:41 2024 INFO: Fill completed in 9min 37secs

TITLE: 10/06 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 3mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.14 μm/s
QUICK SUMMARY:

H1 currently at ENGAGE ASC (after a lockloss from Observing for a 51min lock).  Environmal conditions about identical to yesterday.  (although there looks to be an EQ about an 1hr ago (close to recent lockloss [but also don't see on 1412258495.71875]...perhaps M5.2 from Vanuatu region).

Additional Note:  The 3hr downtime had one lockloss which happened 10min after getting to NLN and H1 Manager had not taken H1 to Observing which is a bit odd.  After that the next 2hr locking time had lots of Green Arm locklosses (9 in total), but it eventually made it back to Observing.

H1 called for assistance at 08:39 UTC after reaching NLN successfully but being unable to start observing due to an issue with SQZ. I found the issue was that the PMC was consistently locking between 11-12V, and because of the lower bound of 15V in the check recently added to unlock and relock the PMC when outside of a comfortable range (see alog80371), SQZ_MANAGER would repeatedly unlock the PMC once it reached FDS_READY_IFO. Since the PMC seemed happy at this 11-12V point, for now I've changed the lower threshold for the PMC PZT check from 15V to 10V (line 73). SQZ_MANAGER injected squeezing just fine after that, and H1 started observing at 08:55 UTC.

TITLE: 10/06 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: 1 lockloss with an automated relock, we've been locked for a little over an hour.
LOG: No log.

01:45 UTC I adjusted the OPO temperature a 2nd time as the high frequency looked bad on NUC33.

01:53 UTC Superevent S241006k

02:35 UTC lockloss (12:44 lock)

03:45 UTC Observing

02:35 UTC lockloss