david.barker@LIGO.ORG - posted 08:15, Sunday 22 September 2024 (80228)
Sun CP1 Fill
Sun Sep 22 08:12:37 2024 INFO: Fill completed in 12min 32secs
Images attached to this report
Sun Sep 22 08:12:37 2024 INFO: Fill completed in 12min 32secs
TITLE: 09/22 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 8mph Gusts, 5mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.14 μm/s
QUICK SUMMARY:
TITLE: 09/22 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Quiet shift after relocking following a PI-caused lockloss.
H1 has now been locked and observing for 5 hours.
LOG:
No log for this shift.
TITLE: 09/21 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: We did not take the calibration measurement as LLO wasn't locked and we weren't fully thermalized either.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 23:58 | SAF | H1 | LVEA | YES | LVEA is laser HAZARD | 18:24 |
| 17:56 | PEM | Robert | Xarm | N | CEX PEM investigations/tests | 21:00 |
H1 back to observing at 23:59 UTC. Fully automated relock, no initial alignment needed.
The lockloss this morning at 12:38 UTC which ended a 31+ hr lock had the rarely seen FSS_OSCILLATION tag, so I started looking back at some related signals just to get a better idea of what happened. I've attached a trend which seems to show some IMC signals (mainly splitmon and IMC_F) see the first action before the lockloss, then the FSS fastmon has its first "glitch" about 140ms later. I'll admit I don't have a complete understanding of all the interactions here or what this is indicative of, but I figured it might be useful to take a look at since these FSS_OSCILLATION locklosses are quite rare.
TITLE: 09/21 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 13mph Gusts, 7mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.16 μm/s
QUICK SUMMARY: H1 just lost lock from PI mode 24 ringing up after being locked for 90 minutes. Starting lock acquisition.
Back to observing at 21:30 UTC
RickS, FranciscoL, TonyS, JoeB, Dripta.
On Saturday, Sept. 21, 2024, the Pcal force coefficient EPICS record values were updated.
At X-end:
Old : H1:CAL-PCALX_FORCE_COEFF_RHO_T 8305.09
New : H1:CAL-PCALX_FORCE_COEFF_RHO_T 8300
Old : H1:CAL-PCALX_FORCE_COEFF_RHO_R 10716.6
New : H1:CAL-PCALX_FORCE_COEFF_RHO_R 10713.3
Old : H1:CAL-PCALX_FORCE_COEFF_TX_PD_ADC_BG 9.6571
New : H1:CAL-PCALX_FORCE_COEFF_TX_PD_ADC_BG 8.81815
Old : H1:CAL-PCALX_FORCE_COEFF_RX_PD_ADC_BG 0.7136
New : H1:CAL-PCALX_FORCE_COEFF_RX_PD_ADC_BG 0.56678
Old : H1:CAL-PCALX_FORCE_COEFF_TX_OPT_EFF_CORR 0.9938
New : H1:CAL-PCALX_FORCE_COEFF_TX_OPT_EFF_CORR 0.99331
Old : H1:CAL-PCALX_FORCE_COEFF_RX_OPT_EFF_CORR 0.9948
New : H1:CAL-PCALX_FORCE_COEFF_RX_OPT_EFF_CORR 0.9944
Old : H1:CAL-PCALX_XY_COMPARE_CORR_FACT 0.9991
New : H1:CAL-PCALX_XY_COMPARE_CORR_FACT 0.99855
At Y-End:
Old : H1:CAL-PCALY_FORCE_COEFF_RHO_T 7145.62
New : H1:CAL-PCALY_FORCE_COEFF_RHO_T 7155.15
Old : H1:CAL-PCALY_FORCE_COEFF_RHO_R 10649.6
New : H1:CAL-PCALY_FORCE_COEFF_RHO_R 10663.6
Old : H1:CAL-PCALY_FORCE_COEFF_TX_PD_ADC_BG 18.2388
New : H1:CAL-PCALY_FORCE_COEFF_TX_PD_ADC_BG 18.3088
Old : H1:CAL-PCALY_FORCE_COEFF_RX_PD_ADC_BG -0.2591
New : H1:CAL-PCALY_FORCE_COEFF_RX_PD_ADC_BG -0.7353
Old : H1:CAL-PCALY_FORCE_COEFF_TX_OPT_EFF_CORR 0.9923
New : H1:CAL-PCALY_FORCE_COEFF_TX_OPT_EFF_CORR 0.99191
Old : H1:CAL-PCALY_FORCE_COEFF_RX_OPT_EFF_CORR 0.9934
New : H1:CAL-PCALY_FORCE_COEFF_RX_OPT_EFF_CORR 0.9931
Old : H1:CAL-PCALY_XY_COMPARE_CORR_FACT 1.0005
New : H1:CAL-PCALY_XY_COMPARE_CORR_FACT 1.00092
The caput commands used for updating the ePICS records can be found here: https://git.ligo.org/Calibration/pcal/-/blob/master/O4/EPICS/results/CAPUT/Pcal_H1_CAPUTfile_O4brun_2024-09-16.txt?ref_type=heads
SDF diff has been accepted.
It has been roughly 4 months since the last update on May 2024. We plan to update the EPICS reords regularly, since over the course of a year , we observed that the Rx sensor calibration exhibits a systematic variation by as much as +/- 0.25 % at LHO. End station measurements allow us to monitor this systematic change over time. We will monitor the X/Y comparison factor to see if these EPICS changes had any significant effect on it. If the update is done correctly, there should be no significant change in the X/Y calibration comparison factor. If we find that there is a signifricant change in it, then we will correct the ePICS records accordingly.
Attached .pdf file shows the Rx calibration (ct/W) trend at LHOX and LHOY end for the entire O4 run. It marks the measurements used to calculate the Pcal force coefficients EPICS record values for the previous update at the start of the O4b run as well as the current update.
The pngs are the screenshots of the MEDM screen after the EPICS update.
Sat Sep 21 08:11:59 2024 INFO: Fill completed in 11min 55secs
TITLE: 09/21 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Aligning
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 10mph Gusts, 5mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.15 μm/s
QUICK SUMMARY:
H1 had been stuck in IA for 1.5 hours, something was clearly yawed from the camera. I looked at the osems scopes for the PRC and the ITM, ETM, TMS and set the test mass sliders to recover the osem values from when we were locking on the 20th. ITMY_Y ended up having to be moved the most, now we're moving along IA at regular pace.
TITLE: 09/21 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Very quiet shift, H1 remained locked throughout. Only events of note were a brief drop in observing because of the SQZ PMC and an earthquake passed through.
H1 has now been locked for just over 24 hours.
TITLE: 09/20 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:
LOG: The range was in the upper 150s for most of shift, we've been locked for almost 19 hours!
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 23:58 | SAF | H1 | LVEA | YES | LVEA is laser HAZARD | 18:24 |
| 16:08 | PEM | Robert | Yarm | N | PEM measurements, left at 16:20, 18:22 | 17:28 |
| 22:11 | VAC | Janos | Site | N | Cryopump checks | 22:27 |
| 23:16 | PEM | Robert | Y-arm | N | Setup test equipment | 01:16 |
HAM6 OMC TRANS camera was pretty jittery the whole shift
18:15 UTC, EDC reports 12 DC chans again, from NUC33. The NUC doesn't look frozen as the SQZ plot is still updating.
TITLE: 09/20 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 16mph Gusts, 9mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY: H1 has been locked and observing for 18 hours. Sounds like it's been a quiet day.
We've been locked for a little over 14 hours, its been a calm day.
The range has been in the high 150s all morning.
The low range check yielded < ~14 Hz SRCL & CHARD_Y (and at >95Hz), and > ~14 Hz PRCL (and at >95Hz) & DHARD_Y coherence.
Followed instructions in 74681. Last done in 78782, 79988. Saved in /ligo/gitcommon/NoiseBudget/aligoNB/aligoNB/H1/couplings/ and pushed to git.
CHARD_P, CHARD_Y, MICH, PRCL, SRCL screenshots attached. The IFO had been in NLN for 4h15 when these were taken. The AS_A_YAW and PRCL offsets were turned off.
I modified the script used in 78969 to project PRCL noise to DARM through MICH and SRCL, and now added coupling through CHARD P + Y.
There is high coherence between PRCL and CHARD, but these active injections that Camilla did show that the main coupling of PRCL to DARM is not through CHARD.
This script is now in /ligo/gitcommon/NoiseBudget/simplepyNB/PRCL_excitation_projections.py (not actually a git repo)
Sheila, Vicky - we ran the noise budget using these updated couplings from Camilla.
Noise budget with squeezing - pdf and svg (and the quantum sub-budget with squeezing). Plots without unsqueezed DARM here: pdf and svg. Picked a time with high range, and good ~4.8dB squeezing.
Noise budget without squeezing - pdf and svg (and the quantum sub-budget without squeezing).
The remaining sub-budgets are for squeezed DARM: Laser, Jitter, LSC, ASC, Thermal, PUMDAC.
Noise below 25 Hz looks pretty well accounted for: 10-15 Hz ~ ASC (CHARD Y, then CSOFT P, CHARD P). 15-20 Hz ~ LSC (PRCL).
Some comments and caveats for these budget plots:
The code has been pushed to aligoNB repo, commit 95d3a88b. To make these noise budget plots:
Thanks to Erik von Reis for helping us update the aligoNB environment to newer python and scipy (etc) versions. Next to-do: have the budget code use median averaging to be more robust to glitches (which can be done now that the environment has an updated scipy!).
Sheila, Louis, Francisco
Following LHO:80044, we measured ASC-DHARD_P(Y) for different ASC-AS_A_DC_YAW_OFFSET and found the loswet values of DHARD_Y at an offset of -0.05.
The "DTT_AS_A_*.png"s show the outputs of DHARD_DARM_240912 when changing AS_A_DC_OFFSET with a reference trace for when the offset was nominal (ASC-AS_A_DC_YAW_OFFSET = -0.15). Each trace has a marker at the two highest peaks in the ASC-DHARD power spectrum (the middle plot on the left). DTT_AS_A_neg0_05 shows the lowest value in the power spectrum compared to DTT_AS_A_neg0_10, while preserving coherence (lowest-left) and phase values (middle-rigt), compared to DTT_AS_A_0. AS_A_NDSCOPE corroborate on the times at which these measurements were done and the values for AS_A offset.
Confirming that the four TFs traces corresponding to reports
were all done under a thermalized interferometer.
