Difference between revisions of "Run Group A"
Line 146: | Line 146: | ||
--> | --> | ||
− | * Take production data with trigger_v12_3.trg @ 50nA on LH2 target, 100 M per run (no longer than 3 hours) till Monday morning, April 30, | + | * Take production data with trigger_v12_3.trg @ 50nA on LH2 target, 100 M per run (no longer than 3 hours) till Monday morning, April 30 |
+ | |||
+ | * From around Monday 8am (April 30), beam studies is scheduled for about 8 hours. Please notify Ruben and enigneering on call, about the scheduled magnet studies. They are schedule to be in the counting house around 8:30. If not, notify them by phone. Youri and Latifa also needs access and please coordinate with them as well. | ||
+ | * April 30 swing shift: Most likely the beam studies will be done around 4pm, and if the magnets have been ramped back and MCC is ready, we need to reestablish the beam Please refer to the manual for procedures or call RC. Once good beam is established, we need to take various moller measurements for 3-4 hours. Please call beamline on-call (Stepan) and 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 50 nA and continue data for production. If there are issues with the beam call the RC. Sometimes MCC operator might ask to deliver tune beam --- please do not accept it. We need CW beam sent to the Faraday cup. If there is in deed a need for tune beam, it should be sent to the tagger dump with the tagger magent on. If you are uncertain, please call RC/PDL. | * 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 50 nA and continue data for production. If there are issues with the beam call the RC. Sometimes MCC operator might ask to deliver tune beam --- please do not accept it. We need CW beam sent to the Faraday cup. If there is in deed a need for tune beam, it should be sent to the tagger dump with the tagger magent on. If you are uncertain, please call RC/PDL. | ||
Line 153: | Line 156: | ||
* <font color=red>'''For RICH recovery procedures, please see Log entry https://logbooks.jlab.org/entry/3562273. This would apply in the cases of 1. DAQ crash: rich4 is not responding or 2. RICH alarms (LV,missing tile, temperature etc). If it does not work or you are uncertain about what to do, please contact the RICH expert on call '''</font> | * <font color=red>'''For RICH recovery procedures, please see Log entry https://logbooks.jlab.org/entry/3562273. This would apply in the cases of 1. DAQ crash: rich4 is not responding or 2. RICH alarms (LV,missing tile, temperature etc). If it does not work or you are uncertain about what to do, please contact the RICH expert on call '''</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:49, 27 April 2018
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: Lei Guo
- (757) 575-7540
- 9 575 7540 from Counting Room
- lguo@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.
The integrated rates on UPSTREAM counters has to be in the range 0-15 Hz (rates up 100 Hz are acceptable) and MIDSTREAM has to be in the rage 10-20 Hz (acceptable up to 50 Hz) @50 nA. Count rates in the range of hundreds or more may indicate bad beam tune or bleed-through from other Halls.
- Note 2: At the end of each run, follow the DAQ restart sequence
"end run", "cancel", "reset", then
if run ended correctly "download", "prestart", "iocjscalerRestartAll.sh", "go".
if run did not ended correctly, or ROCs had to be rebooted "Configure", "download", "prestart", "iocjscalerRestartAll.sh", "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: 2C24A (X=0.5,Y=0.5) , 2H01 (X=1.0 mm, Y=-1.0 mm) see log entry https://logbooks.jlab.org/entry/3560786.
- Note 4: Do not turn OFF FTOF HVs, even during the beam tune
- 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
- Note 6: When beam is being delivered to the Faraday Cup -
- the Fast Shut Down: Upstream, Midstream, Downstream, BOM and Solenoid should be always Unmasked,
- No changes to the FSD threshold without RC or beamline expert approval.
- Note 7: Do not turn on or off SVT - only SVT expert can do that
- Note 8: Any request for a special run or change of configuration has to be approved by RC & documented.
- Note 9: Check carefully BTA every hour and run script btaGet.py . It will print for you what HAS TO BE in BTA for this hour. Edit BTA if it is incorrect.
- Note 10: Reset CLAS12MON frequently to avoid histogram saturation.
Run Plan: April 25-30
|
General Instructions:
Every Shift:
Every Run: Log screenshots of:
|
Webcams |
Manuals |
Epics on the web
|
Hall-B
Run lists |
Accelerator |
Bluejean meetings
|