BTA guidelines

From GlueXWiki
Revision as of 10:18, 29 March 2018 by Njarvis (Talk | contribs) (Created page with "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 b...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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 UED: unplanned experiment down


PCC would include time when beam is masked while moving radiators, etc. UED would include time when we cannot take data due to unpleasant surprises, eg hardware failure and extended daq problems.


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.