Difference between revisions of "Run Group A"
Line 250: | Line 250: | ||
* main scaler GUI display | * main scaler GUI display | ||
* Detector occupancy plots | * Detector occupancy plots | ||
− | * Trigger rate | + | * Trigger rate GUI |
* Beam strip charts | * Beam strip charts | ||
− | * | + | * FT-Cal FADC scalers |
|} | |} | ||
+ | |||
+ | | valign=top | | ||
+ | |||
+ | ==<font color=blue>''' General Instructions''':</font>== | ||
+ | |||
+ | * For a given beam current, compute the FSD thresholds according to the [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf Establish Physics Quality Beam] document. Call MCC to update the values. Contact the beamline expert if there are questions about setting the FSD thresholds. | ||
+ | * The main lights in the Hall (dome lights) and the Forward Carriage lights are being kept off because of light leaks affecting some of the detectors. If these lights are switched on during an access, they should be switched off when leaving the Hall. Note that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cooldown. | ||
+ | * Do not run more than 60 minutes above 30 nA with 5-pass beam without the beam blocker in front of Faraday cup. Put beam blocker in for long running at high currents for 5 pass operations. | ||
+ | * Turn DC HV off only for beam tuning; if no beam is available or when beam is stable, keep them on even if you are not taking data. | ||
+ | * In case of loss of communication with IOCBTARG, follow instructions at https://logbooks.jlab.org/entry/3502218 | ||
+ | * With any issue contact On-Call Experts or RC - do not spend more than 15-20 min trying to fix the problem. | ||
+ | * All jscaler iocs (iocjscalerX) on the health screen (under DAQ tab) must be restarted after every DAQ prestart is completed. Follow this link for detailed instructions https://userweb.jlab.org/~baltzell/CLAS12/SC/jlabScalersOps.txt | ||
+ | * Check that no unecessary beamline-related screens are open. This includes particularly the big beamline overview screen, but also and any motor/harp/collimator screens, and ioc health screens. | ||
+ | |||
+ | '''Every Shift:''' | ||
+ | *Follow run plan as outlined by RC | ||
+ | * If any concern about beam stability, ask MCC if orbit locks are on (they should be). | ||
+ | * Keep shift summary up to date in HBLOG. Record all that happens. | ||
+ | * Check on white board all scalers, strip charts and monitoring plots that need to be logged regularly | ||
+ | * Document any beam condition change and send scaler GUIs to HBLOG | ||
+ | * [https://bta.acc.jlab.org Fill out BTA] hourly. Click "Load from EPICS" to automatically fill the left side. | ||
+ | * Fill and submit the [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook] | ||
+ | <!-- * Once a shift between the runs Restart FTT gas flow. Follow these steps: | ||
+ | ** From main clascss open '''FTT Gas''' | ||
+ | ** Click '''STOP''' and then '''START'''. If you do it quickly interlock will not trip. If interlock trips it will turn OFF FTT HV and you will get an alarm. If this happens do the following: | ||
+ | *** On '''FTT Gas''' make sure the gas is flowing | ||
+ | *** Open '''FTT Soft Interlocks'''. At the bottom of the screen in the 'FTT gas' section click '''Reset''' for those in red. | ||
+ | *** Turn FTT HV back ON. | ||
+ | ** If not sure or have problems call FT on-call. --> | ||
+ | |||
+ | '''Every Run:''' | ||
+ | |||
+ | '' Log screenshots of:'' | ||
+ | * main scaler GUI display | ||
+ | * Detector occupancy plots | ||
+ | * Trigger rate GUI | ||
+ | * Beam strip charts | ||
+ | * FT-Cal FADC scalers | ||
= Monitoring = | = Monitoring = |
Revision as of 09:29, 22 August 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, 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 rates on the midstream counters have to be in the range 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 standard DAQ 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 mm, Y=0.5 mm) , 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 a 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:(Updated: Aug. 22, 2018 at 10:08 a.m.) 1) Before the start of beam delivery: Ramp torus field to -100% (negatives inbending) and ramp solenoid field to -100%. (Call PDL for this step) 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 rates and performance (including initial studies of FADC bit packing) 7a). Complete MM setting optimization. This work will be completed under the direction of the MM experts. 8a) Perform trigger test plans (trigger checks and optimization, study of DC tracking trigger, FTOF/PCAL matching). This work will be completed under the direction of the trigger experts 9a) Optimize the FT settings (FT group will take over DAQ control remotely and complete task). This should be done (preferably) during the owl shift. 10a) Complete a luminosity scan and record data in the following sequence with the standard RG-A trigger:
11a) Take data with the standard RG-A trigger at 20 nA for 4 hrs to collect data for baseline subsystem calibrations 12a) 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 Shift Worker Notes:
In case of other questions or uncertainties of what to do, call the RC |
General Instructions:
Every Shift:
Every Run: Log screenshots of:
|
| valign=top |
General Instructions:
- For a given beam current, compute the FSD thresholds according to the Establish Physics Quality Beam document. Call MCC to update the values. Contact the beamline expert if there are questions about setting the FSD thresholds.
- The main lights in the Hall (dome lights) and the Forward Carriage lights are being kept off because of light leaks affecting some of the detectors. If these lights are switched on during an access, they should be switched off when leaving the Hall. Note that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cooldown.
- Do not run more than 60 minutes above 30 nA with 5-pass beam without the beam blocker in front of Faraday cup. Put beam blocker in for long running at high currents for 5 pass operations.
- Turn DC HV off only for beam tuning; if no beam is available or when beam is stable, keep them on even if you are not taking data.
- In case of loss of communication with IOCBTARG, follow instructions at https://logbooks.jlab.org/entry/3502218
- With any issue contact On-Call Experts or RC - do not spend more than 15-20 min trying to fix the problem.
- All jscaler iocs (iocjscalerX) on the health screen (under DAQ tab) must be restarted after every DAQ prestart is completed. Follow this link for detailed instructions https://userweb.jlab.org/~baltzell/CLAS12/SC/jlabScalersOps.txt
- Check that no unecessary beamline-related screens are open. This includes particularly the big beamline overview screen, but also and any motor/harp/collimator screens, and ioc health screens.
Every Shift:
- Follow run plan as outlined by RC
- If any concern about beam stability, ask MCC if orbit locks are on (they should be).
- Keep shift summary up to date in HBLOG. Record all that happens.
- Check on white board all scalers, strip charts and monitoring plots that need to be logged regularly
- Document any beam condition change and send scaler GUIs to HBLOG
- Fill out BTA hourly. Click "Load from EPICS" to automatically fill the left side.
- Fill and submit the shift checklist in the logbook
Every Run:
Log screenshots of:
- main scaler GUI display
- Detector occupancy plots
- Trigger rate GUI
- Beam strip charts
- FT-Cal FADC scalers
Webcams |
Manuals |
Epics on the web
|
Hall-B
Run lists |
Accelerator |
Bluejean meetings
|