Reports until 13:23, Wednesday 10 April 2019
H1 CAL (CAL)
madeline.wade@LIGO.ORG - posted 13:23, Wednesday 10 April 2019 - last comment - 11:13, Thursday 11 April 2019(48388)
New GDS calibration filters based on updated calibration model params

M. Wade, A. Viets

I have made new filters file for the GDS calibration pipeline based on the model params file aligocalibration/trunk/Runs/O3/H1/params/modelparams_H1_20190404.py in svn r7188.  The new filters are located in

aligocalibration/trunk/Runs/O3/GDSFilters/H1GDS_1238952670.npz 

I have attached results from testing these filters as well as plots of the filters themselves.  The tests were run on a lock stretch from earlier today (GPS times 1238956172-1238956672).  For these tests I did 

  1. The first attached plot is the response of the residual chain correction filter compared to the expected residual correction from pyDARM.
  2. The second attached plot is the response of the control chain correction filter compared to the expected control correction from pyDARM.
  3. The third attached plot is a comparison of the response function as derived from data calibrated (offline) with the GDS pipeline to the response function in pyDARM. 
  4. The fourth plot is a zoom-in on the ratio of this comparison.  Both of these plots indicate agreement at the expected level. 
  5. The fifth plot is a snapshot of the GDS-CALIB_STATE_VECTOR during this time, which looks as expected. 
  6. The sixth plot is a comparison of the ASD from the GDS pipeline with these filters and the two CALCS h(t) data streams (CFTD and not CFTD). 
  7. The seventh plot is a ratio of the ASDs from these three h(t) streams. 
  8. The last set of plots are all time series plots of the TDCFs as produced by GDS and by CALCS. 

We see the expected level of agreement for all of these tests.  I would like to investigate more the differences between the GDS and the CALCS CFTD strain channels, but this should not inhibit the installation of these new filters.

I have also created a new configuration file.  The most significant change to the configuration is that we are now applying scalar corrections for kappa_TST and kappa_C and frequency-dependent corrections for the cavity pole frequency. Note that we are not yet applying scalar corrections for kappa_PUM or kappa_UIM.  We have decided to hold off on this until the calibration lines are moved closer together, which increases the validity of these calculations.  The configuration file can be found in the calibration SVN:

 aligocalibration/trunk/Runs/O3/GDSFilters/H1GDS_1238952670.ini

I installed the new filters and configurations and restarted the calibration pipeline at approximately GPS time 1238962221 on both the production and redundant DMT machines.

Images attached to this report
Comments related to this report
madeline.wade@LIGO.ORG - 11:13, Thursday 11 April 2019 (48411)

M. Wade, J. Kissel

Jeff did a broadband PCAL sweep from 20:30:12 UTC to 20:31:58 UTC.  I analyzed the transfer function of GDS / PCALY during this sweep.  I've attached the results, which are consistent with our uncertainty budget in this frequency region (20 - 200 Hz).  I applied the pyDARM PCAL correction factors as the calibration to the PCAL channel and applied a gain of 3994.5 to the GDS channel to bring both channels into units of meters.

Images attached to this comment