I was left with a small novel describing some calibration measurements that needed to be run. I tried to follow Jeff's instructions, but I don't think everything ran as it was intended. Two measurements described as "Sensor measurements", one doesn't look like the reference and the other doesn't look like it actually ran the excitation properly.
2019-04-10_H1DARM_OLGTF_5to1100Hz_30min.xml <-- this TF is just flat and doesn't look like it actually went.
2019-04-10_H1_PCAL2DARM_TF_5t1100Hz_15min.xml <-- this looked like it ran, but the measurement doesn't look like the reference.
Everything else seemed to go okay, other than the implied times in the file names didn't seem to actually reflect how long the measurements would take. Often a "25min" measurement was more like 10 minutes. I've saved all the new data as requested and left all the measurements up on the workstation that was set up for the measurements.
Thanks Jim and TJ! I'm super happy that y'all got as much as you did -- especially given last night's 50 mph winds from Winter Storm Wesley!
The actuator measurements that were successful:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Measurements/FullIFOSensingTFs
2019-04-10_H1SUSETMX_L1_iEXC2DARM_25min.xml
2019-04-10_H1SUSETMX_L1_PCAL2DARM_8min.xml
2019-04-10_H1SUSETMX_L2_iEXC2DARM_17min.xml
2019-04-10_H1SUSETMX_L2_PCAL2DARM_8min.xml
2019-04-10_H1SUSETMX_L3_iEXC2DARM_8min.xml
2019-04-10_H1SUSETMX_L3_PCAL2DARM_8min.xml
I agree with Jim's assessment of the times on the file names, we've been messing around with the excitation amplitudes and frequency vectors and haven't updated the file names.
The sensing measurements which were only 1/2 successful:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Measurements/FullIFOSensingTFs
2019-04-10_UTC_H1DARM_OLGTF_5to1100Hz_30min.xml <-- DTT disease -- failed to gather data because template is corrupted, shows a transfer function with magnitude and phase of identically 0.0, with 0.0 coherence. Usually just an "abort" and (re)"start" (after seeing a few data points of zero) will work.
2019-04-10_UTC_H1_PCAL2DARM_TF_5t1100Hz_15min.xml <-- This was successful, and although Jim said this "doesn't look like the reference" that's OK. We know this template's calibration is incorrect, but just haven't had time to fix it.
Model parameter set installed in to CAL-CS during these measurements:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/params
modelparams_H1_20190404.py
based on measurements from 2019-04-03 (from LHO aLOG 48220).
Changes to CAL-CS calibration:
- Change the model actuator gains from 0.95 to 1.
caput H1:CAL-CS_DARM_ANALOG_ETMX_L3_GAIN 1.0 (was 0.95)
caput H1:CAL-CS_DARM_ANALOG_ETMX_L2_GAIN 1.0 (was 0.95)
caput H1:CAL-CS_DARM_ANALOG_ETMX_L1_GAIN 1.0 (was 0.95)
- Flip the actuation strength filters "Npct" from ER14 to O3
in the same banks as above, switch from FM9 to FM4 (updates we *very* small, changes at the less-than-0.5% level, but installed just to be consistent with MCMC fits of measurements)
- Change the sensing function filters "Gain" and "D2N" from ER14 to O3
In H1:CAL-CS_DARM_ERR bank, switch FMs 9 and 10 to FMs 7 and 8 (updates were mostly to spring frequency and Q, and small, 1% level nudges to the optical gain and cavity pole frequency.)
- Change delay between actuator and sensing paths from 7 to 9
caput H1:CAL-CS_DARM_CTRL_DELAY_CYCLES 9.0 (was 7.0)
- write new reference model parameters at calibration line frequencies
cd /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Scripts/CALCS_FE/
python3.5 createEPICS_for_20190404.py -w
EPICs Records installed during these measurements:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Results/CALCS_FE
epicsrecords_model-H1_20190404_created-20190410.txt