Difference between revisions of "ShiftLeader"
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
** Learn how to keep track of the BTA with the [[BTA|BTA how-to]]. | ** Learn how to keep track of the BTA with the [[BTA|BTA how-to]]. | ||
| − | * Consult the [ | + | * Consult the [https://wiki.jlab.org/tegwiki/index.php/Daily_run_plans 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. |
* Maintain data taking quality and an efficient use of beam time. | * Maintain data taking quality and an efficient use of beam time. | ||
Revision as of 10:31, 8 November 2017
In the process of editing and updating this page. Please contact any of the Tritium Students for suggestions, ideas, help, or etc.
Back to Tritium-Main Back to Tritium main how-to
Direct link to the entire repository of information. (The original version of the current page.)
Shift Leader Responsibilities
- Communicate clearly and effectively with shift crews and MCC (7047), and log any status information to the HALOG. (Make sure to log in.)
- 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 hall access
- Post Snapshots of important information at least twice a shift.
- Include- Hall A tools, BPM strip-charts, and BCM strip-charts.
- Include any snapshots of the details after a change.
- Please feel free to post these Snapshots more often.
List of useful How-Tos for shift Leader