Difference between revisions of "Shift Leader"
From PREX Wiki
Jump to navigationJump to search| Line 32: | Line 32: | ||
* Communicate clearly and effectively with shift crews and MCC (7047) | * Communicate clearly and effectively with shift crews and MCC (7047) | ||
** arrive ~10 min. early to your shift to talk with the previous shift crew | ** arrive ~10 min. early to your shift to talk with the previous shift crew | ||
| − | ** | + | ** Answer the phone |
| + | ** Communicate with the RC | ||
* Consult the [[RunPlanDaily | Daily Run Plan]] and contact the [https://misportal.jlab.org/mis/apps/physics/shiftSchedule/index.cfm?experimentRunId=PREX/CREX run coordinator] whenever problems happen that cannot be solved by shift workers | * Consult the [[RunPlanDaily | Daily Run Plan]] and contact the [https://misportal.jlab.org/mis/apps/physics/shiftSchedule/index.cfm?experimentRunId=PREX/CREX run coordinator] whenever problems happen that cannot be solved by shift workers | ||
* Log any status information to the [http://logbooks.jlab.org/book/halla HALOG] (Make sure to log in!) | * Log any status information to the [http://logbooks.jlab.org/book/halla HALOG] (Make sure to log in!) | ||
Revision as of 10:45, 15 June 2019
| Quick Links |
| Experts on call |
| Hall A Tools |
| Set HRS magnets |
| Online analysis How-To |
| Starting CODA |
| Trouble-shooting the High Voltage GUI |
| BTA how-to |
| Shift Checklist Instructions |
| Full HOW TOs |
In the process of editing and updating this page. Please contact Juliette Mammei crowder@jlab.org with questions or suggestions.
PREX Main<< Information for Shift Takers
Shift Leader Responsibilities
- Communicate clearly and effectively with shift crews and MCC (7047)
- arrive ~10 min. early to your shift to talk with the previous shift crew
- Answer the phone
- Communicate with the RC
- Consult the Daily Run Plan and contact the run coordinator whenever problems happen that cannot be solved by shift workers
- Log any status information to the HALOG (Make sure to log in!)
- Maintain data taking quality and an efficient use of beam time
- Use Panguin to evaluate data quality
- Post Snapshots with HALOG 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
- Keep track of beam time accounting
- Follow the directives in the COO!
- Log the following in an end of shift summary in the HALOG:
- run list (describing the goal of this run: eg production on Pb, BCM calibration...) and report main statistic numbers
- any major events, including hall access (in addition to making log entries when they happen)
- Complete the Shift Checklist
