TITLE: 11/25 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 6mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.32 μm/s
QUICK SUMMARY:

IFO is in NLN and OBSERVING as of 17:10 UTC (~7 hr lock)

If L1 goes down, I was told I can drop out of OBSERVING and tune SQZ, which has been having some issues today.

This morning there was a range drop on H1 (163Mpc down to about 151Mpc, see attachment#1).  Was working on trying to figure out how to run the Range Check measurements, but while chatting with Vicky on Teamspeak, she reminded me about the daily CP1 Fill can affect range (see attachment #2 which is plot from Dave's alog)  ....and the effect certainly lines up! (Also see Oli's alog from Sept here.)  The time in question is 1802-1812utc (1002-1012amPT).  I will not share the Low-Range-Plots I took for 1810utc since CP1 Fill is most likely the culprit.

However, a note about the range is that it has not really returned to 163Mpc---it's hovered at 157Mpc post-CP1-Fill for the last 4+hrs.

So I ran another Low Range DTT for about an hour ago (2117utc/1317PT).

• ASC:  Can see noisier CHARD_Y & CHARD_P (attachment #3)
• LSC:  MICH, PRCL, & SRCL are noisier at various frequencies (attachment #4)
• IMC WFS:  There are some noisy IMC WFS B pit & yaw peaks (attachment #5)

Sun Nov 24 10:10:08 2024 INFO: Fill completed in 10min 4secs

TCs only just went below -90C trip, so I have increased the trip to -80C for tomorrow's fill.

TCB started at 0C, hence the additional decades in the log plot.

H1 is now back to OBSERVING and it was painless--for the most part.

• H1 went down just before the shift, but it was struggling with green arms (several cycles of INCREASE FLASHES didn't help). 
• Ultimately went for an Initial Alignment (where green arms then had no problem locking surprisingly & rest of alignment was easy)
• For locking, green arms were quick, but DRMI would not lock even right after an alignment (flashes were good, too!).  Took to PRMI and flashes were also nice, but no locking.  Since I couldn't help it, I tweaked the BS in +pitch and then PRMI locked, followed quickly by DRMI and then all the way to NLN!
• In the background, Vicky did touch up for the Squeezer and mentioned there may be SDF diffs for CS_SQZ, but she must have also taken care of that, too.

Had two separate VACSTAT glitches overnight (plots attached)

1. BSC3:  1209utc (409amPT) for about 2-seconds.
2. EX:  1347utc (547amPT) for just over 1-second.

I'm not sure on how to run a reset (toggling the DISABLED/ENABLED removed red status for BSC3, but it changed to a purple color, so I'm guessing a restart for vacstat_ioc.service will be needed per alog); I sent a text to Dave.

TITLE: 11/24 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.30 μm/s
QUICK SUMMARY:

H1 had an almost 16hr lock with the recent lockloss (having some SQZ issues due to the ISS), but NO IMC or FSS tags (link).  H1 has been having troubles with green arms (with repeated INCREASE FLASHES seen yesterday), so starting an initial alignment.

There is a RED VACstat box on the CDS Overview.  It corresponds to:  1 glitch detected and "multiple" state--which I'm assuming is because it sees a glitch at LVEA's BSC3 and EX (see attached).

Environmentally, microseism is between the 50th -95th percentile and winds are low.

The SQZ OPO is struggling to stay locked. We've dropped Observing 7x so far in the last hour. So far it has been able to recover itself, but now it seems to be struggling. If it can't recover itself soon, I'll be calling for help.

On the bright side, H1 has been locked for over 13 hours.

TITLE: 11/24 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
INCOMING OPERATOR: TJ

SHIFT SUMMARY:

IFO is in NLN and OBSERVING as of 23:29 UTC

It has been a very quiet shift with no operator intervension whatsoever. We've been locked and OBSERVING for about 6hrs and a half.

We did drop out of OBSERVING from 05:26 UTC to 05:31 UTC due to the SQZ FC unlocking. However, guardian managed to automatically relock SQZ and get back into OBSERVING.

LOG:

None

TITLE: 11/23 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 161Mpc
INCOMING OPERATOR: None
SHIFT SUMMARY:

It has been a shift with a return to decent locking with H1 unlocked ~2.5hrs for the shift.  Saturday Calibration was run (coordinated with LLO).  Overall locking was fairly easy although the ALS took a bit of time (not bad), and DRMI locking was a little tough and needed PRMI/CHECK_MICH_FRINGES.  But after that locking has been automated.
LOG:

• 1633 Lockloss (after 5hr55min lock)
• Locking Notes:
  • Green arms:  x-arm looked off in pitch and mostly improved via TMSx in +pit, but then let INCREASE FLASHES run for both arms.
    • ALSy would have its alignment driven off, so quickly took down and tweaked up mainly via tmsy (still not great, but made it)
  • DRMI:  Had to go to PRMI.  Still looked off, so touched PRM and then BS in pitch (due to AS flashes) & it locked.  During ASC offload, AS camera went from pitch misalignment to yaw misalignment on the camera and it stuck with that as ASC offloaded.  For DRMI, eventually locked after 4+min, but....
    • 1702 DRMI Lockloss (non-DOWN)
    • 1757 Back to NLN
• 1921 Incoming M5.9 Fiji EQ alert---No issues riding through it.
• 2036-2037 Accidental Drop from OBSERVING due to Operator Error
  • For the next lock, there is currently an ISC_LOCK notification saying, "ALS_XARM:  STOLEN by USER"
• 2100-2132 Calibration
• 2221 Lockloss (after a 4hr24min lock)  
  • ALS locking once again was not smooth.  Required several rounds of INCREASE FLASHES.  And even after that when the arms would lock, they would have noticeable oscillations (for the y-arm the powers had a 5sec period oscillation which would cause a lockloss)  But ISC LOCK eventually moved on.
  • DRMI had flashes, but similar to last lock it wasn't quite there.  I took H1 straight to CHECK MICH FRINGES after a few minutes, and rest of ISC_LOCK was automated.
  • 2329 OBSERVING
• 2349 PI24 begins ringing up & was damped down within a couple minutes.

TITLE: 11/24 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 8mph Gusts, 3mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.25 μm/s
QUICK SUMMARY:

IFO is in NLN and OBSERVING as of 23:29 UTC

IFO has been behaving following the NPRO swap swap that took place Thurs and Fri.

Had to delay this measurement until 1pm locally due to a lockloss in the morning (coordinated with LLO [JoeH] to drop both H1 & L1 at the same time).

For this calibration, ran a non-standard measurement in that the simulines measurement was one Louis Dartez specifically requested be run for H1 (see below).

Measurement NOTES:

• Following instructions (link).....EXCEPT:  For simulines measurement run this file per Louis D.'s request:
  • " gpstime;python /ligo/groups/cal/src/simulines/simulines/simuLines.py -i /ligo/groups/cal/H1/simulines_settings/newDARM_20231221/settings_h1_20241005_lowerPcal_higherPUM.ini;gpstime "
• H1 at NLN for for over ~3hrs
• Calibration_Monitor medm screenshot is attached
• 2100 - 2132  Out of Observing, ISC LOCK to NLN_CAL_MEAS & Observatory Mode to CALIBRATION
• 2100 - 2106  Broadband measurement run
  • Measurement at:  /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/
• 2106 - 2129  Simullines measurement
  • gps START time:  1416431186.370596
  • gps STOP time: 1416432611.142583
  • Files writtten to subfolders here:  /ligo/groups/cal/H1/measurements

20:36:51- 20:37:40 Drop from OBSERVING

This was purely accidental.  I had too many windows open on my Desktop, and was positioning a browser with GWIstat on it (so I could watch it during the next drop from Observing in a few minutes for the CALIBRATION measurement), BUT my fat fingers or bad eyes had my mouse accidentally click the ALS_XARM All-Guardian window's OFFLOAD_ETM_TMS_WFS state!

Since the arm is SHUTTERED, I don't think it did anything to ALSx (see attached LOG screenshot). 

Immediately re-selected SHUTTERED, and returned the NODE to MANAGED & then H1 went back to OBSERVING.

Sat Nov 23 10:09:56 2024 INFO: Fill completed in 9min 53secs

Running with new trip temps of -90C, TCmins today -108C,-106C.

For this 2nd lock post-recent-NPRO-swap, H1's lockloss did NOT have an IMC or FSS tag:  link

That's 2 for 2 so far!

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

H1's been locked 5hrs.  After RyanS's 1st Observing lock (which was about 1hr), the next (& current) lock was fully automated (w/ CHECK MICH FRINGES + PRMI).

Environmentally, microseism had a bump up about 12hrs ago, but has been trending down slowly since.  Winds are almost nonexistant.  There was a light rain on the drive in.

It is Saturday, so I am assuming a calibration is planned this morning for 1930utc (1130amPT).

H1 is back to observing at 161Mpc as of 08:34 UTC following a two-day NPRO swap.

Reached low noise at 08:21 UTC but couldn't start observing due to several outstanding SDF diffs. I made my best guess for some of these, so I encourage the appropriate people check on these changes and make updates as necessary. The models in question are:

• susetmx - Accepted L3 lock bias T-ramp, changed by Sheila (alog81430)
• isiitmx - Accepted ST2 blend "supersens" filter settings, I believe related to some testing done today (no alog)
• sysexisc and syseyisc - Accepted fiber locking temp control setting, possibly related to new laser frequencies (alog81425)
• hpipumpctrl - Reverted remote control mode from manual to auto; not sure if this makes a functional difference (no alog)