Difference between revisions of "Run Group A"
Jump to navigation
Jump to search
Line 98: | Line 98: | ||
== <font color=blue>''' Run Plan:'''</font>== | == <font color=blue>''' Run Plan:'''</font>== | ||
− | ''(last update 4/ | + | ''(last update 4/04- 19:00)'' |
*<font color=red> '''When beam to Faraday Cup the Fast Shut Down: Upstream, Midstream, Downstream, BOM and Solenoid should be always Unmasked ''' | *<font color=red> '''When beam to Faraday Cup the Fast Shut Down: Upstream, Midstream, Downstream, BOM and Solenoid should be always Unmasked ''' | ||
− | *'''Always monitor the rates on the Halo counters when they are tuning beam to the other halls''' | + | *'''Always monitor the rates on the Halo counters when they are tuning the beam to hall B or to the other halls''' |
* '''Do Not turn on or off SVT only SVT expert can do that''' | * '''Do Not turn on or off SVT only SVT expert can do that''' | ||
* '''Any request for special run change of configuration has to be approved by RC & documented''' | * '''Any request for special run change of configuration has to be approved by RC & documented''' | ||
Line 119: | Line 119: | ||
--> | --> | ||
− | + | == '''Run Plan for Wednesday April 4 and Thursday April 5:''' == | |
− | |||
− | |||
+ | * Continue to take production data with <b>trigger_6gev.trg</b> at 20nA | ||
+ | * Stop the run if it reached 100M events or 3 hours duration. | ||
+ | * <b>Note to shift leader:</b> please include relevant links for runs/events to your logbook summary, like here: https://logbooks.jlab.org/entry/3553286 | ||
− | + | <font color=red>'''In case of questions or uncertainties of what to do, please call the RC'''</font> | |
Line 200: | Line 201: | ||
<!-- * If the machine is down and it is back start with low current first (2nA and 5 nA) making sure that the beam is stable in current and position before moving to 30 nA | <!-- * If the machine is down and it is back start with low current first (2nA and 5 nA) making sure that the beam is stable in current and position before moving to 30 nA | ||
--> | --> | ||
− | |||
Revision as of 18:10, 4 April 2018
[edit]
Shift ScheduleShift ChecklistHot CheckoutBeam Time Accounting
|
Manuals |
Procedures |
JLab Logbooks
|
If calling local numbers (with area code prefix 757) from the counting room dial 9+[last 7 digits]. To call other area codes dial 91+[10 digit number]
|
|
- Note, all non-JLab numbers must be dialed with an area code. When calling from a counting-house landline, dial "9" first.
- To call JLab phones from outside the lab, all 4-digit numbers must be preceded by 757-269
- Click Here to edit Phone Numbers. Note, you then also have to edit the current page to force a refresh.
Click Here to edit Phone Numbers. Note, you then also have to edit this page to force a refresh.
CLAS12 Run Group A, Spring 2018
Beam energy 10.6 GeV (5 pass)
Important: Document all your work in the logbook!
Remember to fill in the run list at the beginning and end of each run (clas12run@gmail.com can fill the run list)
RC: Andrey Kim
- (757) 575-7540
- 9 575 7540 from Counting Room
- kenjo@jlab.org
PDL: Eugene Pasyuk
- (757) 876-1789
- 9 876-1789 from Counting Room
- pasyuk@jlab.org
- Note 1: Be very mindful of the background rates in the halo counters, rates in the detectors, and currents in the SVT for all settings to ensure that they are at safe levels.
- Note 2: At the end of each run, follow the DAQ restart sequence "end run", "abort", "reset", "download", "prestart", "go". After DAQ prestart is complete reboot the scaler IOCs with the command: iocjscalerRestartAll.sh. Note: After each step, make sure it is complete in the Run Control message window. If a roc has crashed, find which one it is and issue a roc_reboot command and try again. Contact the DAQ expert if there are any questions.
- Note 3: Nominal beam positions: 2H01 (X=1.0 mm, Y=-1.5 mm)
- Note 4: With beam to the Faraday Cup, typical rates on all halo counters upstream from the target should be either 0 or of the order of few counts. Count rates in the range of tens or more may indicate bad beam tune or bleed-through from other Halls.
Run Plan:(last update 4/04- 19:00)
Run Plan for Wednesday April 4 and Thursday April 5:
In case of questions or uncertainties of what to do, please call the RC
|
General Instructions:
Every Shift:
Every Run: Log screenshots of:
|
Webcams |
Manuals |
Epics on the web
|
Hall-B
Run lists |
Accelerator |
Bluejean meetings
|