Difference between revisions of "Run Group A"

From clas12-run
Jump to navigation Jump to search
Line 97: Line 97:
 
*<font color=red> '''Always monitor the rates on the Halo counters when they are tuning beam to the other halls'''
 
*<font color=red> '''Always monitor the rates on the Halo counters when they are tuning beam to the other halls'''
 
* '''Do Not turn on or off SVT only SVT expert can do that'''
 
* '''Do Not turn on or off SVT only SVT expert can do that'''
−
* Any request for special run change of configuration has to be approved by RC & documented  
+
* '''Any request for special run change of configuration has to be approved by RC & documented'''
 
'''</font>
 
'''</font>
  
Line 123: Line 123:
 
* After that take one run random Trigger for 4 hours  @ 30nA with trigger file: random_v3.trg (Put the comment on the run spreadsheet New PCAL Firmware in the trigger for this run)
 
* After that take one run random Trigger for 4 hours  @ 30nA with trigger file: random_v3.trg (Put the comment on the run spreadsheet New PCAL Firmware in the trigger for this run)
 
* <font color = red>''' STOP before proceeding call Sergey DAQ expert, he will change the PCAL firmware in the trigger''' </font></s>-->
 
* <font color = red>''' STOP before proceeding call Sergey DAQ expert, he will change the PCAL firmware in the trigger''' </font></s>-->
−
* Take Production production run with old trigger @ 30nA 2 hours/run with trigger file (trigger_v3.trg)  
+
<font color=blue>'''  February 17 and February 18 Shifts'''</font>
−
* If the machine is down and it is back start with Low current (2nA and 5 nA)  making sure that the beam is stable in current and position before moving to 30 nA
+
* Continue taking production runs @ 30nA 2 hours/run with trigger file (trigger_v3.trg)  
 +
* If the machine is down and it is back start with low current first  (2nA and 5 nA)  making sure that the beam is stable in current and position before moving to 30 nA
 
* In case of questions or uncertainties of what to do, please call the RC
 
* In case of questions or uncertainties of what to do, please call the RC
  

Revision as of 17:40, 17 February 2018

[edit]
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, Winter 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: Latifa Elouadrhiri

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.
  • Note 2: At the end of each run, follow the DAQ restart sequence "end run", "abort", "reset", "download", "prestart", "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 3: Nominal beam positions: 2H01 (X=1.0 mm, Y=-1.5 mm) and 2H00 (X=2.2 mm, Y=1.5 mm)
  • Note 4: With beam to the Faraday Cup, typical rates on all halo counters upstream from the target should be either 0 or of the order of few counts. Count rates in the range of tens or more may indicate bad beam tune or bleed-through from other Halls.

Run Plan:

(last update 2/17 - 17:30)

  • Always monitor the rates on the Halo counters when they are tuning beam to the other halls
  • Do Not turn on or off SVT only SVT expert can do that
  • Any request for special run change of configuration has to be approved by RC & documented

February 17 and February 18 Shifts

  • Continue taking production runs @ 30nA 2 hours/run with trigger file (trigger_v3.trg)
  • If the machine is down and it is back start with low current first (2nA and 5 nA) making sure that the beam is stable in current and position before moving to 30 nA
  • In case of 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.
  • 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.
  1. Fill and submit the shift checklist in the logbook
  2. Perform 2H01A harp scan once per shift or when beam conditions have changed, based on beam monitors (BPMs, halo rates, beam-viewer). During harp scans the HV for DC and HTCC should be OFF.

Every Run:

  • Log screenshots of:
  • main scaler GUI display
  • Detector occupancy plots
  • Trigger rate gui
  • Beam strip charts


Clas12design.png

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