J. Kissel, T. Shaffer, L. Dartez

After gathering initial "looks OK" from DetChar and the search groups (see, e.g. LHO:71197 LHO:70892), we've turned on CAL_AWG_LINES again. This is in order to 
    (a) grab some more thermalization data now that we're consistently back at 60W (from 75W) to perform similar studies as we did at 75 W, and
    (b) give is more consistent information about the lower frequency response function systematic error

The plan is to have these be on for about 1 week, and to turn on subtraction so that these are subtracted out of the data.

The start time of the lines was 2023-07-25 22:21:15 UTC, just before this lock stretch's power up -- though this is not the start of the observation segment.

Recall, the frequencies are 
    PCALY_EXC  8.925, 11.575, 15.275, 24.5 [Hz]
    DARM_EXC   8.825, 11.475, 15.175, 24.4 [Hz]

H1:CAL-PCALY_DARM_EXC and H1:LSC-DARM1_EXC is the raw excitation channels that the guardian drives these lines into their respective actuators. To find the versions of these excitations that are in channels that are stored in frames, look at H1:CAL-PCALY_EXC_SUM_DQ and H1:LSC-DARM1_EXC_DQ. 
    - The PCALY_EXC_SUM is the sum of ALL line excitations from PCALY, defined either from this DARM_EXC bank or from the individual OSC oscillators. So again, there's no EPICs record that houses these frequencies or amplitudes like a "normal" set of PCAL lines. 
    - The the DARM lines are the only thing driving into the DARM1_EXC channel.

Operational changes in order to make this OK -- for observing:
    - Changed the nominal state of the CAL_AWG_LINES for LINES_ON to be nominal.
    - Accepted the H1:CAL-PCALY_DARM_GAIN = 1.0 value in SDF in the safe.snap and observe.snaps.

Still to-do:
    - actually turn on the subtraction of these lines
    - figure out how to change the guardian such the guardian call to awg is robust across computer failures/restarts (i.e. next Tuesday).