Difference between revisions of "Run Group A"
Jump to navigation
Jump to search
Line 105: | Line 105: | ||
'''</font> | '''</font> | ||
− | === Updated Feb- | + | === Updated Feb-28, 18:10 === |
+ | Take data with the 40 nA beam | ||
+ | <-- | ||
* ''Sat Feb 23: Take data with 35 nA beam until Sergei creates the new trigger file'' | * ''Sat Feb 23: Take data with 35 nA beam until Sergei creates the new trigger file'' | ||
* ''When Sergei comes he will test the new trigger file with 50 nA beam '', if it works, then the plan for the weekend is to take production data with 50 nA beam. | * ''When Sergei comes he will test the new trigger file with 50 nA beam '', if it works, then the plan for the weekend is to take production data with 50 nA beam. | ||
Line 120: | Line 122: | ||
* ''' As soon a good beam is established (good harpscan, beam is centered in FTCalo), then turn on HV on detectors, and start taking data with trigger_v7 '''. | * ''' As soon a good beam is established (good harpscan, beam is centered in FTCalo), then turn on HV on detectors, and start taking data with trigger_v7 '''. | ||
* ''' We want to check whether we can go to a higher current 55 nA, and check whether DAQ is stable and livetime is around 90%, if it works, then we should keep the 55 nA beam current, otherwise we should go back to 50 nA ''' | * ''' We want to check whether we can go to a higher current 55 nA, and check whether DAQ is stable and livetime is around 90%, if it works, then we should keep the 55 nA beam current, otherwise we should go back to 50 nA ''' | ||
− | + | --> | |
<!-- | <!-- | ||
The beam position should be as indicated above. Make sure FSD thresholds are set correctly for whatever current is selected (refer to instructions in the "Establish-physics quality beam" procedure at [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]), integration time is set to 5 ms, and that the orbit locks are on. --> | The beam position should be as indicated above. Make sure FSD thresholds are set correctly for whatever current is selected (refer to instructions in the "Establish-physics quality beam" procedure at [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]), integration time is set to 5 ms, and that the orbit locks are on. --> |
Revision as of 18:09, 28 February 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, Winter 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: Nick Markov
- (757) 575-7540
- 9 575 7540 from Counting Room
- markov@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 2/20 - 1:15 AM)
Updated Feb-28, 18:10Take data with the 40 nA beam <--
-->
|
General Instructions:
Every Shift:
Every Run: Log screenshots of:
|
Webcams |
Manuals |
Epics on the web
|
Hall-B
Run lists |
Accelerator |
Bluejean meetings
|