Difference between revisions of "Information for Shift Takers"

From HallCWiki
Jump to navigationJump to search
 
(106 intermediate revisions by 16 users not shown)
Line 1: Line 1:
Counting house: 5503, 6666 & 6000 | Run coordinator: 270-8916 | MCC: 7046 & 7047 & 7048 | Crew chief: 7045 | Guard house: 8522
 
  
Before the start of your shift: read and understand the [https://hallcweb.jlab.org/safety-docs/current/ Safety Documentation] for this experiment.
+
Counting house: 6000(*), 5503, 6666 | Run coordinator: 757-270-8916 | MCC: 7047(*), 7046, 7048 | Crew chief: 7045 | Guard house: 8522
* '''You must then sign in the Yellow Binder in the Hall C Counting House!'''
 
  
Detailed instructions are available on the [[How-to]] pageIf you encounter problems, first look at those instructions for assistance.
+
Before the start of your shift: read and understand the Safety Documentation (either hard copy, or from the [https://www.jlab.org/physics/hall-c Hall C Main Page] for this experiment'''You must then sign in the Yellow Binder in the Hall C Counting House!'''
  
__NOTOC__
+
----
 +
<span style="color: orange; font-size: 200%;">
 +
Detailed instructions for Shift Takers are available on the '''[[How-to]]''' page.<br>
 +
If you encounter problems, look first at those instructions for assistance.<br>
 +
</span>
 +
----
 +
 
 +
== Current Run Plans ==
 +
*[[Experts on call]]
 +
*[https://bta.acc.jlab.org/ Beam Time Accounting quick link]
 +
** Read Section III of [https://ace.jlab.org/cdn/doc/btm/userguide.pdf BTM Users Guide] to learn distinctions of BNA/ACC/OFF
 +
*[https://misportal.jlab.org/mis/apps/physics/shiftChecklist/index.cfm?shiftChecklistTypeId=2 Shift Checklist quick link]
 +
**[[Shift Checklist Help]]
 +
*[https://hallcweb.jlab.org/live_status/snapshots_controls/ Hall C Live Status (NPS updated)]
 +
 
 +
__TOC__
  
 
== Your Responsibilities ==
 
== 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 ===
 
=== 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 (7047), and log any status information to the [https://logbooks.jlab.org/book/hclog HCLOG]
+
<!-- * [[Media:SL_cheat_sheet.pdf|Shift Leader "Cheat Sheet" (PDF)]], [[Media:SL_cheat_sheet.odp|(Libreoffice original)]]  (For Pol He3 Run Group) -->
 
+
* Communicate clearly and effectively with shift crews and MCC (7046,7047 or 7048), 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 
 +
** 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 <span style="text-decoration:underline;">every</span> 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 using this link [[Media:Runsheet_dvcs_NPS.pdf |RunSheets ]]
 
* Keep track of [https://bta/ beam time accounting]
 
* Keep track of [https://bta/ beam time accounting]
 +
** More information on how to work the [[Beam Time Accounting (BTA)]] web app
 +
** Make use of the beam time accounting helper gui: "go_bta_config"
 +
*** This will allow you to set the beam current threshold for beam available, set whether the experiment is ready, down, or performing a configuration change
  
* Consult the [[RC_daily_meetings_and_daily_runplan|daily run plans]] and communicate with [https://misportal.jlab.org/mis/physics/shiftSchedule/?experimentRunId=HALLC-COMMISSIONING Run Coordinator] whenever problems happen that cannot be solved by shift workers.
+
* 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.  
 
* Maintain data taking quality and an efficient use of beam time.  
Line 22: Line 49:
 
* 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].
  
* Log the following in a shift summary in the [https://logbooks.jlab.org/book/hclog Hall C Logbook]:
+
* The shift lead is responsible for '''running the analysis''':
** run list (describing the goal of this run: eg production on LH2, BCM calibration...) and report main statistic numbers
+
** Start and stop runs in coda
 
+
** Reviewing 50k replays
** any major events, including accesses
+
** Run the full replays and electron counts. 
 +
** See: [https://hallcweb.jlab.org/wiki/index.php/NPS_Online_analysis_(Fall_2023)  NPS_Online_analysis_(Fall_2023)]
  
 
=== Target Operator ===
 
=== Target Operator ===
 +
<!--
 +
-->
 +
* Watch the target, see [[https://userweb.jlab.org/~smithg/target/Qweak/#_12_GeV_Era]]
 +
* 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
 +
** See: [https://hallcweb.jlab.org/wiki/index.php/NPS_Online_analysis_(Fall_2023) NPS_Online_analysis_(Fall_2023)]
  
* Watch the target, see [https://userweb.jlab.org/~smithg/target/Qweak/#_12_GeV_Era Target Info]
+
=== Expert Person ===
 
+
* Carry out online analysis of the data, communicate results and any issues with the shift leader/experts as required.
* Assist the shift leader and third person with their duties
+
** See: [https://hallcweb.jlab.org/wiki/index.php/NPS_Online_analysis_(Fall_2023) NPS_Online_analysis_(Fall_2023)]
  
 +
<!--
 
=== Third person ===
 
=== Third person ===
  
* Start and stop the DAQ. Record the purpose  for <span style="text-decoration:underline;">every</span> single run in the "Run list" binders. Read [[fixme]] to create more blank forms.
+
* 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.  
* Online replay of '''all''' production runs (twice), as described in [[fixme]]. first replay the first 50 k events, check online plots (see next bullet), then run a full replay.
+
** Log any alarms when they occur.
 
+
* Carry out online analysis of the data, communicate results and any issues with the shift leader/experts as required.
* Compare replay histograms with the sample ones and report to shift leader any unexplained differences. Hclog them.
+
** See: [https://hallcweb.jlab.org/wiki/index.php/Pion-LT_analysis_instructions Pion-LT Analysis Instructions]
 
+
* Fill [https://misportal.jlab.org/mis/apps/physics/shiftChecklist/index.cfm?shiftChecklistTypeId=2 shift checklist] once per shift.
* Fill  shift checklist once per shift (for guidance, please see the  checklist how-to).  [[fixme go here to find blank copies of the shift check list and the shift check list how to]]
+
** [[Shift Checklist Help]]
 
+
-->
* The shift leader or TO can help.
+
=== Instructions and How-to's for common problems ===
 
+
* [[How-to|Hall C "How-to" Pages]]
=== [[How-to|How To's]]: Instructions and How-to's for common problems ===
 
 
 
=== [http://hallaweb.jlab.org/12GeV/experiment/E12-07-108/shift_worker_info/Howtoes_updated.html GMP How To's] ===
 
=== [https://misportal.jlab.org/mis/physics/shiftSchedule/?experimentRunId=HALLC-COMMISSIONING Shift Schedule] ===
 

Latest revision as of 14:25, 26 September 2023

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 (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

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 using this link RunSheets
  • Keep track of beam time accounting
    • More information on how to work the Beam Time Accounting (BTA) web app
    • Make use of the beam time accounting helper gui: "go_bta_config"
      • This will allow you to set the beam current threshold for beam available, set whether the experiment is ready, down, or performing a configuration change
  • 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.
  • The shift lead is responsible for running the analysis:

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

Instructions and How-to's for common problems