Difference between revisions of "Shift-taker responsibilities"

From Hall A Wiki
Jump to: navigation, search
(Target Operator)
 
(12 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
Counting house: 5501 & 5507 | Run coordinator: 876-1787 | MCC: 7046 & 7047 & 7048 | Crew chief: 7045 | Guard house: 8522
 
Counting house: 5501 & 5507 | Run coordinator: 876-1787 | MCC: 7046 & 7047 & 7048 | Crew chief: 7045 | Guard house: 8522
  
Before the start of your shift: read, understand and sign the [https://hallaweb.jlab.org/index/safety-docs/current/ safety documentation] of the experiments.
+
Before the start of your shift: read, understand and sign the safety document in the counting house (Yellow binder). Online version available from [https://hallaweb.jlab.org/index/safety-docs/current/ safety documentation]
  
Very detailed instructions are available in the [[Complete How-To]] and [[How to HRS/DVCS]].  If you encounter problems, first look at those instructions for assistance.
+
Very detailed instructions are available in the [[Complete How-To]] and [https://hallaweb.jlab.org/wiki/index.php/How_to_HRS_/_DVCS How-to from DVCS experiments].  If you encounter problems, first look at those instructions for assistance.
  
 
__NOTOC__
 
__NOTOC__
Line 14: Line 14:
 
=== Shift Leader ===
 
=== Shift Leader ===
  
* Communicate clearly and effectively with shift crews and MCC (7047), and log any status information to the [http://logbooks.jlab.org/book/halla HALOG]
+
* Main point of contact between Run Coordinator/MCC and Shift workers.
  
* Keep track of [https://bta/ beam time accounting]
+
* Log any status information to the [http://logbooks.jlab.org/book/halla HALOG]
 +
 
 +
* Keep track of [https://bta/ beam time accounting(BTA)]
  
 
* Consult the [[Daily Run Plans|daily run plans]] and communicate with [https://misportal.jlab.org/mis/apps/physics/shiftSchedule/index.cfm?experimentRunId=APEX run coordinator] whenever problems happen that cannot be solved by shift workers.
 
* Consult the [[Daily Run Plans|daily run plans]] and communicate with [https://misportal.jlab.org/mis/apps/physics/shiftSchedule/index.cfm?experimentRunId=APEX run coordinator] whenever problems happen that cannot be solved by shift workers.
Line 26: Line 28:
 
* Log the following in a shift summary in the [http://logbooks.jlab.org/book/halla HALOG]:
 
* 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, optics calibration, ...) and report main statistic numbers
 
** run list (describing the goal of this run: eg production, optics calibration, ...) and report main statistic numbers
 
 
** any major events, including accesses
 
** any major events, including accesses
  
 
=== Target Operator ===
 
=== Target Operator ===
 +
* [https://hallaweb.jlab.org/wiki/index.php/APEX_Target APEX Target]
  
* Use the target mover gui as required to change targets (see '''TO ADD: TARGET GUI LAUNCH INSTRUCTIONS AND SCREENSHOT''')
+
* Use the target mover gui as required to change targets ([https://hallaweb.jlab.org/index/safety-docs/current/TargetOperators/apextgt_v5_12feb2019.pdf TO instruction])
  
* Start and stop the DAQ. Record the purpose  for <span style="text-decoration:underline;">every</span> single run in the "Run list" binders. Read [[https://hallaweb.jlab.org/wiki/index.php/How_to_HRS_/_DVCS#Blank_lists_.28shift_check_list.2C_run_list.2C_compton_run_list.29 this]] to create more blank forms.
+
* Post target status, strip charts to halog once per shift
  
* Online replay of '''all''' production runs (twice), as described in [[How to HRS / DVCS#Data analysis|the online data analysis instructions]]. first replay the first 50 k events, check online plots (see next bullet), then run a full replay.
+
* Start and stop the DAQ. Record the purpose for <span style="text-decoration:underline;">every</span> single run in the "Run list" binders. Read [[https://hallaweb.jlab.org/wiki/index.php/How_to_HRS_/_DVCS#Blank_lists_.28shift_check_list.2C_run_list.2C_compton_run_list.29 this]] to create more blank forms.
 +
 
 +
* Online replay of '''all''' production runs (twice), as described in [[APEX online analysis|the online data analysis instructions]]. first replay the first 50 k events, check online plots (see next bullet), then run a full replay.
  
 
* Compare replay histograms with the sample ones and report to shift leader any unexplained differences. Halog them.
 
* Compare replay histograms with the sample ones and report to shift leader any unexplained differences. Halog them.
  
* Fill shift checklist once per shift (for guidance, please see the  checklist how-to).  [[https://hallaweb.jlab.org/wiki/index.php/How_to_HRS_/_DVCS#Blank_lists_.28shift_check_list.2C_run_list.2C_compton_run_list.29 go here to find blank copies of the shift check list and the shift check list how to]]
+
* Fill shift checklist once per shift [[https://logbooks.jlab.org/checklists/293 shift check list]].
  
 
* The shift leader can help.
 
* The shift leader can help.
 +
 +
=== Quick link / instruction ===
 +
* [https://wiki.jlab.org/tegwiki/index.php/HALLAtools  Hall A Tools]
 +
* [[How to set HRS magnets]]
 +
* [[APEX online analysis | Online analysis ]]

Latest revision as of 21:23, 12 February 2019

Back to How-To and shift info


Counting house: 5501 & 5507 | Run coordinator: 876-1787 | MCC: 7046 & 7047 & 7048 | Crew chief: 7045 | Guard house: 8522

Before the start of your shift: read, understand and sign the safety document in the counting house (Yellow binder). Online version available from safety documentation

Very detailed instructions are available in the Complete How-To and How-to from DVCS experiments. If you encounter problems, first look at those instructions for assistance.


Your Responsibilities

Shift Leader

  • Main point of contact between Run Coordinator/MCC and Shift workers.
  • Log any status information to the HALOG
  • 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, optics calibration, ...) and report main statistic numbers
    • any major events, including accesses

Target Operator

  • Use the target mover gui as required to change targets (TO instruction)
  • Post target status, strip charts to halog once per shift
  • Start and stop the DAQ. Record the purpose for every single run in the "Run list" binders. Read [this] to create more blank forms.
  • Online replay of all production runs (twice), as described in the online data analysis instructions. first replay the first 50 k events, check online plots (see next bullet), then run a full replay.
  • Compare replay histograms with the sample ones and report to shift leader any unexplained differences. Halog them.
  • The shift leader can help.

Quick link / instruction