Difference between revisions of "ShiftLeader"
Jump to navigation
Jump to search
(Created page with "In the process of editing and updating this page. Please contact any of the [https://hallaweb.jlab.org/wiki/index.php/Graduate_Students Tritium Students] for suggestions, idea...") |
|||
| Line 4: | Line 4: | ||
[https://wiki.jlab.org/tegwiki/index.php/How-To_and_Shift_Info <B>Back one page</B>] | [https://wiki.jlab.org/tegwiki/index.php/How-To_and_Shift_Info <B>Back one page</B>] | ||
| + | |||
| + | |||
| + | <B> Shift Leader Responsibilities </B> | ||
| + | |||
| + | * Communicate clearly and effectively with shift crews and MCC (7047), and log any status information to the [http://logbooks.jlab.org/book/halla HALOG] | ||
| + | |||
| + | * Keep track of [https://bta/ beam time accounting] | ||
| + | ** [[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. | ||
| + | |||
| + | * 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 [http://logbooks.jlab.org/book/halla 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 | ||
Revision as of 12:02, 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
- 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