VACSTAT detected a vacuum glitch at 03:00:24 this morning originating with PT427 (EY beam tube ion pump station, about 1000 feet from EY). The vacuum pressure rapidly increased from 1.4e-09 to 1.4e-07 Torr. It then rapidly pumped back down to nominal in 8 seconds. The glitch was detected soon afterwards by all of the gauges in EY. They only increased  from around 1.0e-09 to 2.0e-09 and they took around 25 minutes to pump down.

The glitch was seen at MY as a much reduced amplitude about 6 minutes after the event.

H1 was not locked at the time.

TITLE: 11/13 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Microseism
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 3mph Gusts, 0mph 3min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 1.22 μm/s 
QUICK SUMMARY:

Currently in DOWN due to excessively high secondary microseism. We're supposed to have calibration measurements and commissioning today. I'll try for a bit to get us back up, but I doubt we'll get past DRMI since it's worse now than it was last night for Ryan or TJ

The useism continues to grow. I'll keep the IFO in down and see where things are at again in a few hours.

TITLE: 11/13 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Microseism
INCOMING OPERATOR: TJ
SHIFT SUMMARY: H1 was happily observing until mid-shift when the microseism just got too high and caused a lockloss. Haven't been able to make it past DRMI since then due to the ground motion. I'm leaving H1 in 'DOWN' since it's not having any success, but TJ says he'll check on things overnight.
LOG:

• 02:44 - Lockloss - alog88081

Lockloss @ 02:44 UTC - link to lockloss tool

Possibly caused by ground motion, as everything looked to be moving quite a lot at the time, and the secondary microseism band has been rising this evening. Environment plots on the lockloss tool show a quick increase in motion at the time of the lockloss also.

TITLE: 11/13 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Observing at 140 Mpc and have been Locked for over 16.5 hours. One short drop out of Observing due to the squeezer dropping out, but that relocked automatically and we're been Observing ever since. GRB-Short E617667 came in today at 21:29 UTC
LOG:

15:30UTC Observing and Locked for over 7.5 hours
    15:52 Out of Observing due to SQZ unlock
    15:56 Back into Observing
    21:29 GRB-Short E617667

TITLE: 11/13 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 5mph Gusts, 3mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.56 μm/s 
QUICK SUMMARY: H1 has been locked for 16 hours and observing the whole day.

• Wind low, microseism on the rise
• All other systems nominal

Wed Nov 12 10:08:17 2025 INFO: Fill completed in 8min 13secs

Gerardo confirmed a good fill curbside.

Closes FAMIS#27534, last checked 87787

I was supposed to do this last week but I was out, so doing it now. Last time it was done was 10/28, so this is comparing to measurements from two weeks ago.

Nothing of note, everything looks very similar to how it looked a couple weeks ago.

TITLE: 11/12 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 1mph 3min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.37 μm/s 
QUICK SUMMARY:

Observing at 148 Mpc and have been Locked for over 7.5 hours. Currently in a standdown due to Superevent S251112cm that came in at 11/12 15:19 UTC

TITLE: 11/12 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: A completely uneventful shift with H1 observing throughout. Now been locked for almost 7 hours.

As per WP 12876 I updated the run number server with a new version to allow more testing of the new frame writer (h1daqfw2), without allowing it to modify external state in CDS.

The run number server tracks channel list configuration changes in the frames.  The basic idea is the the frame writers create a checksum/hash of the channel list, send it to the run number server and get a run number to include in the frame.  This is then used by the nds1 server to optimize multi-frame queries (if it knows the configuration hasn't changed some of the structures can be re-used between frames (this has been measured at about a 30% speed-up)).

This update added a new port/interface that the server listens on.  It behaves a little different, it will only return the current run number (or 0 if the hash doesn't match) and will not increment the global state, so it is safe to have a test system use.

Now the new frame writer can automatically query the run number server to get the correct value to put in the frame (previously we had been setting it via a epics variable).  One step closer to the new frame writer being in production.

FAMIS 28431, last checked in alog87986

New data points for all quads this week, measurement trends attached.

TITLE: 11/12 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Currently Observing at 150 Mpc and have been Locked for just over an hour. Maintenance day was pretty light, but on the way back up there was some testing done with using the ETMY ESD (88065), so it took us a bit longer to get back to Observing. Besides that, getting back up wasn't bad at all.
LOG:

15:30UTC Locked and Out of Observing due to magnetic injections
15:40 Back to Observing
15:45 Out of Observing due to SUS charge measurements
16:01 Back into Observing after SUS charge measurements finished
16:01 Out of Observing to change the OM2 setpoint and unlock the IFO
16:03 I unlocked the IFO for maintenance

19:58 Started relocking
    - initial alignment
    - lockloss from LOWNOISE_COIL_DRIVERS due to commissioning
23:17 NOMINAL_LOW_NOISE
    23:28 Observing                                   

TITLE: 11/12 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 8mph Gusts, 5mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.26 μm/s 
QUICK SUMMARY: H1 has been locked for about an hour following Tuesday maintenance day.

• Wind low, microseism steady below 90th percentile
• All other systems nominal

Last week (87801) Jeff took a bunch of transfer function measurements for PRM for the PRM L, P, and Y estimators. There were some he wasn't able to take:

- H1ISIHAM2 to H1SUSPRM M1 for all dofs with DAMP L, P, and Y all with 20% gain

- H1ISIHAM2 to H1SUSPRM M1 for all dofs with DAMP Y at 20% gain

- H1SUSPRM M1 to M1 for V, R, P, Y with DAMP Y at 20% gain

Today I was able to get the first two bullet points done

Measurements:

First, I made sure the SUSPOINT matrix had the correct values for driving PRM, which it did. 

First set (L P Y DAMP gain at 20%):

L, P and Y DAMP gains were set to 20% of their nominal values, so they were set to -0.1, and T, V, and R were left at their nominal -0.5 gain values. 

Measurements can be found in 

/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/PRM/Common/Data/2025-11-04_1800_H1ISIHAM2_ST1_PRMSusPoint_M1LPYDampingGain0p1_WhiteNoise_*_0p02to50Hz.xml r12766

Second set (Y DAMP gain at 20%):

After those measurements were taken, I set the L and P DAMP gains back to their nominal values of -0.5 and took another set of SUSPOINT measurements with only the Y gain at 20%.

Those measurements can be found in 

/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/PRM/Common/Data/2025-11-04_1930_H1ISIHAM2_ST1_PRMSusPoint_M1YawDampingGain0p1_WhiteNoise_*_0p02to50Hz.xml r12767

I ran out of time and wasn't able to finish the four M1 to M1 dofs that were left for the reduced Y damping, so we'll have to get those next week.

I also wasn't able to get in any measurements for SRM, but that's okay since we're not in a rush.

WP12274

FAMIS28946

We rebooted the h1guardian1 machine today for 3 things:

1. Point the machine back at nds0 as the primary nds server
   • I noticed the other day that the guardian was still defining the chosen nds server as nds1 primary and nds0 as secondary. I'm not entirely sure when this was changed, but maybe 2 years ago (alog66834).
   • This was done by changing the NDSSERVER definition in the /etc/guardian/local-env file
2. Relieve any stale processes that might latch the gps leap second data.
3. Quarterly machine reboot FAMIS task

All 168 nodes came back up and Erik confirmed that nds0 was seeing the traffic after the machine reboot.