H1 was left in a planned IDLE state overnight due to extreme weather conditions.

Environmental Status:

1) Microseism is well above the 95th percentile

• Signal was so hight it was not even touching the 95th percentile mark for a good part of the last 24hrs (from 7am-7:30pmPT)
• Since about 7:30pm PT, the high microseism has sloooowly been starting to touch the 95th percentile (this is still high!)

2) Winds have atleast calmed down starting about 3.5hrs ago (2-3am local)

H1 Status:

Since H1 has been down for a long time, I immediately opted to go for an Initial Alignment (605am PT).  Unfortunately, green arms looked bad and way off (very minimal light in both arms).  As I type this alog, Y-arm has shown life via INCREASE FLASHES, but X-Arm is stuck in ENABLE WFS.  But my computer is slow, so I'm going to reboot & relog into NoMachine.

H1 Status Update (645am Local):

• Y-arm did finally lock up after some INCREASE FLASHES!  I'm guessing around 630amlocal (a guess because it is hard to scroll up on Guardian logs with my computer).
  • It made it to INITIAL ALIGNMENT OFFLOADED.  YAY.
• BUT X-arm has been stuck in ENABLE WFS.
  • I want to atleast get X-arm locked---"baby steps"
• OK, rebooting.

TITLE: 01/10 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Microseism
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 11mph Gusts, 10mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.78 μm/s
QUICK SUMMARY: Corey has been getting green arms up and we will continue to try locking. Wind is now low but useism is still high, although trending down.

TITLE: 01/10 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Microseism
INCOMING OPERATOR: Corey
SHIFT SUMMARY:

Tonight was a wash due to elevated secondary microseism and high winds that have started picking up again.

There have been intermittent MX temp alerts for the 202D channel, and trending it does show that there has been quite a swing in temperature throughout the night. I did see that there was a temperature related repair done at MX earlier today for a low temp alarm, so I'm not sure if this behaviour is expected, but Tagging FMCS just to be thorough
LOG:

No log for this shift.

TITLE: 01/10 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Microseism
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 22mph Gusts, 17mph 5min avg
    Primary useism: 0.07 μm/s
    Secondary useism: 1.01 μm/s
QUICK SUMMARY:

- H1 is down due to high microseism and wind and will be for the forseable future - but will monitor in case it goes down and we can try relocking

- DMs/CDS ok

H1 is still down due to seismic motion. Wind has been on the decline (now peaking at 30 mph), but secondary microseism still has a ~2-3 um/s velocity, which is way too high to relock the detector.

I ran the vent/purge air system for 4 hours today, this was the first time the compressor unit was tested since its recent service, service report aLOG 75055.  The results are that the pressure is good, and the dryer system was able to produce a dew point that was measured before the pressure regulator at -45.0 degrees C.  The Kobelco compressor was inspected before and after today's test and no issues or leaks were encountered.

While performing a test sometime ago at the X-End purge air system the fan for the aftercooler was found to be faulty, report in aLOG entry 74833, aftercooler fan was fixed, report on aLOG 74989, and today finally got a chance to run and test the dew point for this unit.  The dew point was taken at the point of use by the purge/vent valve and read -49.3 degrees C.  No other issues noted.

Functionality test was done on the corner station turbo pumps, see notes below:

Output mode cleaner tube turbo station;
     Scroll pump hours: 5566.7
     Turbo pump hours: 5626
     Crash bearing life is at 100%

X beam manifold turbo station;
     Scroll pump hours: 787.3
     Turbo pump hours: 790
     Crash bearing life is at 100%

Y beam manifold turbo station;
     Scroll pump hours: 1882.2
     Turbo pump hours: 607
     Crash bearing life is at 100%

FAMIS tasks 23526, 23598and 23646.

Vicky, Camilla. Retaking OPO PZT modemattching scan from 66527 and 62691.

Set up: SQZ_MANAGER DOWN then NO_SQUEEZING, SQZ_FC to FC_MISALIGNED , SQZ_OPO_LR to DOWN, "! Toggle Seed/CLF" to let seed though, block CLF and block green pump. We turned up SEED power to 5mW, the polarization isn't good with 0.4mW rejected in HAM7 (but would need to go on table to adjust this).

