J. Kissel

Browsing through SDFs compared against our recent commissioning activity, I've reconciled a few safe.snaps this morning:

H1SUSETMX: 
- accepted L2_DRIVEALIGN_A2L matrices as 1.0 (i.e. permanently turning ON the L2A decoupling filters, recommissioned with new frequency-dependent matrix topology); see LHO aLOGs 51717, 51709, 51604, and 49825.

H1SUSETMY:
- Accepted ETMY PUM A2L spot position gains as 4.3 and 3.6.
H1SUSITMY: 
- Accepted ITMY PUM P2L spot position gain as -3.0
H1SUSITMX:
- Accepted ITMX PUM P2L spot position gain as -3.965
These are the "FULL POWER" positions, according to the current revision of 
${userapps}/release/isc/h1/guardian/lscparams.py
     The "CENTERED" positions, at which we now "start" the ADS loops (see last paragraph of LHO aLOG 51715, which is a shortened version of the dance around the point absorber position, discussed in LHO aLOG 51426), don't get reset (from FULL POWER) until just before the ADS loops are turn on in PREP_ASC_FOR_FULL_IFO, quite a ways along in the lock acquisition sequence. Thus, after a lock loss, and even after the DOWN state is run, the A2L gains will remain at their FULL POWER position, and not be reset. Apparently, some of the FULL POWER A2L gains had been accepted in some safe.snaps, but not consistently in all.
     This has now been remedied. In reality, since the spot position gains *are* set by guardian *eventually* before they're used, this dosn't really matter, but it reduces the number of SDFs which are noise when reconciling in the future.

H1LSC:
- Accepted the filter configuration needed for the improved PRCL FF filter (accepting the configuration shown in the OBSERVE.snap as an attachment to LHO aLOG 51553).
- Also accepted PRCL FF TRAMP to be 3 seconds, as was apparently commissioned on Aug 28 2019, though now appears to be in guardian as well, so again, just reducing noise here.

H1SUSPRM:
- Reverted SUS-PRM_M1_DITHER_P_TRAMP from 10.0 to 0.0. Now inconsequential tramp turned on for a brief test back on Aug 29th. Reverting the tramp to 0.0, since it's otherwise been unused for the entire run. #AlarmNoiseReduction

H1CALCS:
- Accepted values of new Calibration Reference Model Values at Calibration Line Frequencies (aka "EPICS RECORDS", installed and accepted in yesterday's install; see ), but these are different only at the sub-double precision level -- so these diffs will continue re-appear until we round these numbers.
I'll take this as an action to fix the precision at which we write these values.

There are several other unknown differences that may be maintenance / commissioning related activities currently on-going, so we'll take a look after we've re-run the DOWN state at the *end* of maintenance today.