TITLE: 11/16 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Quiet day for the most part, aside from two locklosses.
H1 is relocking, currently in FIND_IR.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 16:02 | FAC | Randy | EY | n | Delivery | 16:32 |
| 16:14 | FAC | Tyler/Eric | MY | n | HVAC troubleshoot | 18:07 |
| 23:53 | VAC | Gerardo | FCES | n | Vac checks | Ongoing |
Lockloss @ 23:45 UTC - no immediately obvious cause, but this looks like another one where LSC-DARM_IN1 saw the first activity.
TITLE: 11/16 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan Short
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 8mph Gusts, 6mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.23 μm/s
QUICK SUMMARY:
Back into observing at 01:09UTC.
I noticed earlier this week that two vacuum guage pressures had been temporarily removed from the alarm system in Sep 2022 during a BSC2/HAM6 vent. I have added them back into the alarm configuration and restarted the service.
+<!-- WP10675 remove for vent
<Channel name="H0:VAC-LY_Y1_PT120B_PRESS_TORR" low="1.0e-10" high="2.0e-06" description="VE gauge, PT120B BSC2 CC">
+<!-- WP10675 07Sep2022. Temporarily remove HAM6 Alarms for the duration of the vent.
<Channel name="H0:VAC-LX_Y0_PT110_MOD1_PRESS_TORR" low="1.0e-10" high="5.0e-06" description="HAM6 VAC">
I have added trend buttons to the FMCS Overview MEDM which open MEDM screens showing the most recent 1day, 1week, 1month trend plots.
Attachment shows the Overview and the VEA temperature trends, showing the recent MY drop in temperature.
Did the same for the Vacuum Trends, they can be launched from the Vacuum Overview MEDM using a pull down related display button (located bottom-right of screen).
A follow up to an operator report that the MC3 camera image on the FOM occassionally flashes blue-screen. I can confirm I have seen several flashes today on my gstreamer display running on my nomachine session. Normally we would immediately restart the server process, except h1digivideo1 was actually rebooted late Tuesday morning which appears to have caused the issue.
At the next TOO I will restart the server process as a simple first test. We may then progress to power cycling the camera.
The low temperature in Mid Y this morning was the result of a malfunctioning heater. Both SCRs had burned up so there was no heating control available. I bypassed both SCRs and wired straight from the line voltage fuses. The heat staging required rewiring as it had been wired to bring on all stages of heating with only a single stage heating command.
21 hr 17 min lock. PRG was seen on the nuc30 FOM oscillating and incresing before lock loss. Looking at the standard plots, it looks like an ASC ringup, though I can't tell who was first.
The lockloss tool (1384194867) shows that there was seismic movement in all bands (anthropogenic, earthquake and micorseism) at the time of the lockloss.
Thu Nov 16 10:03:35 2023 INFO: Fill completed in 3min 32secs
Gerardo confirmed this short fill was a good one from curbside.
TITLE: 11/16 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 7mph Gusts, 5mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.26 μm/s
QUICK SUMMARY: Locked for 18.75 hours. MY has a temperature alarm, looks to be acknowledged but I'll contact FAC.
TITLE: 11/16 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: We've been locked for 10:43, the range has dropped by ~5 Mpc over the past 2 hours or so, the wind has also increased over the same time frame but not by too much 5 -->10mph, and the live SQZ DARM trace is below the FDS reference on NUC33. Another quiet night.
STATE of H1: Observing at 160Mpc
Naoki, Sheila
In the AS72 sensing matrix measurement in alog74106, Daniel suggested to increase the whitening gain of AS72 since it could be limited by ADC noise. We checked the whitening filter of AS72 A and B. Both of them have 12dB whitening gain, but one stage whitening is engaged for AS72 A, while two stage whitening is engaged for AS72 B. We decided to engage the 2 stage whitening for AS72 A, which is used in SRC1. The IFO locks without any problem with this additional whitening. We accepted some SDFs as shown in the attached figures. We will try to increase the whitening gain later.
I think the attached plot shows this was a good idea. I have some old data measuring whitening and no whitening on at RF72, but I never posted it because I couldn't figure out the correct RF72 transimpedance. The attached plot shows an estimation of the ADC noise level comparison with the noise spectrum in lock. Naoki and Daniel were kind enough to help me figure out the proper transimpedance for the RF72 (see 37065).
The measurement procedure and calculation procedure is detailed in alog 66734. At the time, RF72 was using 1 stage of whitening with 12 dB whitening gain.
I think it's likely my shot noise calculation here is incorrect. Correcting that calcuation is in progress...
During Tuesday maintenance and IMC_LOCK is OFFLINE, I measured the AS72 dark noise with different whitening setting. The attached figure shows the dark noise of AS72 A Q PIT/YAW, which are used in SRC1. The 2 stage whitening and 12 dB whitening gain are the current nominal setting. In the previous Elenna's measurement, there was a bump around 25 Hz, but there is no bump in today's measurement.
Sheila, Camilla, Naoki
After alog74223, we engaged the SQZ phase dither servo as shown in the first attached figure. After we engaged the dither servo, the error signal (SQZ-PHASE_DITHER_DEMOD_I_OUTPUT) goes to 0 and the SQZ phase (SQZ-CLF_REFL_RF6_PHASE_PHASEDEG) goes to around optimal value.
Detail
First we checked the error signal of dither servo by scanning SQZ phase as shown in the second attached figure. The dither error signal is SQZ-PHASE_DITHER_DEMOD_I_OUTPUT shown in gray. You can see the two zero crossing points where the BLRMS4 (SQZ-DCPD_SUM_RMS4_MON) is minimum and maximum.
Then we made a new state in SQZ_MANAGER guardian named ADJUST_SQZ_ANG to adjust the SQZ phase using dither servo. The servo is engaged with cdu.Servo and it uses the SQZ-PHASE_DITHER_DEMOD_I_OUT16 as readback channel and the SQZ-PHASE-OUTMTRX_1_1 as control channel. We cannot use the SQZ phase (SQZ-CLF_REFL_RF6_PHASE_PHASEDEG) as control channel since it is a discrete number (SQZ-CLF_REFL_RF6_PHASE_DELAYSTEP must be an integer). So we stored the value of the DELAYSTEP in the unused output matrix element (SQZ-PHASE-OUTMTRX_1_1) and used it as control channel. The DELAYSTEP itself is controlled by rounding the value of SQZ-PHASE-OUTMTRX_1_1 to an integer.
Note: Although the SQZ phase dither servo seems to work, the SQZ phase the servo ended up (152.7 deg) is not exactly optimal value (145.47 deg). We needed to adjust the SQZ phase manually to really optimize the SQZ BLRMS.
This morning I took measurements for MICH and SRCL feedforward and exported in .txt files in /lsc/h1/scripts/feedforward. Gabriele changed SRCL in 73662 Oct 20th. MICH last changed 73420 Oct 12th.
I didn't have good luck re-fitting MICH, I made a new filter in FM7 but although it fit 100-200Hz well, I couldn't get the fit to also be good <20Hz. Plot attached - RED TRACE.
I also tried the current FF without 17.7Hz line, FM6, 74139, it alos change the fit of the filter 20-80Hz, wasn't sure if this was better or worse so will discuss with others and we can implement on Friday. Plot attached, RED TRACE.
Strangely, the current MICH FF looked better than it has done recently and didn't appear to change with thermalization. What has changed since last week 74102?!
