Difference between revisions of "BTA guidelines"
| Line 6: | Line 6: | ||
<li>BNA: beam not acceptable</li></ul> | <li>BNA: beam not acceptable</li></ul> | ||
| − | Experiment beam time | + | <b>Experiment beam time</b> |
| − | ER: experiment ready | + | <ul><li>ER: experiment ready</li> |
| − | PCC: planned configuration change | + | <li>PCC: planned configuration change (when beam is masked while radiators are moved, etc)</li> |
| − | + | <li>UED: unplanned experiment down (unpleasant surprises, hardware failure, extended daq issues)</li></ul> | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | UED | + | |
Revision as of 10:22, 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: acceptable beam 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 information is loaded from epics it shows the accelerator beam time derived from automatic measurements from accelerator counters and experiment beam time as 100% UED.
The shift leader should ensure that the accelerator timesheet is consistent with the total time that we requested no beam, PCC + UED. In particular, BANU should not exceed the integrated time we request no beam. If the accelerator beamtime is not correct, the shift leader should move all the time that is listed under BANU into the BNA column unless they specifically requested no beam from MCC.
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.
