Difference between revisions of "Best Practices/FAQ"
From Hall D Ops Wiki
(Created page with " = Best Practices = * run comments * logbook entries * https://halldweb.jlab.org/hdops/wiki/index.php/Beam_Line_Detectors_Shift#Radiator_Harp_Scan = FAQ = === What should...") |
(→Best Practices) |
||
| Line 2: | Line 2: | ||
= Best Practices = | = Best Practices = | ||
| − | * run | + | * '''Run Control''' |
| − | * | + | ** Every run should be begun starting at the "Configure" step in the Run Control GUI. |
| − | * https://halldweb.jlab.org/hdops/wiki/index.php/Beam_Line_Detectors_Shift#Radiator_Harp_Scan | + | ** Every run should have at least a brief descriptive comment entered, even those taken by experts performing tests. |
| + | *** Here is an example of a good comment for a production run: Radiator is JD70-119, PARA, Target Full, Mode 7, 200nA, 182 M events, good beam, occasional FSD trip, FCAL HV alarms, livetime ~90%, event rate ~ 30kHz, data rate ~600 MB/sec | ||
| + | * '''Logbook Entries''' | ||
| + | ** Each shift should have a summary entry where events and runs are logged, including all interactions with the MCC. Major events should also have their own log entries. A good example of a summary entry [https://logbooks.jlab.org/entry/3447161 is at this link]. | ||
| + | ** The summary logbook entry should have a summary of at minimum the production run taken during the shift along with the number of triggers in each run and the radiator information. | ||
| + | * Once per day a harp scan should be run following the directions [https://halldweb.jlab.org/hdops/wiki/index.php/Beam_Line_Detectors_Shift#Radiator_Harp_Scan at this link]. Note that the beam is expected to be Gaussian with sigmas in the range 0.6mm to ~1.2mm, but any action should be taken by the RC. | ||
= FAQ = | = FAQ = | ||
Revision as of 18:56, 28 January 2017
Best Practices
- Run Control
- Every run should be begun starting at the "Configure" step in the Run Control GUI.
- Every run should have at least a brief descriptive comment entered, even those taken by experts performing tests.
- Here is an example of a good comment for a production run: Radiator is JD70-119, PARA, Target Full, Mode 7, 200nA, 182 M events, good beam, occasional FSD trip, FCAL HV alarms, livetime ~90%, event rate ~ 30kHz, data rate ~600 MB/sec
- Logbook Entries
- Each shift should have a summary entry where events and runs are logged, including all interactions with the MCC. Major events should also have their own log entries. A good example of a summary entry is at this link.
- The summary logbook entry should have a summary of at minimum the production run taken during the shift along with the number of triggers in each run and the radiator information.
- Once per day a harp scan should be run following the directions at this link. Note that the beam is expected to be Gaussian with sigmas in the range 0.6mm to ~1.2mm, but any action should be taken by the RC.
FAQ
What should I do if I can't find an answer
If you have a question that is not answered by this wiki, first look to the whiteboard in the counting house. If that does not answer your question, ask the RC.
