Difference between revisions of "Run Group A"
Jump to navigation
Jump to search
| Line 126: | Line 126: | ||
1) Before the start of beam delivery: Ramp torus field to -100% (negatives inbending) and ramp solenoid field to -100% | 1) Before the start of beam delivery: Ramp torus field to -100% (negatives inbending) and ramp solenoid field to -100% | ||
| + | |||
2) Complete beam tuning studies - <font color="red">This effort will be carried out under the direction of the beamline expert</font> | 2) Complete beam tuning studies - <font color="red">This effort will be carried out under the direction of the beamline expert</font> | ||
* Complete beam tuning to the tagger yoke beam dump following the procedures in the beam tuning document | * Complete beam tuning to the tagger yoke beam dump following the procedures in the beam tuning document | ||
| Line 133: | Line 134: | ||
* Make sure harp scans results for 2C21, 2C24, and 2H01 are posted in the logbook (these will represent our baseline results for the fall 2018 run) | * Make sure harp scans results for 2C21, 2C24, and 2H01 are posted in the logbook (these will represent our baseline results for the fall 2018 run) | ||
* Record nominal beam positions at BPMs in the logbook (these will represent out nominal values for the fall 2018 run) | * Record nominal beam positions at BPMs in the logbook (these will represent out nominal values for the fall 2018 run) | ||
| + | |||
3) With empty target: | 3) With empty target: | ||
* Turn on CLAS12 detectors from least sensitive to most sensitive (call SVT, MM, and DC experts to turn their systems on) | * Turn on CLAS12 detectors from least sensitive to most sensitive (call SVT, MM, and DC experts to turn their systems on) | ||
| Line 139: | Line 141: | ||
* Take empty target run (2 hrs at 100 nA) | * Take empty target run (2 hrs at 100 nA) | ||
* At end of run, have MCC turn the beam off | * At end of run, have MCC turn the beam off | ||
| + | |||
<font color="red">If target is functional</font> | <font color="red">If target is functional</font> | ||
4a) Fill the target (call Engineering for this step) | 4a) Fill the target (call Engineering for this step) | ||
| + | |||
5a) Perform current scan - - check rates vs. beam current to 75 nA (use 2 nA, 10 nA, 30 nA, 50 nA, 75 nA) - record scalers in logbook and record currents on CTOF, FTOF, and PCAL ammeters (see links on monitoring tab to access cameras) | 5a) Perform current scan - - check rates vs. beam current to 75 nA (use 2 nA, 10 nA, 30 nA, 50 nA, 75 nA) - record scalers in logbook and record currents on CTOF, FTOF, and PCAL ammeters (see links on monitoring tab to access cameras) | ||
* DC experts should use this period to finalize the HV and discriminator thresholds | * DC experts should use this period to finalize the HV and discriminator thresholds | ||
* CVT experts should use this period to study currents and stability | * CVT experts should use this period to study currents and stability | ||
| + | |||
6a) Check DAQ and trigger functionality | 6a) Check DAQ and trigger functionality | ||
| + | |||
7a) Optimize the FT settings (FT group will take over DAQ control remotely and complete task). This should be done (preferably) during the owl shift. | 7a) Optimize the FT settings (FT group will take over DAQ control remotely and complete task). This should be done (preferably) during the owl shift. | ||
| + | |||
8a) Complete a luminosity scan and record data in the following sequence with the standard RG-A trigger: | 8a) Complete a luminosity scan and record data in the following sequence with the standard RG-A trigger: | ||
* 2 nA - 2 hrs | * 2 nA - 2 hrs | ||
| Line 152: | Line 159: | ||
* 50 nA - 30 min | * 50 nA - 30 min | ||
* 75 nA - 30 min | * 75 nA - 30 min | ||
| + | |||
9a) Take data with the standard RG-A trigger at 20 nA for 4 hrs to collect data for baseline subsystem calibrations | 9a) Take data with the standard RG-A trigger at 20 nA for 4 hrs to collect data for baseline subsystem calibrations | ||
| + | |||
10a) Take production data with the standard RG-A trigger at 40 nA (3 hr runs) | 10a) Take production data with the standard RG-A trigger at 40 nA (3 hr runs) | ||
| + | |||
<font color="red">If target is not functional</font> | <font color="red">If target is not functional</font> | ||
4b) Ramp torus to 0% field (call Engineering for this step) | 4b) Ramp torus to 0% field (call Engineering for this step) | ||
| + | |||
5b) Take data at 2 nA for DC alignment studies for 1 hr | 5b) Take data at 2 nA for DC alignment studies for 1 hr | ||
| + | |||
6b) Have MCC turn the beam off | 6b) Have MCC turn the beam off | ||
| + | |||
7b) Ramp solenoid to 0% field (call Engineering for this step) | 7b) Ramp solenoid to 0% field (call Engineering for this step) | ||
| + | |||
8b) Take data at 2 nA with both magnets for DC and CVT alignment studies off for 8 hrs | 8b) Take data at 2 nA with both magnets for DC and CVT alignment studies off for 8 hrs | ||
Revision as of 09:50, 18 August 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, Fall 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
RC: Daniel S. Carman
- (757) 575-7540
- 9 575 7540 from Counting Room
- carman@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 the upstream counters have to be in the range 0-15 Hz (rates up 100 Hz are acceptable) and the midstream have to be in the rage 10-20 Hz (acceptable up to 50 Hz) @50 nA. Counting rates in the range of hundreds of Hz may indicate bad beam tune or bleed-through from other Halls.
- Note 2: At the end of each run, follow the standardDAQ restart sequence
"end run", "cancel", "reset", then if the run ended correctly "download", "prestart", "iocjscalerRestartAll.sh", "go". If the run did not end correctly or if any 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.
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/3570290.
- 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 to request beam OFF and to drop Hall B status to Power Permit
- Call Engineering on-call
- Make separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" field 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 elements: Upstream, Midstream, Downstream, BOM, and Solenoid should always be in the state UNMASKED,
- No changes to the FSD threshold should be made 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 the RC & documented
- Note 9: Carefully check the BTA every hour and run the script btaGet.py to 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.
Start-up Run Plan:1) Before the start of beam delivery: Ramp torus field to -100% (negatives inbending) and ramp solenoid field to -100% 2) Complete beam tuning studies - This effort will be carried out under the direction of the beamline expert
3) With empty target:
If target is functional 4a) Fill the target (call Engineering for this step) 5a) Perform current scan - - check rates vs. beam current to 75 nA (use 2 nA, 10 nA, 30 nA, 50 nA, 75 nA) - record scalers in logbook and record currents on CTOF, FTOF, and PCAL ammeters (see links on monitoring tab to access cameras)
6a) Check DAQ and trigger functionality 7a) Optimize the FT settings (FT group will take over DAQ control remotely and complete task). This should be done (preferably) during the owl shift. 8a) Complete a luminosity scan and record data in the following sequence with the standard RG-A trigger:
9a) Take data with the standard RG-A trigger at 20 nA for 4 hrs to collect data for baseline subsystem calibrations 10a) Take production data with the standard RG-A trigger at 40 nA (3 hr runs) If target is not functional 4b) Ramp torus to 0% field (call Engineering for this step) 5b) Take data at 2 nA for DC alignment studies for 1 hr 6b) Have MCC turn the beam off 7b) Ramp solenoid to 0% field (call Engineering for this step) 8b) Take data at 2 nA with both magnets for DC and CVT alignment studies off for 8 hrs
Sometimes, a couple of RICH channel scalers would go to 0 and there is no alarm, even though the "# of fibers connected" would be shown to be the correct 138. Shift takers therefore should periodically, especially at the end of run, check the RICH scalers GUI. If there is an issue:
In case of other questions or uncertainties of what to do, 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
|
|
|
