Run Group K

From clas12-run
Revision as of 07:34, 25 July 2018 by Pasyuk (Talk | contribs) (Created page with "= Shift Documentation = <!--####################################### SHIFT DOCUMENTATION ########################################--> {| {{TableStyle1}} | valign=top | <!--==...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
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)
Engineering on-call 757 748-5048 (cell)
Engineering on-call secondary 757 897-9060 (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
SVT + MM (757) 541-7539 (cell) Yori Gotra Primary
SVT + MM (757) 753-7769 (cell) Rafo Paremuzyan Secondary
ECAL (757) 810-1489 (cell) Cole Smith
FTOF/CTOF (757) 344-7204 (cell) Jose Carvajal
CND (757) 344-7204 (cell) Silvia Niccolai
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) Valery Kubarovsky
DAQ (757) 232-6221 (cell) Sergey Boiarinov
Slow Controls (757) 748-6922 (cell) Nathan Baltzell
Beamline (757) 303-3996 (cell) Eugene Pasyuk
Target (757) 822-9586 (cell) Bob Miller Primary
Target secondary (757) 897-9060 (cell) Denny Insley

| valign=top |

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
Run is Over!
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 ( can fill the run list)

RC: Somebody

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", "", "go".

if run did not ended correctly, or ROCs had to be rebooted "Configure", "download", "prestart", "", "go".

After DAQ prestart is complete reboot the scaler IOCs with the command:

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
    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 . 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: May3-May 6

May 4 (Day/Swing) There are a series of special runs planned.

1. FT-only trigger runs: Genova group (Raffaella/Andrea) just finished this run

2. Random-trigger with existing PCAL/FTOF map: Started around 9am and should conclude around 2pm. If there is any issue, contact Andrea via

For 3--5, Sergey will take control of DAQ

3. DAQ studies(Sergey): Starting from 2:00pm. Sergey must be notified around 1:30pm if he is not already in the counting house. This is a series of short runs

4. DC/Varying readout window size/current scans: This will be a series of short runs (~30min each). For exact setting, please contact Volker (phone # on white board); Sergey will implement the changes.

5. Mode 7: Sergey will perform this run (~2 hrs). Dan should be contacted if needed via FTOF expert phone.

May 4(Swing) --- May 6th (Owl)

When the above special runs are finished. Resume production runs at 50nA with trigger_v12_3.cnf

May 6 at 5 am MCC will terminate beam delivery.

Start preparation for summer shutdown after that

  • Turn HV OFF for:
    • DC
    • FTOF
    • LTCC
    • HTCC
    • FTT
    • BMT/FMT
    • CTOF
    • CND
  • Detectors remain ON for post calibrations:
    • RICH
    • SVT
    • FTC/FTH
    • Cryotarget stays FULL
  • Turn OFF Solenoid and Torus (call PDL)

May 6 7am.

A small reception full of fancy food will be held in the counting house at 7am for the early birds. No reservation needed. Dress code: photo-friendly.

  • 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, roc_reboot adcft1 (and adcft2, adcft3), make sure the roc are connected, 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.
  • 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

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 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

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
  • 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
  • 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