17:22 UTC We started comissioning, starting a little late today due to the IFO not being fully locked and thermalized.

Mon Oct 14 10:12:33 2024 INFO: Fill completed in 12min 29secs

Travis confirmed a good fill curbside.

In the past few weeks, a number OPO temperature changes have been made while the detector was in observing mode (per the relevant instructions). These changes have been highly successful at increasing the range, particularly the most recent couple of OPO changes. However, this type of rapid improvement in the spectrum can create challenges when measuring the spectrum of the data in downstream data analysis pipelines (similar to how the sudden turn-on of the line subtraction was problematic). When the OPO adjustment has created significant changes to the spectrum, the time periods during the transition should be CAT1 vetoed (tagging Detchar-request).

As an example of these transitions, I've included a range timeseries and a daily spectrogram with the transition time indicated.  I also have included a before/after spectrum comparison showing the broadband improvement at high frequency.

To mitigate the impact on data analysis pipelines, future transitions should either be made while briefly out of observing or tracked by Detchar for CAT1 vetoes.  

I've wrote a small script to revert ZM sliders after a SCAN_ALIGNMENT is run (SQZ_MANAGER state 105) incase we don't like it. It does a rough search for when this state was last run in the past day (it probably can be reduced but I needed a larger range for testing) using minute trends. From this time it then does a more narrow second trend to get more accurate state boundary times (did this for speed of nds2 calls), then it just takes the slider values of ZM{4,6} from a minute before the most recent SCAN_ALIGNMENT started and caputs them.

You can change the lookback time by changing the "days" and "hours" variables at the top of the script which lives at /opt/rtcds/userapps/release/sqz/h1/scripts/revert_sqz_align.py

Overall the finidings were similar to the previous days, with a few exceptions.
On Monday there was ground motion reported around 7:00.
On Tuesday, there was also earthquake ground motion, and a slight increase in glitch rate around the hours of 1:00-3:00, and at 12:00 and 15:00.
On Wednesday, there were no significant changes to report.
On Thursday, there was rotational wind motion around hours 1-5:00 and glitch rate increase around hours 6:00-8:00. Also there was a decrease in the Detchar Fscan lines to around 400, which was less than previous days.
On Friday, there were no significant changes to report. Fscans lines increased back to the normal range.
On Saturday, there was earthquake motion around 19:00.
On Sunday, there was a slight increase in the lock/strain/sensitivity around 16:00.

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

• Relocking at MOVE_SPOTS, 12:57 UTC lockloss
• Low wind, microseism it just under the 90th percentile but looks static
• 15:30 -> 19:30 UTC commissioning is planned for today

Over the summer, Sam, Robert, and I investigated several peaks in DARM, including one at ~35.4 Hz and a peak that oscillates between 30-40 Hz. The 35.4 Hz peak was found to couple strongly at HAM1 and HAM6 (see alog 79546). Shut-offs of the office area air handler and the main chillers showed that the peak decreases when these systems are shut off, though it doesn't disappear completely. See Figure 1 and Figure 2 with office area air handler shut offs at 19:33:00-19:38:30 and 19:43:00-19:55:00 (alog 79888), and Figure 3 for main chiller shut offs (alog 73941). Note that there is also a fainter peak about 0.2 Hz above the 35.4 Hz peak as seen in Figure 4 but it is unclear if it also decreases when the HVAC is shut off.

The oscillating 30-40 Hz peak tends to be near 40 Hz at the beginning and end of the UTC day and drops to near 30 Hz in the middle of the day as seen in Figure 5. It often appears sinusoidal as seen in Figure 6 but sometimes has a more random appearance as in Figure 7. It is seen in microphones and magnetometers as well, and first appeared at least as early as 6 June 2024. Its source has yet to be identified.

These peaks were dicussed in a presentation at the end of our summer fellowship as well as in a DetChar call, now posted on the DCC: LIGO-G2402140.

TITLE: 10/14 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Pretty quiet evening with just one lockloss followed by an automatic relock. Range has been keeping fairly steady this lock.

• 23:30 - H1 locked for 1.5 hours
• 23:53 - Lockloss - alog80652
• 00:48 - Resumed observing

