https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1382593909 Ground motion was elevated at the time due to an earthquake.
We reaquired NLN at 02:51 after the previous LL, now I'm just waiting on ADS to converge to return to Observing.
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1382578143
Looks like a fast CHARD and DHARD ringup in both P & Y. The LSC signals also saw a fast wiggle right before the LL.
Another LL at CARM_TO_TR, NO IR in arms. It went through find/check IR too quickly and didn't actually find it, I'm going to request FIND_IR and make sure it actually finds it this time.
TITLE: 10/28 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 150MPc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Three locklosses from NLN today. There has been a LVEA temperature excursion which is turning around, plot attached.
LOG:
TITLE: 10/28 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Camilla (DAY)
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 4mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.11 μm/s
QUICK SUMMARY:
In observing at 23:14, the sign change on ITMY mode8's gain (-0.2 -> +0.2) also is working and bringing it down.
Lockloss after being in NLN for 5 minutes. 1382565549. Hadn't yet got into Observing after 20:46UTC lockloss 73799.
Third lockloss of the shift. No obvious reason again, environment, LSC and ASC signals look fine.
LVEA temperatures have a 0.5deg excursion but looks to be turning around, plot attached. The outside temperatures have changed a lot this week and we were seeing smaller excursions on Thursday/Friday. Tagging FMCS.
Can see that LVEA temperature sensor 5A changed 1.7degF and some of the close optics show alignment drifts with this: PR2, MC2, ITMY. Plot attached. This could be the cause of the last two locklosses today.
After being at NLN for 1h30. 1382561229. No obvious reason for lockloss: environment, LSC and ASC signals look fine.
Reached NLN at 21:53UTC and while waiting for camera servos to converge we had a lockloss at 21:58UTC 73800. No issues with SQZ FC locking.
After IFO locked 11h29m. 1382549720 ~6Hz wobble in DARM before lockloss.
After 4 locklosses at LOCKING_ALS (COMM and DIFF beatnotes at -18 and -15), at 18:05UTC I started an initial alinement. IA went smoothly and finished at 18:30UTC. Observing at 19:46UTC.
NLN at 19:14UTC, I let SQZ_MANAGER try for 8 minutes but it kept failing at TRANSISION_IR_LOCKING, as yesterday 73770. Repeated yesterdays "Issues with SQZ FC Guardian" wiki steps and touched FC2 Pitch. Then had trouble with SQZ_FC at ENGAGE_FC_ASC step. When Vicky stepped through the guardian this wasn't an issue and it locked fine, we then had the guardian do it and it locked fine. I touched SQZ OPO temperature and SQZ angle, high frequency SQZ looks bad but we are unsure why.
FM2 DARM2 boost that was tuned on yesterday 73783, 73776 did not come on so I sdf reverted to turn it on. I'll search the alog to find where this needs to be added the ISC_LOCK. Tagging ISC. sdf
This bad high frequency noise was present in the start of most (but not all) of our locks since Tuesday, zoomed out plot. ZM6 alignment shifted Tuesday and is close to saturating. It is also moving a lot at the start of each lock, maybe causing this changing high frequency squeezing. We could repeat Naoki's 73171 offloading.
We can also see in the purple SQZ BLRMS (centered at 4.8kHz) jump at ~ 08:12UTC (1h40 into the lock) the DARM plot shows that the high frequency slowly gets better but at ~ 08:12UTC the noisy region at 4.8kHz and 3kHz suddenly disappears and is replaced by noise at 4kHz (compare purple/yellow traces to red). What would cause this?
Sat Oct 28 10:10:35 2023 INFO: Fill completed in 10min 32secs
TITLE: 10/28 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
OUTGOING OPERATOR: Austin
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 1mph Gusts, 0mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY:
IFO has been locked for 9 hours. Range seems to have dropped in last hour, plot attached, unsure why. Environment and squeezing is fine.
Looking at omicron glitches and DARM (red better range than brown), the range drop appears to be in the 20-300Hz region and could be due to squeezing (attached SQZ BLRMS plot: orange trace 150Hz, yellow trace ~350Hz).
The TCSX laser unlocked this morning at 13:38 UTC 10/28. Before I had a chance to get into NoMachine to check it out, the laser relocked itself again at 13:45 UTC.
This is the first time the CO2X laser has unlocked since the new chiller was installed 73704. On CO2 unlock, the TCS_ITMX_CO2 guardian couldn't find a lock point so stepped the chiller temperature which starts a 5 minute timer before scanning PZT again. Total time down was ~7m30s. This issue has associated FRS#28943. If this happens again we could add a longer timer to IFO_NOTIFY (currently alerts after 3 minutes out of observing) if the CO2s are not nominal.
The PZT has been much noisier since the chiller was swapped 4 days ago, see attached pink trace. Is also noisier than CO2Y.
I activated Jenne's DARM2 boost from LHO:73745 (in FM2) at 10/27/2023 13:25:54. The FM2 change has been saved in SDF. The file that includes this new DARM2 boost filter is at/opt/rtcds/lho/h1/chans/filter_archive/h1omc/H1OMC_1382307261.txt. I've copied it to/ligo/svncommon/CalSVN/aligocalibration/trunk/Common/H1CalFilterArchive/h1omcfor the Cal group. The file has been committed to the SVN. The corresponding repo has been updated on the LHO cluster under the cal account too.
Added this FM2 boost to ISC_LOCK state LOWNOISE_LENGTH_CONTROL, FM2 is now turned on at the same time as DARM2 FM8 is.
This Calibration-affecting change has been recorded in the H1 Record of Real-Time Calibration Pipeline Parameter Changes (DCC T2300297).
In observing at 03:15UTC