Difference between revisions of "ShiftLeader"
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
* Keep track of [https://bta/ beam time accounting] | * Keep track of [https://bta/ beam time accounting] | ||
| − | ** [[BTA|BTA | + | ** Learn how to keep track of the BTA with the [[BTA|BTA how-to]]. |
* Consult the [[daily run plans]] and communicate with [https://misportal.jlab.org/mis/physics/shiftSchedule/index.cfm?experimentRunId=HALLAC-2017 run coordinator] whenever problems happen that cannot be solved by shift workers. | * Consult the [[daily run plans]] and communicate with [https://misportal.jlab.org/mis/physics/shiftSchedule/index.cfm?experimentRunId=HALLAC-2017 run coordinator] whenever problems happen that cannot be solved by shift workers. | ||
| Line 22: | Line 22: | ||
** run list (describing the goal of this run: eg production on LH2, BMC calibration...) and report main statistic numbers | ** run list (describing the goal of this run: eg production on LH2, BMC calibration...) and report main statistic numbers | ||
** any major events, including accesses | ** any major events, including accesses | ||
| + | |||
| + | *Post Snapshots of important information at least twice a shift. | ||
| + | ** Include- Hall A tools, BPM strip-charts, and BCM strip-charts. | ||
| + | ** Include any snap shots of the details after a change. | ||
Revision as of 11:09, 17 July 2017
In the process of editing and updating this page. Please contact any of the Tritium Students for suggestions, ideas, help, or etc.
Shift Leader Responsibilities
- Communicate clearly and effectively with shift crews and MCC (7047), and log any status information to the HALOG
- Keep track of beam time accounting
- Learn how to keep track of the BTA with the BTA how-to.
- Consult the daily run plans and communicate with run coordinator whenever problems happen that cannot be solved by shift workers.
- Maintain data taking quality and an efficient use of beam time.
- Follow the directives in the COO
- Log the following in a shift summary in the HALOG:
- run list (describing the goal of this run: eg production on LH2, BMC calibration...) and report main statistic numbers
- any major events, including accesses
- Post Snapshots of important information at least twice a shift.
- Include- Hall A tools, BPM strip-charts, and BCM strip-charts.
- Include any snap shots of the details after a change.