Difference between revisions of "Information for Shift Takers"
From HallCWiki
(→Your Responsibilities) |
(→Shift Leader) |
||
Line 46: | Line 46: | ||
* Follow the directives in the [https://hallcweb.jlab.org/safety-docs/current/COO.pdf COO] and associated [https://hallcweb.jlab.org/safety-docs/current/ Safety Documentation]. | * Follow the directives in the [https://hallcweb.jlab.org/safety-docs/current/COO.pdf COO] and associated [https://hallcweb.jlab.org/safety-docs/current/ Safety Documentation]. | ||
− | * When taking single-arm data in both arms, the shift lead is responsible for '''running | + | * When taking single-arm data in both arms, the shift lead is responsible for '''running HMS analysis''': |
** Start and stop HMS runs in coda | ** Start and stop HMS runs in coda | ||
** Reviewing HMS 50k replays | ** Reviewing HMS 50k replays |
Revision as of 14:22, 30 September 2022
Counting house: 6000(*), 5503, 6666 | Run coordinator: 757-270-8916 | MCC: 7047(*), 7046, 7048 | Crew chief: 7045 | Guard house: 8522 | Regina Virtual Counting House: 6613
Before the start of your shift: read and understand the Safety Documentation (either hard copy, or from the Hall C Main Page for this experiment.
- You must then sign in the Yellow Binder in the Hall C Counting House!
Detailed instructions for Shift Takers are available on the How-to page.
If you encounter problems, look first at those instructions for assistance.
Current Run Plans
Contents
Your Responsibilities
The tasks listed below are not set in stone, you should use your own judgement and initiative. You should assist other shift workers in their tasks as needed.
Shift Leader
NOTE: The Shift Leader is also responsible for the 3rd Person duties below. You can ask the TO for help too.
- Communicate clearly and effectively with shift crews and MCC (7046,7047 or 7048), and log any status information to the HCLOG
- Follow the run plan and co-ordinate switching to the next experimental configuration with other shift workers and the MCC as required.
- Maintain and update the Shift Summary detailing the events which occur while on shift
- This is done by starting the summary as a log entry (from web browser, NOT gui) entitled "X Shift Summary" where X = Day, Swing, Owl
- Save & edit the summary after ANY event of interest occurs, including accesses
- This provides the readers with an up-to-date play by play of the current shift
- See example: https://logbooks.jlab.org/entry/3402742
- Record the purpose for every single run in the "Run list" binders (if available).
- Use the new configuration sheets for the first set of runs on any new setting.
- There are extra copies on the table in the middle of the counting house, if you run out the pdfs can be found here
- Keep track of beam time accounting
- More information on how to work the Beam Time Accounting (BTA) web app
- Consult the Run Plan and communicate with the 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 and associated Safety Documentation.
- When taking single-arm data in both arms, the shift lead is responsible for running HMS analysis:
- Start and stop HMS runs in coda
- Reviewing HMS 50k replays
- Run the full replays and electron counts.
- See: XEM Analysis Instructions
Target Operator
- Watch the target, see [[1]]
- Start and stop the SHMS/COIN DAQ. Ensure the correct PS factors are being used.
- Consult the run plan for estimated PS factors to be used for a given setting, adjust these up or down as needed
- Carry out 50k replays for the SHMS DAQ (For COIN DAQ run shms and hms 50k scripts)
- Compare 50k replay histograms with the sample ones and report to shift leader any unexplained differences. Hclog them.
- Assist the shift leader and third person with their duties
Expert Person
- Carry out online analysis of the data, communicate results and any issues with the shift leader/experts as required.