Run Group A

From clas12-run
Revision as of 15:14, 29 April 2018 by Lguo (talk | contribs)
Jump to navigation Jump to search
[edit]

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]

Role Phone Number
Hall B Run Coordinator (757) 575-7540 (cell)
Hall B Physics Division Liaison (757) 876-1789 (cell)
MCC 7048
Crew Chief 7045
Crew Chief (757) 876-3367 (cell)
Program Deputy (757) 876-7997 (cell)
RadCon (757) 876-1743 (cell)
Gate House Guard 5822
Location Phone Number
Hall B Floor 5165
Hall B Space Frame 5170 and 5171
Hall B Forward Carriage 5371
Hall B Gas Shed 7115
Hall B Counting House 5244 (Shift Expert)
Hall B Counting House (757) 329-4846 (Shift Expert cell)
Hall B Counting House 5245 or 5126 (Shift Worker)
Hall A Counting House 5501
Hall C Counting House 6000
Hall D Counting House 5504
Hall B System Phone Number On-Call Person
Engineering (757) 748-5048 (cell)
(757) 897-9060 (cell)		 Engineering On-Call (primary)
Denny Insley (secondary)
Slow Controls (757) 748-6922 (cell) Nathan Baltzell
Beamline (757) 303-3996 (cell) Eugene Pasyuk
DC (757) 218-4372 (cell)
(757) 748-5048 (cell)		 Florian Hauenstein (primary)
Engineering On-Call (secondary)
SVT/MVT/MM (757) 541-7539 (cell)
(757) 753-7769 (cell)		 Yuri Gotra (primary)
Rafo Paremuzyan (secondary)
ECAL (757) 810-1489 (cell) Cole Smith
FTOF/CTOF/CND (757) 344-7204 (cell) Daniel Carman
ALERT (757) 329-4844 (cell) Raphael Dupré
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)
(757) 748-6922 (cell)		 Christopher Dilks (primary)
Nathan Baltzell (secondary)
DAQ (757) 232-6221 (cell) Sergey Boiarinov
HYDRA (317) 550-9226 (cell) Torri Jeske
Authorized Hall B Solenoid/Torus Operators
Hall B Denny Insley, Morgan Cook, Eugene Pasyuk
Magnet Group Probir Ghosha, Renuka Rajput-Ghoshal
Detector Support Group Brian Eng, Pablo Campero, Tyler Lemon
DC Power Onish Kumar, Sarin Philip
  • 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, Spring 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: Lei Guo

PDL: Eugene Pasyuk


  • 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 UPSTREAM counters has to be in the range 0-15 Hz (rates up 100 Hz are acceptable) and MIDSTREAM has to be in the rage 10-20 Hz (acceptable up to 50 Hz) @50 nA. Count rates in the range of hundreds or more may indicate bad beam tune or bleed-through from other Halls.

  • Note 2: At the end of each run, follow the DAQ restart sequence

"end run", "cancel", "reset", then

if run ended correctly "download", "prestart", "iocjscalerRestartAll.sh", "go".

if run did not ended correctly, or 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.

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 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 -
    1. Notify MCC, request beam OFF and drop Hall status to Power Permit
    2. Call Engineering on-call
    3. Make separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" filed add Ruben Fair, Probir Goshal, Dave Kashy and esr-users@jlab.org
    4. Notify Run Coordinator
    5. Call the MM expert to turn the detector off
    6. Call SVT expert to turn SVT off
    7. Turn off all the other detectors
  • Note 6: When beam is being delivered to the Faraday Cup -
    1. the Fast Shut Down: Upstream, Midstream, Downstream, BOM and Solenoid should be always Unmasked,
    2. No changes to the FSD threshold 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 RC & documented.
  • Note 9: Check carefully BTA every hour and run script btaGet.py . It will 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.

Run Plan: April 29-May 2

April 29 (Sunday) Day - Aprl 30 (Monday) Owl

  • Take production data with trigger_v12_3.trg @ 50nA on LH2 target, 100 M per run (no longer than 3 hours) till Monday morning, April 30
  • From time to time, we might experience trigger bit issues (FT bits: 24, 25, and 26 and 27). bit 26 might not trigger the alarm but when this issue happens it will count abnormally high pre-prescale. For the time being, shift leaders cand try to do the sequence of End->Cance->Reset, ro_reboot adcft1 (and adcft2, adcft3), make sure the roc are conencted, then Download->Prestart->Go. If this does not work, repeat the sequence and add "Configure" in front of "Download". If the trig issue persist, please continue take production data without fixing it -- please make sure you log this infor in the RCDB "Comment" field. The underlying issue will be addressed on Monday.
  • If the machine is down for few hours 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 50 nA and continue data for production. If there are issues with the beam call the RC. Sometimes MCC operator might ask to deliver tune beam --- please do not accept it. We need CW beam sent to the Faraday cup. If there is in deed a need for tune beam, it should be sent to the tagger dump with the tagger magent on. If you are uncertain, please call RC/PDL.


  • Please contact the Micromegas (BMT, FMT & FTT) expert if there are trips, or if you notice any issues in the online monitoring. Do not turn OFF or ON the MM only the expert can do that. See Log entry https://logbooks.jlab.org/entry/3556528

