Displaying report 1-1 of 1.
Reports until 17:05, Wednesday 03 August 2022
H1 CAL (CDS, DetChar, ISC, OpsInfo, SUS)
jeffrey.kissel@LIGO.ORG - posted 17:05, Wednesday 03 August 2022 - last comment - 15:05, Wednesday 10 August 2022(64316)
Calibration Changed a bit from PUM DAC Upgrade, Updated (again via Fudging Method) To Compensate; Also Sweeps Gathered so we can stop Fudging.
J. Kissel

I re-measured the broadband (CAL-DELTAL_EXTERNAL_DQ / CAL-PCALY_RX_PD_DQ) transfer function, and found it slightly different from the 2022-07-22 measurements (4% low below 20 Hz, 2% higher from 65 to 200 Hz). 

As such, and suspecting the root cause being the DAC upgrade of the penultimate stage, I nudged around the same scalar factors of the actuator I fudged the calibration with last time and thus I changed the calibration again. I found I needed to 
    - Change the PUM scale-factor from 1.01 to 1.05, and
    - Change the TST scale-factor from 1.045 to 1.07
to restore the systematic error to the levels of the previous fudge. Given how many times I've said fudge already, and that I need to change both the PUM and TST stage, you know that while these scale factors have made the systematic error transfer function similarly flat it doesn't make sense physically. But, we'll solve that mystery later. For now, the calibration is now as good as it was prior to the PUM DAC change.

In order to "solve that mystery later," I've gathered the 8 transfer function sweeps of all components of the response function. I'll post details about those measurements in the comments.

Attached are screenshots of the current new values of the scale factors.

Also attached is the DTT measure of the transfer function (which still has an old version of the corrective transfer function). 
    - Red trace is now, after sweeps and after fudge tuning.
    - (REF2) Blue trace is today, but before today's fudging, showing the ~4% frequency dependent error (~2% change) that has accrued since we last fudge-tuned the calibration on 2022-07-22
    - (REF4) Gray trace is just after fudge tuning, today, but before all the sweeping began a few hours ago. 
    - (REF4) Black trace is the 2022-07-22 measurement after the first fudging.
I took "post tuning" broad band injections twice several hours apart as a crude check to see if the IFO's *actual* time-dependent correction factors (most likely the sensing function optical gain or cavity pole) have changed. Because they report the same answer several hours apart leads me to believe that the TDCFs were stable across this period. It's a crude measurement (you'd see this more clearly if the PCAL had the range to drive out to higer frequency, but it does not.)
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 17:14, Wednesday 03 August 2022 (64318)
Here're the locations of all the sweeps I gathered for future post processing

    /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Measurements/FullIFOSensingTFs/
        2022-08-03_H1_DARM_OLGTF_LF_SS_5to1100Hz_15min.xml       # 1/(1+G)
        2022-08-03_H1_PCAL2DARMTF_LF_SS_5to1100Hz_10min.xml      # C/(1+G) and also (DELTAL / PCAL) transfer functions
        2022-08-03_H1_OMCDCPDSUM_to_DARMIN1.xml                  # measure of the [mA of OMC DCPD SUM/ DARM_ERR ct] transfer function 
                                                                 # for scaling the sensing function from units of [DARM_ERR ct / DARM m] 
                                                                 # to [mA on the DCPD SUM / DARM m]

        2022-08-03_H1_PCALY2DARMTF_BB_afterfudgeaftersweeps_3min.xml   # The broad band (DELTAL / PCAL) transfer function

    /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Measurements/FullIFOActuationTFs/
        2022-08-03_H1SUSETMX_L1_iEXC2DARM_25min.xml              # A_U * C / (1+G)
        2022-08-03_H1SUSETMX_L1_PCAL2DARM_8min.xml               # C / (1+G)
        2022-08-03_H1SUSETMX_L2_iEXC2DARM_12min.xml              # A_P * C / (1+G)
        2022-08-03_H1SUSETMX_L2_PCAL2DARM_6min.xml               # C / (1+G)
        2022-08-03_H1SUSETMX_L3_iEXC2DARM_12min.xml              # A_T * C / (1+G)
        2022-08-03_H1SUSETMX_L3_PCAL2DARM_6min.xml               # C / (1+G)

Will post the processed results in due time.
jeffrey.kissel@LIGO.ORG - 15:05, Wednesday 10 August 2022 (64428)INJ
In order to facilitate both 
    - automating this broadband excitation, and
    - understanding how to compute how much range the PCAL has for arbitrary waveforms (rather than the sum the simple RMS from one or two sine waves)

I attach a screenshot of the following things of the CAL-PCAL_EXC_SUM_DQ channel and the CAL-PCAL_RX_PD_OUT_DQ during the last of these broadband injections.
    - the 128 second time series from 2022-08-03 23:32:00 to 23:34:08 UTC,
    - the DTT computed amplitude spectral density 
        - ASD parameters, only 1 "average," thus the full 128 seconds were used with a single FFT, a Hanning Window is applied, 50% overlap [thought that doesn't matter for only one average], with the mean removed)
    - the cumulative RMS of the ASD as a function of frequency

Note that the ASD of CAL-PCAL_RX_PD_OUT_DQ is "calibrated" via the DTT calibration feature into m or m/rtHz with the simplest version of the corrections needed for PCAL, a zpk with a gain of 1.0 and two poles at 1 Hz. Thus, any amplitude loss, or phase distortion from the digital AA and analog AA filters are not accounted for, but for the purposes of this ASD measurement it doesn't matter at all, since the relevant data only goes up to 400 Hz, and we don't start to see appreciable impact from the AA filters until several kHz.

I've committed exports of these two time series and two ASDs (including the cumulative RMS ASD) here:
    /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Measurements/FullIFOSensingTFs/
        2022-08-03_H1_PCALY2DARMTF_BB_PCALEXC_freqasdrms.txt
        2022-08-03_H1_PCALY2DARMTF_BB_PCALEXC_timeseries.txt
        2022-08-03_H1_PCALY2DARMTF_BB_PCALRXPD_freqasdrms.txt
        2022-08-03_H1_PCALY2DARMTF_BB_PCALRXPD_timeseries.txt
I'll use these for validation of any python implementation of computing the ASD or RMS ASD from the time series (and vice versa).

The value of the cumulative RMS for the calibrated estimate of displacement (the PCAL_RX_PD_OUT_DQ * zpk([],[1;1],1.0) trace) is 3.3e-16 m_{rms}.
Images attached to this comment
Displaying report 1-1 of 1.