I have found new damping settings for ETMY mode01 and ITMY mode05/06, which are given below,
ETMY01
Nominal - FM1+FM6+FM10, Gain = +0.1 (+30deg phase)
New - FM1+FM8+FM10, Gain = +0.1 (+60deg phase)
ITMY 05/06
Nominal - FM5+FM6+FM7+FM10, Gain = +0.02 (-30deg phase)
New - FM5+FM6+FM8+FM10, Gain = +0.01 (+30deg phase)
I have not made any changes in the lscparam file, will check these new settings for a few lock stretches (also let microseism to settle down) before making them final.
Tagging OpsInfo
So once Rahul is happy with the new Violin Mode settings for ETMy 01 & ITMy 05/06, Operators will need to enter his NEW settings by hand (this can be done any time after the DAMP_VIOLINS_FULL_POWER [566] state. For clarity, also attaching screenshots with the filter banks in question circled in light blue:
Mon Nov 25 10:03:17 2024 INFO: Fill completed in 3min 15secs
Problematic fill; TCs started with positive temps, very fast fill, TCmins -91C,-89C. Standard plot plus one offset in time (negative TCs).
This morning we tested the SQZ_MANGER states SCAN_SQZ_ALIGNEMNT and SQZ_SQZANG, the AS42_AS_B_RF41_PIT was at -0.15 and the angle changed ~2deg. The range and squeezing didn't noticeably change so we went back to FREQ_DEP_SQZ which turns back on the SQZ ASC AS42 alignment servo and the ADF sqz angle servo as we've nominally been using them.
This morning, Commissioners wanted suite of calibration measurements run. Broadband measurement was run first with Squeezing, but after this measurment I paused to let them take H1 to No Squeezing (I believe they did this because they didn't want calibration to affect their squeezing work). Then proceeded with the "non-standard" simulines measurement---where,"non-standard" is measurement is what Louis Dartez has specifically been requesting for H1 (see below).
Measurement NOTES:
Took it to NO_SQUEEZING during calibration measurements. Reset the AS42 no-squeezing offsets, and there are very minimal changes (which is great). Accepted new "no-sqz" offsets in SDF.
TITLE: 11/25 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 4mph Gusts, 1mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.48 μm/s
QUICK SUMMARY:
H1 had another 15+hr lock w/ a lockloss overnight (which is most likely due to a M4.6 earthquake 200 miles off the WA coast and NOT IMC or FSS!); TJ needed to assist H1 during his owl shift. H1 currently at just under 5hrs for current lock.
Environmentally, a slight increase in µseism to start touching the 95th percentile, otherwise quiet with no wind. Today it looks like they are pouring concrete at the new Warehouse next to the Staging Building.
Monday morning, but not sure if there is commissioning time on the docket.
SRM M3 had tripped during initial alignment, something that we've seen a few times this week. After untripping it and watching AS AIR in DOWN, I moved it in yaw ~20 urad and then it locked right up.
TITLE: 11/25 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
IFO is in NLN and OBSERVING as of 17:12 UTC 11/24 (~13 hr lock!)
Extremely quiet shift. Intentionally dropped out of OBSERVING twice:
LOG:
None
I tried to change the ADF demod phase to change the SQZ angle servo setpoint (aka: to change the sqz angle). Also tried OPO set temperature, but the original was good already. Between temperature and sqz angle, I think the kHz squeezing improved < 0.5dB, and I saw minimal difference in other SQZ BLRMS and range (see lazy summary pages trends). So the lower range this lock is likely not only the squeezer.
TITLE: 11/24 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Aligning
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY:
Brought H1 back to NLN at the beginning of the shift. Then H1 was jostled around by a CP1 Fill (and then spent the rest of the shift returning to a BNS range it had before CP1). Have been watching L1 to see if they drop out of Observing so we could have Vicky touch up the Squeezer (but they've been locked for ~40hrs).
LOG:
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).
Attached plots show the 30 minutes around the CP1 overfill for Sunday and Saturday. The H1 range shows a correlation with the CP1 discharge line pressure. An increase in line pressure indicates the presence of cold LN2 vapor, and later liquid, in the pipe. The Y manifold accelerometer signal shows correlated motion.
The accelerometer correlation can also be seen on the previous Sunday. This is not seen clearly during the week because the ACC was nore noisy, presumably due to LVEA activity around 10am each day.
Attached shows ACC signal Sun 8th Sep 2024 correlated to the discharge pressure. Back then we were filling at 8am. It doesn't appear that the beam manifold motion has gotten any worse over the past two months during cp1 fills.
The attached plots shows the BNS range around CP1 fill times for the last six CP1 fills (10 AM PDT) when the IFO was also in the locked state. In four cases among these six, we can see BNS range drop during the CP1 fill. In the remaining two it is not clear whether CP1 fill happened or not. We see a spike in H0:VAC-LY_TERM_M17_CHAN2_IN_MA.mean, but we don't see an extened increase in that channel as we see in the other four cases.
The attached plot show the BNS range variations during the CP1 fill times during the first ~10 days of December. We are plotting only those days when the IFO was in observing (H1:GRD-IFO_OK == 1). For these days, the drop in the BNS range during the fill times seem lower than what we saw during November (plot in the above comment). We also see that the fill times are in general less in these ten days compared to what were in November. Maybe longer the fill time, more the drop in the BNS range!? Also looking at these plots and plots from November, it seem the range might be coming back to a lower value after the fill than it's value before the fill.
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.
Had two separate VACSTAT glitches overnight (plots attached)
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.
This morning's VACSTAT false alarm was caused by two sensors randomly glitching within 2 hours of each other (Corner station BSC3 and EX BSC9).
Timeline (all times PST):
04:08 BSC3 PT133_MOD2 has one of its regular glitches, which puts VACSTAT into sensitive mode waiting for a coincident chamber trip.
05:47 BSC9 PT510B has a random glitch which exceeds the lowered delta-P trip level. Alarms are sent to the vacuum team.
08:48 VACSTAT restarted to reset
Attached 5 hour trend shows the BSC3 glitch (top row) and the BSC9 glitch (bottom row) 1hr 38min later.
Attached BSC9 7-day trend show it does occassionally have small glitches, but this morning's was larger and just enough to exceed the lowered delta-P trip level.
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.
Looks like the SQZ sorted itself out out at 1422 and has stayed locked for 15 min so far.
Since IFO was down, I tried to fix this. SHG output power dropped >30% overnight, and ISS ran out of range trying to follow (so not necessarily a pump iss alignment problem). See trends in first attachment.
1) I turned the pico-waveplate before the ISS AOM to sent more power to the fiber (aka reject less green power). This pico worked.
2) Adjusted SHG temperature from 35.95 C --> 35.3 C to optimize output green power, which is a surprisingly big move. See second attachment of trends to optimize temperature. Not sure why the setpoint temperature changed so much, and I wonder if it will change back to "normal" later.
Conservatively, even though 35.3 C was best for SHG green power, I set the SHG TEC setpoint inbetween at 35.5 C, and accepted this in SDF.