Explicitly track Procedural Tuning

[slominskir]

Just like the Experimenter halls which have procedures, the accelerator has it's own procedures such as QE Measurements, which need to occur relatively frequently to maintain a quality beam, and in the aggregate consume a substantial amount of beam time. These procedures aren't currently tracked explicitly by BTM.

The common Procedural Tuning activities include:

• QE Measurement
• Pathlength and Gangphase measurements
• BLA BCM Calibration
• PSS Reconfiguration

This has implications for the Joule report, which has a "Tuning" metric. There are actually several other flavors of tuning, including restoring the machine from SAM (NPES Restore), and pass/energy/quality changes in Accelerator Configuration Change (ACC). These two are actually explicitly captured on Crew Chief timesheets in BTM already.

There are a few nuances to consider:

1. The pulsed beam mode is tracked per hall by Crew Chiefs, and is unfortunately labeled Tune beam mode. This probably needs to change, and it isn't necessarily used for tuning, and on the flip side, sometimes tuning occurs with Continuous Wave (CW) beam mode, so it's definitely a misnomer. Plus, it turns out we really don't need to make a distinction on beam mode at all in BTM. So probably just consolidate the Tune metric into the existing UP metric (which captures CW only currently). Simplify. Archiver will likely still track pulsed vs CW if anyone needs to know for some reason.

2. Currently QE Measurements (and other procedures) are likely captured one of two ways, depending on machine mode. If we're doing Physics then QE Measurements are likely captured as hall BNA (should be OFF). If we're in internal accelerator mode, then QE Measurements are likely captured as Internal Down (should be OFF). Going forward we are proposing capturing Procedural Tuning as a separate dedicated metric (an unambiguously explicit accelerator activity, so halls would need to record OFF).

3. In DTM operators often (but not always) record tuning as a Beam Transport downtime. If they select Event Type ACC then this counts as an unscheduled failure in the Joule report. To correct, we must ensure the Event Type is Non-Program (NP). We may consider adding additional selection options under Category/System Beam Transport to help better track specific procedures.

4. We actually have an allowance of tuning as set by the NPES (varies, but often 8 hours per week, and there is often a special separate allowance for SAM Restore as well). This also has implications on the Joule report - if we exceed our allowance then tuning counts as downtime.

5. This enhancement would require changes to BOOM. It is unclear if it would require changes to IOC automated time accounting (if it doesn't default to OFF during accelerator activities, then yes).

[slominskir]

Operability has provided a mock-up of what they want this to look like: