J. Kissel, L. Dartez, J. Rollins All dates called out "verbally" rather than automatically generated are in the format YYYY-MM-DD. All dates embedded into file names, automatically generated, are YYYYMMDD(T)HHMMSS(Z) where "T" represents "Time" and "Z" represents "Zulu" aka UTC time. Setting aside our desire to have immediate feedback that "what we've done is good" using a thermalized IFO that's not otherwise in use, we've updated the calibration pipeline. This physics of this update includes: - Minor changes to the CAL-CS foton filters that represent the calibration model's "free parameters." These are needed because the last update to the sensing function parameters was on May 05 2023 (LHO:69332), using sensing function data from 2023-05-04 -- prior to us finalizing the -290 SRCL offset on May 08 2023 LHO:69402, and the DARM offset equivalent to 40 mA of OMC DCPD SUM LHO:69358. Note that these updates do NOT include measurements taken after, or corrected for the 0.6% systematic error that had been present in PCAL and only corrected for on Friday May 12 2023 (LHO:69539) :: a new (inverse) optical gain, and cavity pole (actually different because of the new SRCL and DARM offsets) :: a new set of actuator strengths for the L1, L2, and L3 stages (only different because there's noise in the MCMC fitting) - Minor changes to "modeled DARM loop transfer functions at calibration line frequencies" EPICs records, corresponding to the above changes in the free parameters - Updates to final stages of FIR filters within the GDS (DMT) portion of the calibration line related to noise cleaning; no changes were made to the "primary" FIR filters which correct the sensing and actuation paths (since these do not depend on the free parameters). The new report also comes with, for the first time with the modern pydarm cmd-dev infrastructure, trust-worthy estimates of our "unknown frequency systematic error" [GPR fit results of the sensing and actuation functions]. That should mean we have everything we need to produce a modeled estimate of the response function systematic error (with uncertainty, sometime just referred to as "the uncertainty budget") though, only for frequencies below 1000 Hz, and for times when the IFO is completely thermalized. #LibrarianshipDetails This update uses the values and filters from the 20230510T062635Z calibration report (attached, in case it gets overwritten in the future), derived from the collection of "fixed" pydarm model parameter values set by the pydarm_H1.ini parameter file whose version has git hash c0bd4afe, and MCMC fits to the free parameters from - sensing measurements taken on 2023-05-10, LHO:69462 MCMC chains saved to ~cal/archive/H1/reports/20230510T062635Z/ sensing_mcmc_chain.hdf5 - actuation measurements taken on 2023-05-09, LHO:69427 MCMC chains saved to ~cal/archive/H1/reports/20230510T062635Z/ actuation_L1_EX_mcmc_chain.hdf5 actuation_L2_EX_mcmc_chain.hdf5 actuation_L3_EX_mcmc_chain.hdf5 and generated with the cmd-dev branch of the pydarm software suite, which has git hash 048acc12d. The GPR fits also live report's folder, ~cal/archive/H1/reports/20230510T062635Z/ sensing_gpr.hdf5 actuation_L1_EX_gpr.hdf5 actuation_L2_EX_gpr.hdf5 actuation_L3_EX_gpr.hdf5
After this report was exported to the front end and pushed to the archive, I restarted the GDS component of the pipeline (gstlal_compute_strain) at around 11:30am local time.
Now that the IFO's back up, things look good based on the metrics I have in the control room. Things are still evolving given that we're still thermalizing, but here's the state 1.0 hour in. opticalplant.png: \kappa_C is now closer to 1.0 (0.993, where it was 1.03). This is expected given the correct optical gain from the new DARM offset is now in place. f_CC is still evolving, currently at 440 Hz, but looks like it will settle on the new thermalized value of 433 Hz. actuatorstrength.png No change, as expected in any of the actuator \kappa values. systematicerror.png Systematic error at *some* line frequencies are better. Some low frequency lines (below 24 Hz) are worse, but I attribute that to thermalization. systematicerror_MEDM.png Screenshot of systematic error values, and a map between line numbers and line frequencies.