TITLE: 07/03 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: 5mph Gusts, 2mph 3min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.07 μm/s
QUICK SUMMARY:
H1 had (3) ~2-hr locks overnight (looks like no wake-up calls for Oli!). H1 is currently locking (just powered up to 25W). Winds stepped down at about 130amPDT (837utc).
Today is Thurs Commissioning from 8am-12pmPDT (15-19utc). H1 won't be thermalized until about 1030-11amPDT, so no calibration...hopefully H1 short locks won't be an issue for calibration where we need H1 thermalized 3hrs. Robert and Sheila will probably start their work
Just want to add a note that all three locks from last night were nearly the exact same length, 1:51, and the locklosses are all tagged with "PI monitor". A ring heater was changed yesterday, 85514, which may have caused this problem.
Additionally, each of the 3 locklosses were from PI28/29 according to VerbalAlarms (the Ring Heater change yesterday was made to address PI24 which riddled our 7hr lock for the last hour before the ultimate lockloss).
While we have been running PIMON live on nuc25, it appears the data from the lockloss hasn't been saved. The newest file in the /ligo/gitcommon/labutils/pimon/locklosses folder is from December 2024. I'm not sure what's going on. We think our problem is an 80 kHz PI, so this would be useful data to have.