Difference between revisions of "Run Group A"
Jump to navigation
Jump to search
| Line 100: | Line 100: | ||
*# Call the MM expert to turn the detector off | *# Call the MM expert to turn the detector off | ||
*# Call SVT expert to turn SVT off | *# Call SVT expert to turn SVT off | ||
| − | *# Turn off all the other detectors'''</font> | + | *# Turn off all the other detectors''' |
| + | </font> | ||
{| {{TableStyle1}} | {| {{TableStyle1}} | ||
| Line 121: | Line 122: | ||
*Set correct FSD thresholds for 50nA and then ask MCC to send 50 nA. | *Set correct FSD thresholds for 50nA and then ask MCC to send 50 nA. | ||
*Except for SVT, turn on HVs for all detectors. Call SVT expert to turn ON SVT.--> | *Except for SVT, turn on HVs for all detectors. Call SVT expert to turn ON SVT.--> | ||
| − | |||
<!-- | <!-- | ||
| Line 127: | Line 127: | ||
* Try to collect 100M events per run (make sure "ROL1 BLOCK_LVL is OK" in terminal bottom left corner before pushing "GO" button.). | * Try to collect 100M events per run (make sure "ROL1 BLOCK_LVL is OK" in terminal bottom left corner before pushing "GO" button.). | ||
--> | --> | ||
| − | |||
== '''Run Plan for Wednesday April 11 Day shift''' == | == '''Run Plan for Wednesday April 11 Day shift''' == | ||
* Continue data taking for production with with trigger_v12.trg @ 45nA 3 hours/run, make sure that the trigger rates are as expected. | * Continue data taking for production with with trigger_v12.trg @ 45nA 3 hours/run, make sure that the trigger rates are as expected. | ||
| − | |||
* If the machine is down for few hours ask for low current first 5 nA make sure that the beam is stable both in position and current, check that the rates are OK on all the detectors and halo counters. Then ask for 45 nA and continue data for production. If there are issues with the beam call the RC. | * If the machine is down for few hours ask for low current first 5 nA make sure that the beam is stable both in position and current, check that the rates are OK on all the detectors and halo counters. Then ask for 45 nA and continue data for production. If there are issues with the beam call the RC. | ||
* <font color=red>'''Please contact the Micromegas (BMT, FMT & FTT) expert if there are trips, or if you notice any issues in the online monitoring. Do not turn OFF or ON the MM only the expert can do that. See Log entry https://logbooks.jlab.org/entry/3556528 '''</font> | * <font color=red>'''Please contact the Micromegas (BMT, FMT & FTT) expert if there are trips, or if you notice any issues in the online monitoring. Do not turn OFF or ON the MM only the expert can do that. See Log entry https://logbooks.jlab.org/entry/3556528 '''</font> | ||
| − | |||
| − | |||
'''In case of other questions or uncertainties of what to do, please call the RC''' | '''In case of other questions or uncertainties of what to do, please call the RC''' | ||
Revision as of 14:44, 11 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: Valery Kubarovsky
- (757) 575-7540
- 9 575 7540 from Counting Room
- vpk@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.
- Note 5: In case of the Torus and/or Solenoid Fast Dump do the following:
- Notify MCC, request beam OFF and drop Hall status to Power Permit
- Call Engineering on-call
- Make separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" filed add Ruben Fair, Probir Goshal, Dave Kashy and esr-users@jlab.org
- Notify Run Coordinator
- Call the MM expert to turn the detector off
- Call SVT expert to turn SVT off
- Turn off all the other detectors
Run Plan:(last update 4/11 - 10:30)
Run Plan for Wednesday April 11 Day shift
In case of other 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
|
|
|
