Difference between revisions of "BTA guidelines"
| Line 12: | Line 12: | ||
| − | When the information is loaded from epics it contains automatic calculations of accelerator beam time from beamline monitors and 100% UED experiment down. | + | When the BTA information is loaded from epics it contains automatic calculations of accelerator beam time from beamline monitors and 100% UED experiment down. |
Revision as of 10:37, 29 March 2018
Proposed beam time accounting guidelines (based on Mark D's proposal in https://halldweb.jlab.org/wiki/index.php/Run_Planning_Meeting_Notes,_Feb_1-Feb_7,_2018)
Accelerator beam time
- ABU: acceptable beam used
- BANU: beam acceptable but not used
- BNA: beam not acceptable
Experiment beam time
- ER: experiment ready
- PCC: planned configuration change (when beam is masked while radiators are moved, etc)
- UED: unplanned experiment down (unpleasant surprises, hardware failure, extended daq issues)
When the BTA information is loaded from epics it contains automatic calculations of accelerator beam time from beamline monitors and 100% UED experiment down.
Proposed guidelines
The shift leader should ensure that the accelerator timesheet is consistent with ours. In particular, BANU should equal PCC+UED, the total time when no beam was requested.
During physics running, ABU + BANU should be the duration of good quality beam delivery.
During initial setup following beam restoration the beam quality is not so critical, so beam-time spent checking radiation levels and harp scans etc should be counted as ABU.
Total time should be estimated to the nearest minute?
(The shift leader should also make a log entry at the end of each shift showing the stripcharts for beam current and position following our whiteboard instructions.)
