Difference between revisions of "Shift Leader"

From PREX Wiki
Jump to: navigation, search
(Shift Leader Responsibilities)
 
(5 intermediate revisions by 2 users not shown)
Line 30: Line 30:
  
 
== Shift Leader Responsibilities ==
 
== Shift Leader Responsibilities ==
 
+
* Calculate ABU's when in production mode by counting good Coulombs per run: 150uA each hour = 0.54C. 1hour runs. For each hour long run(s) take #good-Coulombs/0.54C = #ABU's  (even when running at a lower current, obsolete method: https://logbooks.jlab.org/entry/3785102)
 
* 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
Line 37: Line 37:
 
* 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!)
* Maintain data taking quality and an efficient use of beam time
+
* Maintain data taking quality and efficient use of beam time
 
** Use [[Panguin]] to evaluate data quality
 
** Use [[Panguin]] to evaluate data quality
 
* Post Snapshots with HALOG of important information at <B> least </B> twice a shift.  
 
* Post Snapshots with HALOG of important information at <B> least </B> twice a shift.  
Line 43: Line 43:
 
** Include any snapshots of the details after a change
 
** Include any snapshots of the details after a change
 
** Please feel free to post these Snapshots more often
 
** Please feel free to post these Snapshots more often
** Sample screenshots to make during shifts: collimator temp, Compton ion chambers, bpms, vacuums, parity controls, FFB, raster, ioc chamber
+
** Sample screenshots to make during shifts (examples below during no-beam conditions, purely descriptive): collimator temp, Compton ion chambers, bpms, vacuums, parity controls, FFB, raster, ioc chamber
*** [https://logbooks.jlab.org/entry/3716007]
+
*** [https://logbooks.jlab.org/entry/3822533 '''Collimator and Beamline temperatures''']
 +
*** [https://logbooks.jlab.org/entry/3822531 '''Hall A Beamline monitors''', and Compton and Moller magnets, and bleedthrough check] - useful for evaluating beam set up and tune
 +
*** [https://logbooks.jlab.org/entry/3822534 '''Ion Chambers''']
 +
*** [https://logbooks.jlab.org/entry/3822527 '''FFB system'''] - these examples show the system while inactive - check a more recent log entry with active FFB for a prescriptive example
 +
*** [https://logbooks.jlab.org/entry/3822525 '''Hall A Raster''']
 +
*** [https://logbooks.jlab.org/entry/3822524 '''Hall A Tools, magnets''']
 +
*** [https://logbooks.jlab.org/entry/3822472 '''Hall A Target status''']
 +
*** [https://logbooks.jlab.org/entry/3822540 '''Scaler GUI''']
 +
*** [https://logbooks.jlab.org/entry/3822545 Injector Loss Monitor] - useful for diagnosing large Aq widths and noise problems
 +
*** [https://logbooks.jlab.org/entry/3822543 Charge Feedback Monitor]
 +
*** [https://logbooks.jlab.org/entry/3822542 Compton]
 +
*** [https://logbooks.jlab.org/entry/3822541 Target motion and mask]
 +
*** [https://logbooks.jlab.org/entry/3822538 Beamline Vacuum]
 +
*** [https://logbooks.jlab.org/entry/3822536 Parity Controls]
 
* Keep track of [https://bta/ beam time accounting]
 
* Keep track of [https://bta/ beam time accounting]
 
* Follow the directives in the [http://hallaweb.jlab.org/index/safety-docs/current/ COO!]
 
* Follow the directives in the [http://hallaweb.jlab.org/index/safety-docs/current/ COO!]
Line 51: Line 64:
 
** any major events, including hall access (in addition to making log entries when they happen)
 
** any major events, including hall access (in addition to making log entries when they happen)
 
* Complete the [https://logbooks.jlab.org/checklists/293 Shift Checklist] at the <b>beginning of the shift</b> - see [[Shift_Checklist|Instructions]]
 
* Complete the [https://logbooks.jlab.org/checklists/293 Shift Checklist] at the <b>beginning of the shift</b> - see [[Shift_Checklist|Instructions]]
 +
** Note: There is a convenient script in ~/cameronc/SL/auto-SL.sh which will walk you through the steps of the shift checklist and provide easily copyable text-outputs for easy entry into the checklist and comparison with expectations
 
* Print off additional run sheets (printer "chax"): https://logbooks.jlab.org/entry/3700479
 
* Print off additional run sheets (printer "chax"): https://logbooks.jlab.org/entry/3700479
 
* A PREX analysis shift worker will be on hand for most shifts (although not required by the COO) to help out in high demand situations. Please coordinate with them as well.
 
* A PREX analysis shift worker will be on hand for most shifts (although not required by the COO) to help out in high demand situations. Please coordinate with them as well.

Latest revision as of 10:02, 8 August 2020

Quick Links
Experts on call
Hall A Tools
Set HRS magnets
Online analysis How-To
Using CODA
Trouble-shooting the High Voltage GUI
BTA how-to
Shift Checklist Instructions
Full HOW TOs

PREX Main<< Information for Shift Takers


Useful links

Shift Leader Responsibilities

  • Calculate ABU's when in production mode by counting good Coulombs per run: 150uA each hour = 0.54C. 1hour runs. For each hour long run(s) take #good-Coulombs/0.54C = #ABU's (even when running at a lower current, obsolete method: https://logbooks.jlab.org/entry/3785102)
  • 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 efficient use of beam time
    • Use Panguin to evaluate data quality
  • Post Snapshots with HALOG of important information at least twice a shift.
  • 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 at the beginning of the shift - see Instructions
    • Note: There is a convenient script in ~/cameronc/SL/auto-SL.sh which will walk you through the steps of the shift checklist and provide easily copyable text-outputs for easy entry into the checklist and comparison with expectations
  • Print off additional run sheets (printer "chax"): https://logbooks.jlab.org/entry/3700479
  • A PREX analysis shift worker will be on hand for most shifts (although not required by the COO) to help out in high demand situations. Please coordinate with them as well.
  • Read Common Problems for information on how to deal with common issues cropping up