Smooth shift (other than initial quick pair of SQZ locklosses) for H1. L1 joined us about 1.75hrs ago.
TITLE: 11/23 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 160Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 4mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.42 μm/s
QUICK SUMMARY:
While getting the hand off from RyanC, H1 dropped from OBSERVING due to the SQZ being unlocked (and then quickly relocked). And a few minutes later, the same thing happened---where the Squeezer relocked on its own.
Will be mindful of:
Environmentally: microseism is still high, but continues it's trend down from yesterday. Winds are calm.
TITLE: 11/22 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 160Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Quiet day with some SQZ commissioning
18:21UTC Lockloss
18:51 Initial alignment started, finished at 19:16
20:10 NLN
20:25 Observing
20:39 into Commissioning
21:10 GRB-Short E454458 while SQZ comissioning was underway and LLO was still down
ITMY modes 5/6 was rising at a rate of 0.2% per hour (calculated from DTT measurements, 500 - 518 Hz BW=0.002), the broad monitor filter was showing it rising while the narrow was showing it decreasing which was confusing but the DTT measurements confirm its rising under its current settings.
23:00 I started a calibration measurement which finished at 23:30
23:35 back into Observing
23:56 SQZer unlocked and dropped us out of observing, back in at 23:59
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 16:31 | FAC | Karen | H2 enc | N | Tech clean | 16:32 |
| 19:09 | FAC | Cindi | Laundry room | N | Switch laundry | 19:24 |
| 18:54 | FAC | Firechief | Xarm | N | Drive down the arm | 19:20?? |
| 20:15 | FAC | Cindi | Laundry room | N | Get laundry | 20:30 |
| 22:53 | VAC | Travis | Optics lab | N | Parts check | 23:06 |
BB:
Started at 23:00 finished at 23:06
/ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20231122T230020Z.xml
Simulines:
GPS start: 1384729634.995449
2023-11-22 23:29:03,664 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20231122T230659Z.hdf5
2023-11-22 23:29:03,682 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20231122T230659Z.hdf5
2023-11-22 23:29:03,694 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20231122T230659Z.hdf5
2023-11-22 23:29:03,705 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20231122T230659Z.hdf5
2023-11-22 23:29:03,716 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20231122T230659Z.hdf5
ICE default IO error handler doing an exit(), pid = 418784, errno = 32
GPS end: 1384730961.811799
Sheila, Naoki
Instead of SQZ angle dither servo, we tried the SQZ angle ADF servo. The dither servo seems to work, but the dither makes the squeezing level worse and the SQZ angle the dither servo ended up is not exactly optimal value as reported in 74210. For ADF servo, we made a new guardian state named ADJUST_SQZ_ANG_ADF. This state has the same logic as ADJUST_SQZ_ANG_DITHER which is explained in 74210. We adjusted the ADF demod phase so that the ADF SQZ angle crosses 0 when the SQZ BLRMS4 gets minimum. The attached figure shows that the ADF servo seems to work. When the servo is closed, the ADF SQZ ANG goes to 0, the SQZ BLRMS4 goes to minimum, and the SQZ angle goes to the optimal value at 188 deg. We will leave the ADF servo on and see if it stabilizes the squeezing level next week.
(Jordan V., Gerardo M.)
Yesterday, Jordan and I installed 3 o-ring valves on the filter cavity tube crosses, with this installation the crosses for section B of the filter cavity tube are complete, as far as hardware goes. Most of the equipment used during the installation was moved out of the LVEA and into the filter cavity enclosure, where we are going to start o-ring installation on section "C" next week.
Naoki, Sheila
We tried to move the SRCL digital offset to see if we can reduce the frequency dependence of the squeezing angle. We roughly reproduced similar results to 68814 where Vicky And Elenna did the same test. We think that this method won't be helpful for tuning the SRCL offset to reduce the much smaller frequency dependence of the sqz angle we see in 74256
ref 0: FDS, SRCL offset -175, CLF6 demod phase 189.49 (observing configuration)
ref1: FIS, SRCL offset -175, CLF6 demod phase 189.49
ref2: FIS, SRCL offset -185, CLF6 demod phase 189.49
ref3: FIS, SRCL offset -200, CLF6 198.03
ref4: FIS, SRCL offset -100, CLF6 180
ref5: FIS, SRCL offset +100, CLF6 117.98
We've started our comissioning period at 20:39UTC after reaquiring NLN at 20:10UTC.
Fil, Dave:
Normally all the HWWDs show some activity to indicate they are operational, but ETMX has been quiet for just over 3 months. To verify it is still operational before we go into the holiday season, Fil went to EX and unplugged one of the satellite amp monitor cables from the front of the HWWD unit. It immediately started its 20 minute countdown. The cable was reattached after only a few seconds.
ndscope 30 day trend (https://lhocds.ligo-wa.caltech.edu/exports/dave/hwwd_30_day.png) in attachment shows the single ETMX data point from yesterday.
At 05:22:13 Tue 21st November 2023 PST most, but not all, Dolphin IPC receivers on h1sush7 recorded a single receive error.
Attachment shows timemachine capture of h1susfc1 and h1sussqzin IPC receive MEDMs.
I think this is the first non-forced spontaneous IPC receive error we have seen during O4, so it warrents a FRS ticket:
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1384712509
We saw some motion in the 1-3 Hz bandwidth at the corner station, and ASC_P saw some motion in the CS signals: INP1, MICH, PRC2...
Reaquired NLN at 20:10UTC
Wed Nov 22 10:04:45 2023 INFO: Fill completed in 4min 42secs
FAMIS 25966, last checked in alog 74193
Script reports elevated high frequency noise for the following sensors:
ITMX_ST2_CPSINF_H3
ITMX_ST2_CPSINF_V1
ETMX_ST2_CPSINF_H2
Elevated noise on ITMX H3 and V1 sensors has been reported in the past several checks, but ETMX ST2 H2 is new and certainly looks elevated.
All other chambers look nominal.
We lost lock 12 seconds after getting to NLN at 00:06UTC, there was a ~520Hz oscillation in DARM, the violins were decently rung up. The DCPDs were at pretty much the same level as they were in the following lock but both of these locks' DCPD signals were 10x what they were when we previously locked on 11/20 at 15:42UTC.
TITLE: 11/22 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 4mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.49 μm/s
QUICK SUMMARY:
PSL 102 (Anteroom) dust counts haven't changed in 23 hours, the 300nm have been stuck at 10 and the 500nm at 0.
IFO_NOTIFY called for help at 09:32 UTC this morning after H1 reached low noise but couldn't start observing due to an outstanding SDF diff. I REVERTED this diff in the EX_ISC SDF table for "H1:ALS-X_FIBR_LOCK_LOGIC_FORCE"
H1 is now happily observing as of 09:41 UTC.
TITLE: 11/22 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:
Fairly decent first 2/3's of the shift; then a M7.0 earthquake (+ high microseism) made the last 3hrs of the shift tough---with ALSy being the problem child as usual. In hindsight, I probably should have just waited out the earthquake longer instead of trying to lock after 2hrs.
Ended up staying a little extra to confirm the Initial Alignment completed. Then taking H1 back to locking after tonight's earthquake activity.
LOG:
Artem, Gabriele, Sheila, Louis Plots and Jupyter notebook with these results are also available here.ESD quadratic noise
This is a follow up on investigation of potential non-stationary noise at Handford introduced by the ESD drive, reported in 73913 and previous entries linked from there. The idea is that from the ESD signal, Vs, and bias, Vb, voltages we can reconstruct ESD force applied to the mirror, using equations in LIGO-T1700446. The force component linear in Vs gets subtracted by the control loop and therefore does not affect DARM. But the force component quadratic in Vb and both linear and quadratic in Vb can couple to DARM. Therefore in this report, we are calculating respective force components and projecting them to DARM. Then respective ASDs and spectrograms are compared.Selection of input channels
The ESD drive voltages are recorded by Monitors, H1:SUS-ETMX_L3_LVESDAMON_LL_OUT_DQ for Vs and H1:SUS-ETMX_L3_ESDAMON_DC_OUT_DQ for Vb. Important note here: we initially tried channel H1:SUS-ETMX_L3_ESDAMON_UL_OUT_DQ to get Vb, but it looks like it's not connected to anything and recording ASD noise... The H1:SUS-ETMX_L3_ESDAMON_DC_OUT_DQ seems to be fine. Also, LIGO-T1700446 specifies calibrations for voltage channels (equations 13 and 16), but currently the channels mentioned above are already calibrated to voltage.![]()
Calculating force terms
Calculation is based on equation 3 in LIGO-T1700446, but this equation is modified in the following way:
I did the same exercise but now for GPS time 1382909598 (and up to +22 mins from it), where bias voltage was set at 409V. Below you find plots where you can see that noise went up* (ASD) but apparent non-stationarity is reduced (spectrograms), which is consistent with Gabriele's findings in comment in 73935, specifically this and this plots.![]()
* Currently noise ASD is actually higher than DARM, this is not realistic but the modelling is not 100% precise. What is important here is relative changes with respect to results with "standard" level of bias voltage. Plots and Jupyter notebook with these results are also available here.
Another way to look at ESD quadratic noise. The DARM strain band-limited RMS (computed between 16 and 30 Hz and normalized to the median over time) is correlated to the total RMS of the ESD drive (dominated by the low frequency component, below 10 Hz)