Run Group K

From clas12-run
Jump to: navigation, search

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]

Person Phone Number
Run Coordinator (757) 575-7540 (cell)
Physics Division Liaison (757) 876-1789 (cell)
Shift Expert (757) 329-4846 (cell)
Remote Shifter (day/swing) (757) 310-7198 (cell)
MCC-OPS 7048
Crew Chief 7045
Crew Chief 9-876-3367 (cell)
Program Deputy 9-876-7997 (cell)
Gate House Guard 5822
Location Phone Number
Hall-B Floor 5165
Hall-B Space Frame 5170, 5171
Hall-B Forward Carriage 5371
Hall-B Counting Room 5245 (Shift1), 5126 (Shift2)
Hall-B Counting Room 5244 (Expert)
Hall-B Gas Shed 7115
System Phone Number On-Call Person
DC (757) 748-5048 (cell) Engineering On-Call
FMT (757) 541-7539 (cell) Yuri Gotra -presently on a mountain. Call RC or RTPC expert instead
BONuS (RTPC) (757) 329-4844 (cell) Mohammad Hattawy
ECAL (757) 810-1489 (cell) Cole Smith
FTOF/CTOF (757) 344-7204 (cell) Jose Carvajal
CND (757) 218-2266 (cell) Katheryne Price
HTCC-LTCC (757) 344-7174 (cell) Youri Sharabian
FT (757) 344-1848 (cell) Raffaella De Vita
BAND (757) 310-7198 (cell) Florian Hauenstein
RICH (757) 344-3235 (cell) Andrey Kim
DAQ (757) 869-2188 (cell) Sergey Boiarinov
Slow Controls (757) 748-6922 (cell) Nathan Baltzell
Beamline (757) 303-3996 (cell) Eugene Pasyuk
Engineering (757) 748-5048 (cell) Denny Insley, Bob Miller

Backup system to the On Call:
Use this ONLY if the On Call
phone is not answered
CLASCSS->Page Expert button


Click Here to edit Phone Numbers. Note, you then also have to edit this page to force a refresh.

CLAS12 Run Group K, Fall 2018
Beam energy 7.5/6.5 GeV (4 pass)
Important: Document all your work in the logbook!
Remember to fill in the run list at the beginning and end of each run ( can fill the run list)

RC: Volker Burkert

PDL: Daniel S. Carman

  • 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", "go". If the run did not end correctly or if any ROCs had to be rebooted, "configure", "download", "prestart", "go".
    • 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: 2C21A (X= - 0.37 mm, Y=0.33 mm) , 2C24A (X=0.2 mm, Y=0.3 mm) , 2H01 (X=1.1 mm, Y=-2.0 mm)
  • Note 4: Do not turn OFF FTOF HVs, even during the beam tune with CW beam (turn off when doing a Moller run or if there is tuned/pulsed beam in the upstream beamline)
  • Note 5: In case of a Torus and/or Solenoid Fast Dump do the following:
    1. Notify MCC to request beam OFF and to drop Hall B status to Power Permit
    2. Call Engineering on-call
    3. Make separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" field add Ruben Fair, Probir Goshal, Dave Kashy and
    4. Notify Run Coordinator
    5. Turn off all detectors
  • Note 6: When beam is being delivered to the Faraday Cup:
    1. the Fast Shut Down elements: Upstream, Midstream, Downstream, BOM, and Solenoid should always be in the state UNMASKED
    2. No changes to the FSD threshold should be made without RC or beamline expert approval
  • Note 7: Any request for a special run or change of configuration has to be approved by the RC & documented
  • Note 8: Carefully check the BTA every hour and run the script to print for you what HAS TO BE in BTA for this hour. Edit BTA if it is incorrect.
  • Note 9: Reset CLAS12MON frequently to avoid histogram saturation.
  • Note 11: Do not Turn OFF MVT HV: Instead go to 'Restore settings' from the MVT overview screen:
    1. SafeMode.snp for beam tuning and Moeller runs
    2. MV_HV_FullField.snp for full solenoid field
    3. MV_HV_MidField.snp wgeb solenoid < 4T

  • NOTE 12: Check the vacuum periodically, make sure vacuum is not higher than 5e-5
  • NOTE 13: Always reset the CFD threshold after all power off/on on the CND CAMAC crate
    • If the CND CAMAC CFD crate (camac1) is switched off for any reason, it is mandatory to reset the thresholds via the command: $CODA/src/rol/Linux_x86_64/bin/cnd_cfd_thresh -w 0
    • If this command fails and the crate is not responding, reboot it as follows: roc_reboot camac1
  • NOTE 17: CLAS12 is configured with FT-Off - Do not turn on LV or HV for any of the FT components (Cal, Hodo, Trk)

