J. Kissel

After the success of injection a large collection of extra/new calibration lines (i.e. a frequency "comb" of calibration lines) back on 2019-12-17 (see LHO aLOG 53951), and the results turned out to be quite interesting (see LHO aLOG 55182), the calibration group would like to repeat this measurement. However, it requires manual turn-off of these extra lines, and it requires that the data be taken for 2 hours, just after hitting NOMINAL_LOW_NOISE, and staying OUT of observation mode. Thus, it must get run-coordinator approval (which we already have), and it has to be done during a target of opportunity (T.O.O.; i.e. after a lock loss). Thus, I provide instructions here, in hopes that any one may start the measurement, if that T.O.O. arises. 

We only need this measurement once more, so please check in with me and/or Keita to see if (a) tonight / today is a good day for this measurement, or (b) we've already taken the measurement.

Here're the instructions to run the measurement:
    (1) Wait until the ISC_LOCK guardian has acquired past MAXIMUM_POWER 
    - It's not *imperative* when exactly you start the following *exact* when MAXIMUM_POWER finishes, but I haven't tested the robustness of the IFO against these lines at earlier stages (specifically -- between ENGAGE_SOFT_LOOPS and POWER_10W may not be able to tolerate these lines, but thus far that's anecdotal evidence).
    - It *is* imperative that you at least get steps 2 and 3 below done *before* we enter NOMINAL_LOW_NOISE.

    (2) From a terminal and run the script to turn on all the the new *PCAL* calibration lines,
    ~$ cd /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Scripts/CALCS_FE
  ~$ python3.5 setup_sensingfunction_callinecombs.py

    (3) From a terminal, open up the DTT template for the DARM calibration lines, and run it.
    ~$ cd /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Scripts/CALCS_FE
  ~$ diaggui 2019-12-17_H1DARMEXC_SpringMonitoring.xml
    hit RUN

    (4) From a terminal, open up an ndscope trend of the detuned SRC, optical spring frequency (squared; aka "f_s^2"); this is your metric for "doneness" of the measurement.
    ~$ NDSSERVER=nds2.ligo.caltech.edu ndscope H1:GDS-CALIB_F_S_SQUARED -w [-7200,0]&
    [you'll have to wait *very* patiently, for these 2 hours of live 16 Hz data to populate, but, don't worry, you've got time.]

    (5) Watch and wait as the ISC_LOCK guardian reaches NOMINAL_LOW_NOISE, and then wait there for ~2 hours, until the detuned optical spring frequency levels out around -10 Hz^2.

    (6) While you're waiting, trend the PCALX high frequency roaming line frequency,
    ~$ NDSSERVER=nds2.ligo.caltech.edu ndscope H1:CAL-PCALX_PCALOSC1_OSC_FREQ -w [-7200,0]&
    and find out what it has been during the last, most recent observation ready segment. Store that number; we'll call it PCALXHFLINEFREQ for use below.

    (7) Record the UTC times (and GPS times, if you're nice) when we hit NOMINAL_LOW_NOISE and when you deem that ~2 hours is up and you begin to turn off the measurement, and grab a screenshot of the trend of f_s^2.

    (8) Go through the "turn off" instructions below

    (9) Write an independent aLOG (with CAL as its primary task, and OpsInfo tagged) that you've completed this measurement, and shoot an email to Jeff Kissel and Evan Goetz to let them know you've completed the measurement

Here's how to "turn off" and/or revert to *actual* NOMINAL_LOW_NOISE:
    (1) Hit "STOP" on the above DTT template.

    (2) Go to the CALEX and CALEY SDF screens and REVERT all differences. REVERT. REVERT. DO NOT ACCEPT.

    (3) Set the high frequency PCALX line back to it's most recent roaming line frequency,
    caput H1:CAL-PCALX_PCALOSC1_OSC_FREQ PCALXHFLINEFREQ

Thank you!