Difference between revisions of "Ar(ee'p)"
From Hall A Wiki
(→Shift Workers) |
(→Shift Workers) |
||
Line 49: | Line 49: | ||
==Shift Workers== | ==Shift Workers== | ||
+ | Counting house: 5501 & 5507 | Run coordinator: 876-1787 | MCC: 7046 & 7047 & 7048 | Crew chief: 7045 | Guard house: 8522 | ||
+ | == Your Responsibilities == | ||
+ | Before the start of your shift: read, understand and sign the [https://hallaweb.jlab.org/wiki/index.php/Shift_safety_documents safety documentation] of the experiments. | ||
+ | === 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] | ||
+ | |||
+ | * Keep track of [https://bta/ beam time accounting] | ||
+ | |||
+ | * Consult the [[daily run plans]] and communicate with [ 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 | ||
+ | |||
+ | * 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 on LH2, BMC calibration...) and report main statistic numbers | ||
+ | |||
+ | ** any major events, including accesses | ||
+ | |||
+ | === Target Operator === | ||
+ | |||
+ | * Watch the target, see [[http://hallaweb.jlab.org/equipment/targets/cryotargets/Halla_tgt.html Target Info]] | ||
+ | |||
+ | * Assist the shift leader and third person with their duties | ||
+ | |||
+ | === 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 [[ this]] to create more blank forms. | ||
+ | |||
+ | * Online replay of '''all''' production runs (twice), as described in [[https://hallaweb.jlab.org/wiki/index.php/Ar%28ee'p%29#Replay_data|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. | ||
+ | |||
+ | * Fill shift checklist once per shift (for guidance, please see the checklist how-to). [[checklist go here to find blank copies of the shift check list and the shift check list how to]] | ||
+ | |||
+ | |||
+ | * The shift leader or TO can help. | ||
==Links== | ==Links== | ||
[[Ar(ee'p) DAQ]] | [[Ar(ee'p) DAQ]] |
Revision as of 16:55, 15 February 2017
Contents
General
Analysis
DAQ
How to taking Data
Start Coda
- How to run DAQ
- From a terminal login as "adaq2" machine (do "ssh adaq@adaq2" without the quotes)
- Password is available on the white board
- After login to adaq2, type "startcoda" to bring up the runcontrol GUI
- The default configuration is "coincidence", if it is not loaded you can choose it from the menu "configurations->Cool", select "coincidence"
- Click "Platform->connect"
- Click on "Download" button
- Click on "Start (>>)" button, and acknowledge "start-of-run" pop-up window
- To end a run click on "End" button
- How to kill coda processes
- At the terminal of adaq2, type "kcoda"
- How to setup the Prescale
- We just use PrescaleR for Ar experiment.
login as "adaq" on "adaq2" machine type "prescaleR &" to open the GUI set desired prescale factors and click "Save" and Exit
Replay data
- From a terminal login as aonl machine ( do "ssh a-onl" without the quotes)
- Password is available on the white board
- After login to a-onl, type gotritium, then Type
analyzer .x replay_coinc.C runnumber (You can see the run number from CODA GUI)
Online GUI
(Last updated: February 15th 2017)
Once the run has been replayed (see instructions above), login to aonl1, aonl2, aonl3, or aonl4 as user a-onl (password on the white board) and do
$ gotritium [] onlineLHRS [] onlineRHRS
The output files are stored under adaq1/data1/Ar40_[run number].root
Shift Workers
Counting house: 5501 & 5507 | Run coordinator: 876-1787 | MCC: 7046 & 7047 & 7048 | Crew chief: 7045 | Guard house: 8522
Your Responsibilities
Before the start of your shift: read, understand and sign the safety documentation of the experiments.
Shift Leader
- Communicate clearly and effectively with shift crews and MCC (7047), and log any status information to the HALOG
- Keep track of beam time accounting
- Consult the daily run plans and communicate with [ 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
- Log the following in a shift summary in the HALOG:
- run list (describing the goal of this run: eg production on LH2, BMC calibration...) and report main statistic numbers
- any major events, including accesses
Target Operator
- Watch the target, see [Target Info]
- Assist the shift leader and third person with their duties
Third person
- 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 [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.
- Fill shift checklist once per shift (for guidance, please see the checklist how-to). checklist go here to find blank copies of the shift check list and the shift check list how to
- The shift leader or TO can help.