H1 has been locked and observing for just over 4 hours.

Lockloss @ 23:53 UTC - link to lockloss tool

No obvious cause. Maybe a small ETMX glitch before the lockloss, but otherwise I haven't noticed anything else.

TITLE: 10/13 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: We've been locked for just over 2 hours, 3 locklosses today fairly automated relocks.
LOG: No log.

• 14:06 UTC lockloss
  • I adjusted the OPO temperature while we were relocking as it looked like the range had been slowly degrading again this morning.
  • Ran into SQZ issues, it ended up being from a PMC_PZT voltage checker alog80646. (contacted help)
  • I ran a SCAN_SZQANGLE once we had fixed it as we had been locked for 2 hours at that time.
  • 17:17 UTC Observing, range looks good... Better than the stretch this morning.
• 19:18 UTC Lockloss (4:04 lock)
  • 20:05 UTC MAX_POWER lockloss (IMC tag in lockloss tool) IMC and ASC-AS_A lost lock at the same time
  • 21:27  UTC Observing after damping violins in OMC_WHITENING for 10 minutes and adjusting the OPO temp to fix high freq SQZing

TITLE: 10/13 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.45 μm/s
QUICK SUMMARY: H1 has been locked and observing for 1.5 hours.

• Wind is low, microseism trending down and now just below the 90th percentile
• Planning to check OPO temp once thermalized

Laser Status:
    NPRO output power is 1.829W (nominal ~2W)
    AMP1 output power is 64.44W (nominal ~70W)
    AMP2 output power is 137.5W (nominal 135-140W)
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 3 days, 3 hr 9 minutes
    Reflected power = 24.22W
    Transmitted power = 101.8W
    PowerSum = 126.0W

FSS:
    It has been locked for 0 days 0 hr and 21 min
    TPD[V] = 0.7953V

ISS:
    The diffracted power is around 2.1%
    Last saturation event was 0 days 0 hours and 22 minutes ago

Possible Issues:
    AMP1 power is low
    PMC reflected power is high

EX saturation then lockoss

RyanC, Camilla, Vicky

I noticed that the SQZer wasn't locking from NUC33 this morning when I first adjusted the OPO temperature. The OPO kept dropping when the FC trys to lock IR, there was a SQZ ISS saturated notification on DIAG_MAIN. I looked through the alogs and wikis on this. I investigated the checks that RyanS went through last night in alog80639 to no avail, I also tried setting FC1 & 2 back to their spots from the last time we locked the SQZer using OSEMs which didn't help either. I ended up contacting Camilla, where we:

• tried SQZ_FC guardian step by step, saw the issue was at IR_FOUND which is where we change the FC VCO, at this point OPO was unlocking, but OPO shouldn't be effected by FC VCO.
• We then followed instructions in SQZ wiki for if FC green wound't lock and touched up FC to improve green alignment H1:SQZ-FC_TRANS_C_LF_OUTPUT improved form 75 to 120.
• Still same problem persisted, Camilla didn't understand FC VCO so called Vicky.
• Vicky said it shouldn't be related, check SQZ_MANGER.
• Found that once SQZ_MANGER was paused, there was no issues.
• Tracked down to PMC PZT voltage being high outside of range added in https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=80371. And then SQZ_MANAGER pulled everything DOWN.
• We increased this range to def PMC_PZT_OK(): return 5 < ezca['SQZ-PMC_PZT_VOLTS'] < 95 and everything worked fine. Simular issue to what Ryan Short had in https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=80490
• To do for SQZ team, make this checker / the Beckhoff scan for the PMC PZT smarter

Sun Oct 13 10:12:24 2024 INFO: Fill completed in 12min 21secs

Overall the fill looks good, but the TCs are not showing their normal winter profile and are getting very close to the -200C limit. Friday 11oct2024 plot shown for comparison.

Also TC-B again looks significantly different from TC-A.

TITLE: 10/13 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 5mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.42 μm/s
QUICK SUMMARY:

• We lost lock about 25 minutes ago, we had been locked for almost 9 hour
• Relocking at PRMI
• Secondary microseism is decreasing