Run Plan:

(Updated: Dec. 16, 2018 at 14:50hrs)

  • Update the reference harp scan links on the run wikipage (the RC should do this)

Turn on all CLAS12 detectors (note that FT components should be left off as they are not used in this part of the run)

  • In the following use the BPM positions: 2C21A: x=-0.14, y=0.460; 2C24A: x = 0.290, y=0.290 ; 2H00: x=1.3, y=1.0; 2H01: x=1.13, y=-1.91

Plan until Thursday morning 6:00:

  • Trigger file: rgk_v6_200MeV.trg, HWP IN. Beam current at 35nA. Run until 1,000M events are collected.
  • Trigger file: rgk_v6_150MeV.trg, HWP IN. Beam current at 5nA. Take data until Wednesday 8:00am.
  • Trigger file: rgk_v6_300MeV_random_30KHz.trg, HWP IN. Beam currents at 10nA, 35nA, 60nA, 75nA. Collect 200M events at each current (~2hrs per current).
  • Empty target. rgk_v6_150MeV.trg, Beam current: ~150nA. Take data for 4 hours.
  • Ramp Torus current down to 1885A (ask Daniel Carman, PDL). At the same time fill target with lH2. Trigger file: rgk_v6_150MeV.trg, Beam current at 35nA. Take data until Thursday 6am.

End of RGK run!


  • Once per day shift apply the RICH recovery procedure described in
  • If beam is expected to be off for more than 1 hr turn DC HV off, wait 5 minutes, turn DC HV on again.
  • Any questions or uncertainty about what to do please call RC
  • Make sure to save ROC Rates (MB/s) GUI to logbook for each run together with beam screens and trigger GUI
  • Make sure that the FSD thresholds are set correctly and they are unmask when ready to receive beam to the FC @40-50 nA
    • Upstream 2000
    • Midstream 1000
    • Downstream 1000000
    • BOM 30000
    • Dwell time 5 ms

Shift Worker Notes:

  • If the machine is down for more than 30 min 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 the nominal production beam current and continue data taking for production. If there are issues with the beam call RC. Sometimes MCC operator may ask to deliver tuned mode beam --- do not accept it. We need CW beam sent to the Faraday cup. If there is indeed a need for tuned beam, it should be sent to the tagger dump with the tagger magnet on. If you are uncertain, please call RC/PDL.

In case of other questions or uncertainties of what to do, call the RC

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
  • With any issue contact On-Call Experts or RC - do not spend more than 15-20 min trying to fix the problem.
  • Check that no unnecessary 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.
  • Reference harp scans: 2C21, 2C24, 2H01

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.
  • When you do BTA keep track of of BANU. Include at the end of shift summary log details of BANU: the reason and duration.
  • Fill and submit the shift checklist in the logbook

Every Run:

Log screenshots of the following screens, and make sure at the moment you capture the screen the beam is ON

  • main scaler GUI display
  • Detector occupancy plots
  • Trigger rate GUI
  • Roc Rates (MB/s) GUI
  • Statistics DAQ rates GUI
  • Beam strip charts