TITLE: 10/12 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 2mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.38 μm/s
QUICK SUMMARY:

• We've been locked for 17:22!, in observing sincxe 12:17 UTC
• Secondary microseism is rising quicky over the past 12 hours
• The range looks like it has been trending down this morning, high freq SQZ doesn't look good again

TITLE: 10/12 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Very quiet shift tonight; H1 was locked and observing for the duration with the current lock stretch up to 8 hours. One high profile GW candidate and a couple small earthquakes came through, but not much else to report.

• 23:38 - S241011k

After finding that the source of the broad 60 Hz shoulders in L1 appears to be a problem with line subtraction, as reported in LLO alog 773549, we have checked for possible related issues in H1. We have found that unlike in L1, the broad shoulders appear after October 1st instead of after September 17th as can be seen by checking at L1:GDS-CALIB_STRAIN vs L1:GDS-CALIB_STRAIN_NOLINES vs L1:GDS-CALIB_STRAIN_CLEAN at different points in time during these dates, where the shoulders appear in NOLINES and CLEAN. It would also appear like before September 17th the substraction was not ideal either, since there are still some small shoulders
September 17:


September 26:


October 1st:


October 2nd:


October 11th:

TITLE: 10/11 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: The FSS transmitted power has been dropping the past few (~4?) days, TPD notification has been flashing on OPS_OVERVIEW. 2 locklosses today, automated relocks. We've been locked for 2.5 hours.
LOG:

• Observing 06:36 UTC
• 14:37-39 UTC I adjusted the OPO temp (decreased), increased range by ~5 Mpc
• Lockloss at 16:21 UTC (9:47 lock)
  • ALS_X was badly aligned now
  • 16:43 UTC Decided to do an IA, as I thought it would be faster, XARM took forever to converge, particularly ITMX_P
  • The IMC struggled a little relocking going from INPUT_ALIGN to PRC_ALIGN
  • 18:13 UTC Observing
• 20:14 UTC lockloss (2:02 lock) -  No FSS glitching seen
  • ALS_X took a while to fix its alignment again
  • 21:09 UTC observing, PI 31 started to ring up after 5 minutes
  • 22:15 UTC Tyler let me know that for the next 2-3 hours Richland bomb squad will potentially creating some ground motion (DetChar)

TITLE: 10/11 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 4mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.20 μm/s
QUICK SUMMARY: H1 has been locked and observing for 2 hours. Sounds like it's been a relatively quiet day so far.

• Wind is low, microseism moderately low
• All other systems nominal

We get another false positive VACSTAT alarm for PT132 due to a noise spike. Alarm was raised at 14:29, I cleared it by restarted vacstat_ioc on cdsioc0 at 15:41

The AIP for GV10 is red, system railed about 2 hours ago.  System will be assessed next Tuesday or at the next opportunity, we may need to replace the ion pump for GV10.

FAMIS 26333, last checked in alog80540

All fans within noise range and largely unchanged compared to last check.

No clear reason why, the lockloss website isn't updating "online last update: 237.1 min ago (2024-10-11 09:23:15.156027)"

Fri Oct 11 10:12:04 2024 INFO: Fill completed in 12min 0secs

Gerardo confirmed a good fill curbside. TCs looking much better today.

Lockloss at 16:21 UTC (9:47 lock)

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

• We've been locked for 8 hours, inb Observing since 06:36 UTC
• Secondary microseism is decreasing
• SQZ doesn't look great at high frequency
• Low range check

TITLE: 10/11 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

IFO is LOCKING at FIND_IR. I see IR resonances in both Comm and Diff (screenshot) so I believe guardian will be able to find IR (though it has now taken a few mins).

Super calm shift. Was observing the entire time until at 04:28 UTC, we had a Lockloss (Lockloss alog 80610).

LOG:                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

Lockloss after 9hrs and 45 minutes in NLN.

Cause so far unknown but known not to be the PSL (IMC and ASC lost lock 200ms apart).

Closes FAMIS 26011. Last checked in alog 80261. 

No significant changes from last week.

I added a tag to the locklost tool to tag "IMC" if the IMC looses lock within 50ms of the AS_A channel seeing the lockloss: MR !139. This will work for all future locklosses.

I then ran just the refined time plugin on all NLN locklosses from the emergency break end 2024-08-21 until now in my personal lock loss account. The first lockloss from NLN tagged "IMC" was 2024-09-13 1410300819 (plot here), then got more and more frequent: 2024-09-19, 2024-09-21, then almost every day since the 2024-09-23.

Oli found that we've ben seeing PSL/FSS glitches since before June 80520 (they didn't check before that). The first lockloss tagged FFS_OSCLATION (where FSS_FAST_MON >3 in the 5 seconds before lock loss) was Tuesday September 17th 80366.