Scanned OPO PZT1 with Sawtooth 400s period, plot attached for SEED.

Then reverted back to CLF, blocked CLF and looked at scan in green, decreased pump power from 22mW to 2.2mW using waveplate and H1:SQZ-OPO_ISS_DRIVEPOINT. Scan in plot attached.

We had a power glitch which caused light to flicker at work and at my home on the other side of Kennewick. The only thing we could find in CDS was a single DAQ CRC error from h1susey to DC1 (DC0's data was not impacted).

There were no IPC errors.

I have cleared the CRC error and emailed LDAS to use FW0's frames when frame mismatches are seen at this time.

Dave, Jonathan, and Camilla,

Camilla noted that the SQZT7 camera had died and asked us to power cycle it.  We found the config for the SQZT7 camera which identified it as h1cam19.  When we went to cycle the port on the lvea-aux switch we found that h1cam20 went down.  The port labels were wrong.  After double checking mac addresses on the switch with arp entries for the camera we confirmed the correct port and cycled h1cam19.  We have updated the port labels to reflect where h1cam19 and h1cam20 actually are plugged in.

TITLE: 01/09 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Wind
INCOMING OPERATOR: Austin
SHIFT SUMMARY: The IFO has been down for 15 hours due to high wind, high useism, and a maintenance period. The forcast shows the wind calming down late tonight, so we'll see how it goes for us!
LOG:

Joe Areeda has completed a 1-week long run of HVeto to help track down recurring issues in the detector. This run covers from Jan 1 0:00 UTC - Jan 8 0:00 UTC. The full results can be found here: 

https://ldas-jobs.ligo-wa.caltech.edu/~detchar/hveto/week/240101/

The most significant glitch class that was identified was loud glitches, with the most significant witness H1:PEM-EX_VMON_ETMX_ESDPOWER48_DQ.

Jim W, TJ S

The SEI_ENV node will now automatically handle USEISM and USEISM_EARTHQUAKE state transitions based on environment conditions. Users will now request the AUTOMATIC state, and the node should determine where to go from there. This AUTOMATIC state will only be the request, it should never stay in this state for any length of time. Normal earthquake transitions will occur, and maintenance mode is also unaffected.

Jim and I have discussed for some time about how best to handle the useism vs wind conditions. We're going back to a simple method of assuming that we are in a windy/calm state unless the max of H1:ISI-GND_STS_ITMY_Z_BLRMS_100M_300M.mean,m-trend over the last two hours is above 800. We will also subtract out any times where the peakmon channel is above 1000 to avoid any bleed into this band. It's possible that we might look at the slopes of some type of linear regression fit and compare that over some length of time and then determine if it should be switching or not, but we'll start small and get there later.

Camilla, Erik, TJ, Dave:

My original HWS camera control code queried the camera state every minute (camera running or stopped waiting for an external trigger). We found that the HWS servers seemed to be unstable when this code was running over the holiday break. We suspected a possible race condition between the camera control code and the HWS frame grabber. To test this, we stopped the camera control code late last week, and have had no server issues since.

Today, on Camilla's request, I have modified the code to only query the camera status at code startup, and after the camera has been turned on/off (as verification). This means the new code will only send commands to the camera when H1 changes its lock state.

[Measurements attached]

FAMIS LINK:  25973

BSC CPS:  Received following from CPS script terminal output:

• ITMX_ST2_CPSINF_H1 high freq noise is high!

NOTE:  If one was to follow the above channel as an example, it would seem several other BSCs had CPS' with spectra similarly high by eye:

• ITMx ST2 V1
• ITMx ST1 V1
• ITMy ST1 V2

HAM CPS:  Looks good.

Maintenance activities have wrapped up, but the wind is still gusting in the 40s mph and sometimes above 60mph, and the useism continues to grow. We will hold off locking until the environment calms down a bit.

State of H1: Observing at 159Mpc

Very quiet shift with H1 observing the entire time except at 03:25 UTC when SQZ unlocked (SQZ_OPO_LR Guardian reported "PZT voltage limits exceeded"). Guardians were able to bring everything back automatically and observing was resumed within 2 minutes. BNS range improved by 5-6Mpc after this event.