TITLE: 04/08 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 12mph Gusts, 10mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.20 μm/s
QUICK SUMMARY:
Eric, Sheila, Jennie, Naoki, Camilla
Aiming to repeat 68814 O4a FIS SQZ, SCRL offset data set. Nominal H1:LSC-SRCL1_OFFSET = -175, previously looked at in 74373.
Using data from our PSAMS scan 76986, we're set ZM4 to 8.8V (175 offset), leaving ZM5 with -0/7V (100 offset). Reran alignment scripts following 76986. Accepted PSAMs sdf, and alignment sliders.
For FIS took SQZ_MANGER to AUTO to stop ISC_LOCK bringing it to FDS.
PSAMs at 8.8/-0.7
Data with different angles (+/-10deg from SQZ and ASQZ, and +/- midsqz aimed to match no SQZ level) with SRCL1_OFFSET -175. Plot attached.
Data with different angles (+/-10deg from SQZ and ASQZ) with SRCL1_OFFSET -275.
Additional plots for data above:
Note: As a sanity check, we took another NoSQZ trace at H1:LSC-SRCL1_OFFSET = -= -425 and saw that it looked idential to NoSQZ at H1:LSC-SRCL1_OFFSET = -175.
After looking at this scan, we were wondering if H1:LSC-SRCL1_OFFSET = -275 might be a more optimal operating point than H1:LSC-SRCL1_OFFSET = -175. We decided to do a few more FIS measurements at the two candidate operating points:
After rethermalizing, we plan to look at FDS at H1:LSC-SRCL1_OFFSET = -275 and perhaps tweak the filter cavity a bit to see if this SRCL detuning is better or worse in terms of range.
An alternate version of one of the plot from the original post. A few intetrmediate traces are removed and replaced w reference FDS and No SQZ traces.
Sheila, Jennie W
Sheila and I changed H1:ASC-CAM_PIT1_OFFSET down and went through a point which increased the build-ups in the arms.
She has added this camera offset to guardian.
CAM1 is the servo which moves the PRM to keep the spot constant on the beamsplitter.
See Sheila's pic showing where the best offset is.
We are planning to optimise the A2L gains for each ITM and ETM after this.
Mon Apr 08 10:08:37 2024 INFO: Fill completed in 8min 34secs
Jordan confirmed a good fill curbside.
FAMIS 20023
The PSL was taken down 6 days ago for a Beckhoff update (alog76879), which is seen on several trends.
After that, the PMC seems to have locked with lower transmission by almost 1W.
TITLE: 04/08 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 4mph Gusts, 2mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.20 μm/s
QUICK SUMMARY: H1 has been locked and observing for 20 hours (since 19:02 UTC yesterday).
TITLE: 04/08 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: We stayed locked the whole shift, about 11 hours as off 07:00UTC. In observing since 19:02UTC
ISC_LOCK has flashed "ISS DIFF power is low a few times"
I've seen the MC1/3 camera flash blue a few times
The lock clock on NUC28 is incorrect
LOG:
No log
STATE of H1: Observing at 153Mpc
We've been locked for ~7 hours
TITLE: 04/07 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 9mph Gusts, 6mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.17 μm/s
QUICK SUMMARY:
TITLE: 04/07 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Mostly quiet day with just one lockloss and a fully automated relock. The network has been down all day and came back at 22:48 UTC.
LOG:
No log for this shift.
I restarted the lock_loss_alerting system at 19:59, it had not been running correctly following the network outage.
Lockloss @ 17:52 UTC - no obvious cause. There was a small spike in the EQ band at EX around that time, but I don't expect something that small would cause a lockloss.
H1 back to observing at 19:02 UTC.
Sun Apr 07 10:08:32 2024 Fill completed in 8min 29secs
Dave confirmed a good fill curbside.
TITLE: 04/07 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 3mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.15 μm/s
QUICK SUMMARY:
Late entry while alog was down. All systems nominal.
A test alog to verify local backup authentication is working
The spectra of CS_ACC_LVEAFLOOR_YCRYO_Z, CS_ACC_HAM3_PR2_Y are much lower than the other accelerometer channles.
(i) The channel CS_ACC_LVEAFLOOR_YCRYO_Z has been like that since March 12.
(ii) The channel CS_ACC_HAM3_PR2_Y has been like that since Jan 30.
It seems they are either disconnected or having a lose connection.
TITLE: 04/07 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: Currently Observing and have been Locked for 3 hours. Lockloss earlier in the evening needed me to adjust ALSY and move the beamsplitter for MICH/PRMI/DRMI but we went up quickly after that.
LOG:
23:00UTC Detector Observing and Locked for 7.5 hours
02:47 Lockloss
- ALSY had really high flashes but was struggling to catch until I bumped the flashes up by ~0.02.
- We ended up going through CHECK_MICH_FRINGES but I was able to get us aligned enough to go through DRMI without needing to do an initial alignment - we'll definitely need to run an initial alignment next time
03:54 NOMINAL_LOW_NOISE
03:56 Observing
Lockloss 04/07 02:47UTC from unknown cause
Into Observing at 23:06UTC