Difference between revisions of "Run Group A"
Jump to navigation
Jump to search
Line 134: | Line 134: | ||
** Look carefully int Halo counters, all halo counters upstream of the target are counting less than 10 Hz | ** Look carefully int Halo counters, all halo counters upstream of the target are counting less than 10 Hz | ||
** Look into FT Calo scaler screen, which is the main measure how the beam is centered, for reference look https://logbooks.jlab.org/entry/3535015 this, and make sure X and Y asymmetry is close to 0 (less than +/-6% with 2 nA beam, and less than 3% when you go to production current). | ** Look into FT Calo scaler screen, which is the main measure how the beam is centered, for reference look https://logbooks.jlab.org/entry/3535015 this, and make sure X and Y asymmetry is close to 0 (less than +/-6% with 2 nA beam, and less than 3% when you go to production current). | ||
− | ** If the beam is centered enough and halo rates on midstream and upstream halo counters don't exceed few Hz, request for 20 nA beam, and ask out orbit lock to be engaged. | + | ** If the beam is centered enough and halo rates on midstream and upstream halo counters don't exceed few Hz, request for 20 nA beam, and ask out orbit lock to be engaged. Check again beam is centered, and halo counters still coun order of few Hz. |
− | |||
** Check also beam position on 2H01, should be around '''2H01 (X=1.0 mm, Y=-1.5 mm)''' | ** Check also beam position on 2H01, should be around '''2H01 (X=1.0 mm, Y=-1.5 mm)''' | ||
<!-- | <!-- | ||
Line 143: | Line 142: | ||
** As soon you are done with 2c21 and tagger harp scans, put back FSD hresholds for upstream and midstream counters to 1000, and integration time to 5 ms. | ** As soon you are done with 2c21 and tagger harp scans, put back FSD hresholds for upstream and midstream counters to 1000, and integration time to 5 ms. | ||
--> | --> | ||
− | ** For 2H01 harp scan, ask BOM limit to be | + | ** For 2H01 harp scan, ask BOM limit to be 1000000 and itegration time 50 ms. then do 2H01 harp scan. Compare harp scan result to the most recent one https://logbooks.jlab.org/entry/3534806, make sure beam sigmas are close to the one in the link. |
* Next step is to tur HV on for detectors, for '''SVT''' only call Yuri and ask him to turn SVT HV on. | * Next step is to tur HV on for detectors, for '''SVT''' only call Yuri and ask him to turn SVT HV on. |
Revision as of 14:12, 22 February 2018
[edit]
Shift ScheduleShift ChecklistHot CheckoutBeam Time Accounting
|
Manuals |
Procedures |
JLab Logbooks
|
|
|
- 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: Rafayel Paremuzyan
- (757) 575-7540
- 9 575 7540 from Counting Room
- rafopar@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-21, 23:25The plan until Friday Feb 23 noon: Take data with trigger_v5.trg at 35 nA beam
|
General Instructions:
Every Shift:
Every Run:
|
Webcams |
Manuals |
Epics on the web
|
Hall-BRun lists |
Accelerator |
Bluejean meetings
|