Sometimes, a couple of RICH channel scalers would go to 0 and there is no alarm, even though the "# of fjibers 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, please refer to the instruction below.

  • For RICH recovery procedures, please see Log entry https://logbooks.jlab.org/entry/3562273. This would apply in the cases of 1. DAQ crash: rich4 is not responding or 2. RICH alarms (LV,missing tile, temperature etc). If it does not work or you are uncertain about what to do, please contact the RICH expert on call


April 30 (Monday) Day


  • After hall work is done and everybody is out of the hall call for sweep and close the hall for "Beam Permit", this should be done before 3pm, April 23
  • When hall is closed ask MCC to ram up the tagger magnet in preparation for beam delivery, also ask to change helicity reporting scheme to "Delay reporting, 8-windows" for the Moller run
  • Fill the target while beam is down
  • When MCC will be ready to send beam, notify run coordinator.

Follow instructions in the "Establish-physics quality beam" procedure at [1] to get an acceptable beam profile. Call PDL to ramp up solenoid and torus to 100%, with negative inbending.

  • Once the beam profile is satisfying (2C21:[2], 2C24:[3], perform Moller runs (follow Moller procedure).
  • Two Moller measurements must be done, with half wave plate OUT and IN, leave half wave plate in IN position
  • After the Moller runs, take the beam away, turn off Moller setup, degauss tagger magnet and send a 5nA beam to the Faraday Cup with empty target. Make sure Upstream, Midstream, Downstream, BOM and Solenoid FSDs are Unmasked with appropriate thresholds.
  • Once the beam is on the Faraday cup and all halo counter rates are normal, perform 2H01 harp scan (see "Establish-physics quality beam" procedure).
  • After physics quality beam is established to Faraday cup, set correct FSD thresholds for 50nA run on LH2 target (see https://logbooks.jlab.org/entry/3564642) and ask MCC to send 50 nA.
  • Except for SVT, turn on HVs for all detectors. Call SVT expert to turn ON SVT.



  • From around Monday 8am (April 30), beam studies is scheduled for about 8 hours. Once the beam is off, turn off all detector HV's, except SVT and MVT which you should notify the corresponding experts to do so. Please notify Ruben (and enigneering on call), about the scheduled magnet studies. They are schedule to be in the counting house around 8:30. If not, notify them by phone. Youri and Latifa also needs access and please coordinate with them as well. Francesco (MVT expert), Sergey/DAQ/BEN (DAQ) should also be notified for scheduled hall work.
  • Most likely the beam studies will be done around 4pm.
  • After hall work is done and everybody is out of the hall call for sweep and close the hall for "Beam Permit". Magnet group should have already ramped up the magnet by now. If not, ask either engineer on call or PDL to ramp up the magent.
  • When hall is closed ask MCC to ram up the tagger magnet in preparation for beam delivery, also ask to change helicity reporting scheme to "Delay reporting, 8-windows" for the Moller run
  • Fill the target while beam is down (if the target was emptied earlier -- TBA)
  • When MCC will be ready to send beam, notify run coordinator and beamline expert (Stepan).

Follow instructions in the "Establish-physics quality beam" procedure at [4] to get an acceptable beam profile.

  • Once the beam profile is satisfying (2C21:[5], 2C24:[6], perform Moller runs (follow Moller procedure).
  • Three moller measurements will be done: A. Half wave plate in, Wien angle at 50 degrees; B. Half wave plate in, Wien angle at 50+25.8 degrees; C. Half wave plate in, Wien angel at 50-25.8 degrees. Each setting takes ~15minutes to set up, and about an hour for the run. For each setting, please notify/request MCC, and also notify Hall C as well.


  • After the Moller runs, we will end with half wave plate in OUT position. Then take the beam away, turn off Moller setup, degauss tagger magnet and send a 5nA beam to the Faraday Cup with empty target. Make sure Upstream, Midstream, Downstream, BOM and Solenoid FSDs are Unmasked with appropriate thresholds.
  • Once the beam is on the Faraday cup and all halo counter rates are normal, perform 2H01 harp scan (see "Establish-physics quality beam" procedure).
  • Except for SVT/MVT, turn on HVs for all detectors. Call SVT/MVT expert to turn ON SVT/MVT.
  • Then resume production data taking.


May 1st/May 2nd: On May 2nd around noon time, there is a scheduled tour of Hall B. Please notify PDL to ramp down the magnets if he is not in the counting house already. The RF recovery might happen during this tour, hopefully (or it might happen on Tuesday May 1st). Once the tour concludes, PDL will ramp up the magnet again. Once this is done, and all detectors ready, pleasze refer below and resume produciton run. If the beam is not good, then we should reestablish the beam by following the procedures (on the right).


In case of other questions or uncertainties of what to do, please 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 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
  • FTCalo FADC scalers


Clas12design.png

Retrieved from "https://wiki.jlab.org/clas12-run/index.php?title=Run_Group_A&oldid=1433"