jeffrey.kissel@LIGO.ORG - posted 17:17, Monday 24 April 2023 - last comment - 08:43, Tuesday 25 April 2023(68959)
Model Prep: Changes to PCAL_MASTER Force and Displacement Calibration Infrastructure
J. Kissel, D. Bhattacharjee, T. Sanchez, J. Betzwieser WP 11138 From LLO:64213, I'm importing three changes to, and one feature removal from, the PCAL end-station calculations to compute the representative force and corresponding displacement for each channel, updating them for the latest methodology the team wishes to use in O4. Within the force calculation block this includes: (1) Correcting an inconvenience an EPICs record set in the computation of force coefficient, where the reference optical efficiency for the RX and TX PDs are stored. Where before the RX and TX optical efficiency EPICs records (TX_OPT_EFF_CORR and RX_OPT_EFF_CORR) were divided into each channels path, now, the TX record is multiplied in and the RX record remains divided in to each respective channel. (2) The calculation of optical efficiency *ratio* (comparing the ratio of TX to RX, then normalized by the above reference values) has been re-arranged, with an additional EPICs monitor of the unnormalized ratio for better understanding. Note: this causes a channel name change -- formerly, the normalized ratio was called OPT_EFF_RATIO_MON, and now it's called OPT_EFF_LIVE_OVER_REF. The new channel monitoring the unnormalized ratio is called OPT_EFF_LIVE_MON. (3) The former monitor of the ratio between channels was taken *after* this optical efficiency correction, with an EPICs and test point channel called ETM_PWR_RATIO_MON and ETM_PWR_RATIO_OUT. These have been unceremoniously removed. See before vs. after screenshots. Outside the force calculation, just prior to the conversion to displacement in the TX_PD and RX_PD filter banks, there's now a new EPICs record that applies the multiplicative correction to account for the differences in displacement between the X and Y arm, informed by the side-by-side comparison between the answer as seen in DARM. This new record is XY_COMPARE_CORR_FACT. See before vs. after screenshots. To import these changes was relatively simple, just an svn up to /opt/rtcds/userapps/release/cal/common/models PCAL_MASTER.mdl The h1calex and h1caley models, with the following updated library part, have been built successfully in prep for tomorrow's install and restart. I'll update MEDM screens tomorrow.
Images attached to this report
Comments related to this report
The CDS team informs me that it's been recently decreed that "no channels shall be removed without ECR," so I've reverted the removal of the OPT_EFF_RATIO_MON, OPT_EFF_RATIO_OUT, ETM_PWR_RATIO_MON, ETM_PWR_RATIO_OUT channels since the PCAL team doesn't have an ECR for these changes. All other infrastructure that rearranges the calculation and adds new channels will still go in as described above. See new screenshot of the FORCE_COEFF block. Here's the official channel change list for these changes jeffrey.kissel@cdsws03:~$ check_model_daq_configuration h1calex --------------------- file times ---------------------- Tue Apr 25 07:54:43 2023 = Model build time Tue Apr 18 10:21:21 2023 = Current configuration load time DAQ configuration is changed, processing... ++: slow channel H1:CAL-PCALX_FORCE_COEFF_OPT_EFF_LIVE_OVER_REF added to the DAQ ++: slow channel H1:CAL-PCALX_FORCE_COEFF_OPT_EFF_LIVE_MON added to the DAQ ++: slow channel H1:CAL-PCALX_XY_COMPARE_CORR_FACT added to the DAQ Total number of DAQ changes = 3 (3 additions, 0 deletions) jeffrey.kissel@cdsws03:~$ check_model_daq_configuration h1caley --------------------- file times ---------------------- Tue Apr 25 07:59:02 2023 = Model build time Tue Apr 18 10:21:21 2023 = Current configuration load time DAQ configuration is changed, processing... ++: slow channel H1:CAL-PCALY_FORCE_COEFF_OPT_EFF_LIVE_OVER_REF added to the DAQ ++: slow channel H1:CAL-PCALY_FORCE_COEFF_OPT_EFF_LIVE_MON added to the DAQ ++: slow channel H1:CAL-PCALY_XY_COMPARE_CORR_FACT added to the DAQ Total number of DAQ changes = 3 (3 additions, 0 deletions) which all match the functional changes expected from above.
Images attached to this comment
