J. Kissel, T. Shaffer We've not yet done a quantitative study on how the CAL_AWG_LINES guardian's eight "thermalization characterization" calibration lines (PCALY driven at freq=[8.925, 11.575, 15.275, 24.5] Hz, and DARM1_EXC driven at freq=[8.825, 11.475, 15.175, 24.4] Hz) substantially pollute parts of the detector sensitivity, but given that we "should have enough data" from the past few weeks to fullfil the current plan of how to handle what systematic error the detuned SRC brings in to the calibration during thermalization (see, e.g. LHO:69796), we've turned off the CAL_AWG_LINES guardian calibration line excitations. Here's what "turning off" looks like: - Requested the CAL_AWG_LINES guardian to IDLE. (Because this guardian is not robust against computer crashes [LHO:69688], that made the guardian go into error, so we hit "RELOAD" to re-initialized it, and confirmed that the PCALY and DARM1_EXC test points have disappeared). Not it sits in IDLE, with none of its lines driven. - We've changed the NOMINAL_STATE to "IDLE" (rather than LINES_ON) - Committed CAL_AWG_LINES code changes the changes to cal/h1/guardian/CAL_AWG_LINES.py, now at rev 25692. - We've removed the following lines from the ISC_LOCK guardian, and reloaded the guardian as of 2023-05-23 16:24 UTC ISC_LOCK Actual Code Context Notes Line # 43 CAL_AWG_LINES # In the list of managed nodes 5475 nodes['CAL_AWG_LINES'] = 'LINES_ON' # In ISC_LOCK's LOWNOISE_LENGTH_CONTROL state, in the "run" portion, making sure the lines were on on the way up during every lock acquisition sequence 5899 nodes['CAL_AWG_LINES'] = 'IDLE' # In ISC_LOCK's NLN_CAL_MEAS state, in the "main" portion, turning these OFF during calibration measurements 5923 nodes['CAL_AWG_LINES'] = 'LINES_ON' # In ISC_LOCK's NLN_CAL_MEAS state, in the "run" state, turning them back ON when returning from NLN_CAL_MEAS to NOMINAL_LOW_NOISE - Set the CAL_AWG_LINES guardian's MANAGER to "AUTO" by hitting the H1:GRD-CAL_AWG_LINES_MODE button. - Committed the ISC_LOCK guardian code to the userapps/isc/h1/guardian/ to the svn. (just before my "removal" commit was rev 25693, removed commit is rev 25699.) We have *not* stopping or disabling the node, just in case we *don't* have enough data and we want to bring this back online occasionally.