Difference between revisions of "Information for Shift Takers"
From HallCWiki
Jump to navigationJump to search (→Your Responsibilities: Updated priorities for Summer 2019 running) |
|||
| Line 20: | Line 20: | ||
* Communicate clearly and effectively with shift crews and MCC (7047), and log any status information to the [https://logbooks.jlab.org/book/hclog HCLOG] | * Communicate clearly and effectively with shift crews and MCC (7047), and log any status information to the [https://logbooks.jlab.org/book/hclog 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 | * 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 titled "X Shift Summary" where X = Day, Swing, Owl | ** This is done by starting the summary as a log entry titled "X Shift Summary" where X = Day, Swing, Owl | ||
** '''Save & edit''' the summary after '''ANY''' event of interest occurs | ** '''Save & edit''' the summary after '''ANY''' event of interest occurs | ||
** This provides the readers with an up-to-date play by play of the current shift | ** This provides the readers with an up-to-date play by play of the current shift | ||
| + | ** You should also log any major events, including accesses | ||
** See example: https://logbooks.jlab.org/entry/3402742 | ** See example: https://logbooks.jlab.org/entry/3402742 | ||
| − | + | * Record the purpose for <span style="text-decoration:underline;">every</span> single run in the "Run list" binders. Blank forms for Fall 2018 can be found [http://lichen.phys.uregina.ca/~huberg/kaon/?C=M;O=D here]. | |
* Keep track of [https://bta/ beam time accounting] | * Keep track of [https://bta/ beam time accounting] | ||
** More information how to work the [[Beam Time Accounting (BTA)]] web app | ** More information how to work the [[Beam Time Accounting (BTA)]] web app | ||
| − | * Consult the [[RC daily meetings and daily runplan | + | * Consult the [[RC daily meetings and daily runplan summer 2019|daily run plans]] and communicate with the [https://misportal.jlab.org/mis/physics/shiftSchedule/?experimentRunId=HALLC-SPRING-2019 RC] 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. | ||
* 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]. | ||
| − | |||
| − | |||
| − | |||
| − | |||
=== Target Operator === | === Target Operator === | ||
* Watch the target, see [https://userweb.jlab.org/~smithg/target/Qweak/#_12_GeV_Era Target Info] | * Watch the target, see [https://userweb.jlab.org/~smithg/target/Qweak/#_12_GeV_Era Target Info] | ||
| − | + | * Start and stop the DAQ. Ensure the correct PS factors are being used. | |
* Assist the shift leader and third person with their duties | * Assist the shift leader and third person with their duties | ||
| Line 51: | Line 48: | ||
** If there are any alarms being ignored or silenced, find out why and enter this in the logbook. | ** If there are any alarms being ignored or silenced, find out why and enter this in the logbook. | ||
** Log any alarms when they occur. | ** Log any alarms when they occur. | ||
| − | * | + | * Carry out online analysis of the data, including 50k replays for the HMS and SHMS |
| − | * | + | ** Compare 50k replay histograms with the sample ones and report to shift leader any unexplained differences. Hclog them. |
| − | * Compare replay histograms with the sample ones and report to shift leader any unexplained differences. Hclog them. | + | ** For the Pion Electroproduction experiment analysis instructions see [https://hallcweb.jlab.org/wiki/index.php/Pion-LT_analysis_instructions here]. |
* Fill [https://misportal.jlab.org/mis/apps/physics/shiftChecklist/index.cfm?shiftChecklistTypeId=2 shift checklist] once per shift. | * Fill [https://misportal.jlab.org/mis/apps/physics/shiftChecklist/index.cfm?shiftChecklistTypeId=2 shift checklist] once per shift. | ||
** '''An older Shift Checklist file, which also includes help for locating items, should be available [https://hallcweb.jlab.org/document/Checklist/CurrentChecklist.pdf here].''' | ** '''An older Shift Checklist file, which also includes help for locating items, should be available [https://hallcweb.jlab.org/document/Checklist/CurrentChecklist.pdf here].''' | ||
Revision as of 13:40, 12 June 2019
Counting house: 6000(*), 5503, 6666 | Run coordinator: 757-270-8916 | MCC: 7047(*), 7046, 7048 | Crew chief: 7045 | Guard house: 8522
Before the start of your shift: read and understand the Safety Documentation 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
- RC daily meetings and daily run plan for Summer 2019
- Run plans for all energies on Redmine
- Experts on call
- Beam Time Accounting quick link
- Shift Checklist quick link
Your Responsibilities
Shift Leader
- Communicate clearly and effectively with shift crews and MCC (7047), 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 titled "X Shift Summary" where X = Day, Swing, Owl
- Save & edit the summary after ANY event of interest occurs
- This provides the readers with an up-to-date play by play of the current shift
- You should also log any major events, including accesses
- See example: https://logbooks.jlab.org/entry/3402742
- Record the purpose for every single run in the "Run list" binders. Blank forms for Fall 2018 can be found here.
- Keep track of beam time accounting
- More information how to work the Beam Time Accounting (BTA) web app
- Consult the daily run plans and communicate with the RC 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.
Target Operator
- Watch the target, see Target Info
- Start and stop the DAQ. Ensure the correct PS factors are being used.
- Assist the shift leader and third person with their duties
Third person
- Make certain that the Hall-C Alarm Handler process is running. See Hall_C_Alarm_Handler.
- If there are any alarms being ignored or silenced, find out why and enter this in the logbook.
- Log any alarms when they occur.
- Carry out online analysis of the data, including 50k replays for the HMS and SHMS
- Compare 50k replay histograms with the sample ones and report to shift leader any unexplained differences. Hclog them.
- For the Pion Electroproduction experiment analysis instructions see here.
- Fill shift checklist once per shift.
- An older Shift Checklist file, which also includes help for locating items, should be available here.
