aLIGO LHO Logbook

H1 CAL (DetChar, ISC, OpsInfo)

jeffrey.kissel@LIGO.ORG - posted 09:48, Monday 09 September 2019 - last comment - 12:46, Friday 13 September 2019(51819)

NEW, MORE ACCURATE CALIBRATION MODEL BEING INSTALLED NOW

YES THIS WILL DROP THE FRONT-END COMPUTED BNS RANGE, because we're improving the accuracy of the real-time pipeline in order to better matrch the current IFO (more power than when it was last updated, no detuning, good spot positions, SRCL offset, accounting for new UIM boost, etc.)

Should be done in an hour or three. When we come back in to OBSERVATION READY, the new model will be in place.

See details of the model in LHO aLOG 51784, and references there in.
The decision point to change the model is documented in LHO aLOG 51782, which has yet more references and explanation.

Comments related to this report

jeffrey.kissel@LIGO.ORG - 12:13, Monday 09 September 2019 (51825)DetChar, ISC, OpsInfo

Link

INSTALLATION COMPLETE. As predicted, front-end BNS range dropped by ~5 Mpc, and now in better agreement with GDS produced BNS range.

First OBSERVATION READY SEGMENT with this new 2019-09-09 model installed started at GPS Time 1252088806 (Sep 09 2019 18:26:28 UTC; Sep 09 2019 11:26:28 PDT).

jeffrey.kissel@LIGO.ORG - 11:03, Monday 09 September 2019 (51821)

Link

Reference Model values at calibration line frequencies (aka "EPICs records") for this model update have been generated and installed.
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Results/CALCS_FE/
    epicsrecords_model-H1_20190909_created-20190909.txt


In doing so, I've created the script
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Scripts/CALCS_FE/
    python3.5 createEPICS_for_20190909.py rev 8397.


and modified it and computeDARM.py to be able to write the EPICs records to file separately from actually pushing it to the front-end.
/ligo/svncommon/CalSVN/aligocalibration/trunk/Common/pyDARM/src/
    computeDARM.py rev 8399

aaron.viets@LIGO.ORG - 17:36, Wednesday 11 September 2019 (51916)

Link

I've used the broadband injection made just after the model update to do a comparison of calibration accuracy with different levels of time-dependent corrections applied, using the new model. This is similar to the analysis done in LHO aLOG 51794. The attached plot has 4 versions of offline calibration, each with different TDCF corrections applied, as indicated in the plot legend. The 5th (red) curve is from the online GDS data (C00). The previous conclusions are still supported by this data: 1) We should not be correcting for SRC time dependence; and 2) We should not be applying the imaginary parts of the actuation kappas. Note the large errors caused by applying corrections for SRC time dependence. This may be due to the fact that the model value of f_s is zero, causing numerical instability when applying time-dependent corrections.

This plot, as well as text files with the data, are available in the calibration SVN here:
aligocalibration/trunk/Runs/O3/H1/Measurements/FullIFOSensingTFs/DCS_BB_plots

Images attached to this comment

aaron.viets@LIGO.ORG - 12:46, Friday 13 September 2019 (51934)

Link

The values of the TDCFs used by the GDS and DCS calibration pipelines to produce the calibrated data during this broadband injection were:

For the C00 data (this can be seen on the summary page for that day, just after 18 UTC):

kappa_tst = 1.0006982 - 0.0017864768 i
kappa_pum = 1.0056942 - 0.018216213 i
kappa_uim = 0.98730505 - 0.0054550767 i
kappa_C = 0.99618191
f_cc = 411.49304 Hz
f_s^2 = -6.3915501 Hz^2
1/Q = 0.053302728

For the DCS data (very similar, but not quite identical):

kappa_tst = 1.0003096 - 0.0017248055 i
kappa_pum = 1.0059613 - 0.018130977 i
kappa_uim = 0.98809701 - 0.0064163199 i
kappa_C = 0.99798113
f_cc = 411.66858 Hz
f_s^2 = -6.49055 Hz^2
1/Q = 0.070739277