Difference between revisions of "Engineering Run"

From clas12-run
Jump to navigation Jump to search
Line 100: Line 100:
 
''(last update 1/31 - 14:30 pm)''
 
''(last update 1/31 - 14:30 pm)''
  
−
<!-- * Prepare for beam tuning to the tagger yoke: SVT (contact expert to do it), MVT, CND, CTOF, FTT, HTCC, DC, FTOF should be off, tagger magnet should be on. Follow the instructions in the "Establish-physics quality beam" procedure at [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]. Compare harp scan to the ones performed on 1/25 swing shift (https://logbooks.jlab.org/entry/3520873 and https://logbooks.jlab.org/entry/3520881). Consult with the beamline expert in case of issues.
+
* All studies will take data at 100% torus field (negatives inbending) and solenoid to 100% field, beam position as indicated above. Make sure FSD thresholds are set correctly for whatever current is selected (refer to instructions in the "Establish-physics quality beam" procedure at [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]), integration time is set to 5 ms, and that the orbit locks are on.
−
* If beam profiles at the tagger are acceptable, move to beam tuning to the Faraday Cup. Again, refer to the instructions in the "Establish-physics quality beam" procedure at [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]. Compare harp scan with the one from 1/25 swing shift (https://logbooks.jlab.org/entry/3520947).  
+
 
−
* Once beam to Faraday Cup is established, prepare to start data taking. Switch on all detectors; contact expert to switch on SVT. Start trigger studies following instructions from the DAQ expert. -->
+
<!-- * Prepare for beam tuning to the tagger yoke: SVT (contact expert to do it), MVT, CND, CTOF, FTT, HTCC, DC, FTOF should be off, tagger magnet should be on. Follow the instructions in the "Establish-physics quality beam" procedure at [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]. Compare harp scan to the ones performed on 1/25 swing shift (https://logbooks.jlab.org/entry/3520873 and https://logbooks.jlab.org/entry/3520881). Consult with the beamline expert in case of issues. -->
−
* Once trigger studies are completed, resume data taking at 100% torus field (negatives inbending) and solenoid to 100% field, beam position as indicated above. Make sure FSD thresholds are set correctly (refer to instructions in the "Establish-physics quality beam" procedure at [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]), integration time is set to 5 ms, and that the orbit locks are on.  
+
<!--* If beam profiles at the tagger are acceptable, move to beam tuning to the Faraday Cup. Again, refer to the instructions in the "Establish-physics quality beam" procedure at [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]. Compare harp scan with the one from 1/25 swing shift (https://logbooks.jlab.org/entry/3520947). -->
−
<!--** DC threshold test: ask the DAQ expert to set the DC Region 2 thresholds to 60 mV and take one run (1 h) at 30 nA with elec_htcc_1phe_pcal_300.cnf trigger. Once completed, reverted to the nominal threshold of 45 mV.-->
+
<!--* Once beam to Faraday Cup is established, prepare to start data taking. Switch on all detectors; contact expert to switch on SVT. Start trigger studies following instructions from the DAQ expert. -->
−
** <s>75 nA. 10M events with DC in the trigger: DAQ configuration PROD_noVTP, trigger file dc_elec_htcc_1phe_pcal_300.trg</s>
+
 
−
** <s>75 nA. 10M events without DC in the trigger: DAQ configuration PROD_noVTP, trigger file dcno_elec_htcc_1phe_pcal_300.trg</s>
+
* Carry out trigger studies for electron trigger and FT+hadron trigger. This work will be led by the trigger and DAQ experts.
−
** <s>30 nA. 10M events with DC in the trigger: DAQ configuration PROD, trigger file dc_elec_htcc_1phe_pcal_300.trg</s>
+
* Take regular data taking with PROD/elec_htcc_1phe_pcal_300.cnf at 5 nA until 3 am; 2 hours long runs (low current runs for subsystem calibrations).
−
** <s>30 nA. 10M events without DC in the trigger: DAQ configuration PROD, trigger file dcno_elec_htcc_1phe_pcal_300.trg</s>
+
* Continue work on trigger studies for electron trigger and FT+hadron trigger. This work will be led by the trigger and DAQ experts.
 +
* Complete test plan for tracking trigger checkout:
 
** 10 nA. 1M events with DC in the trigger: DAQ configuration PROD, trigger file dc_elec_htcc_1phe_pcal_300.trg
 
** 10 nA. 1M events with DC in the trigger: DAQ configuration PROD, trigger file dc_elec_htcc_1phe_pcal_300.trg
 
** 10 nA. 1M events without DC in the trigger: DAQ configuration PROD, trigger file dcno_elec_htcc_1phe_pcal_300.trg
 
** 10 nA. 1M events without DC in the trigger: DAQ configuration PROD, trigger file dcno_elec_htcc_1phe_pcal_300.trg
 
** 5 nA. 1M events with DC in the trigger: DAQ configuration PROD, trigger file dc_elec_htcc_1phe_pcal_300.trg
 
** 5 nA. 1M events with DC in the trigger: DAQ configuration PROD, trigger file dc_elec_htcc_1phe_pcal_300.trg
 
** 5 nA. 1M events without DC in the trigger: DAQ configuration PROD, trigger file dcno_elec_htcc_1phe_pcal_300.trg
 
** 5 nA. 1M events without DC in the trigger: DAQ configuration PROD, trigger file dcno_elec_htcc_1phe_pcal_300.trg
−
** Continue regular data taking with PROD/elec_htcc_1phe_pcal_300.cnf at 5 nA until 3 am; 2 hours long runs.
+
* DC threshold test: ask the DAQ expert to set the DC Region 2 thresholds to 60 mV and take one run (1 h) at 30 nA with elec_htcc_1phe_pcal_300.cnf trigger. Once completed, reverted to the nominal threshold of 45 mV.
−
** At the time, RICH studies will begin under the guidance of the RICH group. Use PROD6/elec_htcc_1phe_pcal_300.cnf at 50 nA. Continue until 5 am.
+
* Carry out FT luminosity response studies with FT-only trigger for 2 hours. This work will be led by FT system experts.
−
** At the time, FT studies will begin under the guidance of the FT group. Ask for 5 nA, daq settings will be established by the FT group. Continue until 9 am.
+
* Take regular data taking with PROD/elec_htcc_1phe_pcal_300.cnf at 5 nA until 3 am; 2 hours long runs (low current runs for subsystem calibrations).
−
* Continue regular data taking with PROD/elec_htcc_1phe_pcal_300.cnf at 5 nA.
 
  
 
<!-- == <font color=blue>''' Beam Tuning:'''</font>==
 
<!-- == <font color=blue>''' Beam Tuning:'''</font>==

Revision as of 14:35, 31 January 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 Engineering Run, 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: 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.
  • 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: 2C21 (X=0.0 mm, Y=0.0 mm), 2C24 (X=0.0 mm, Y=0.7 mm), 2H01 (X=0.3 mm, Y=-0.6 mm)
  • Note 4: With beam to the Faraday Cup, typical rates an 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 1/31 - 14:30 pm)

  • All studies will take data at 100% torus field (negatives inbending) and solenoid to 100% field, beam position as indicated above. Make sure FSD thresholds are set correctly for whatever current is selected (refer to instructions in the "Establish-physics quality beam" procedure at [1]), integration time is set to 5 ms, and that the orbit locks are on.


  • Carry out trigger studies for electron trigger and FT+hadron trigger. This work will be led by the trigger and DAQ experts.
  • Take regular data taking with PROD/elec_htcc_1phe_pcal_300.cnf at 5 nA until 3 am; 2 hours long runs (low current runs for subsystem calibrations).
  • Continue work on trigger studies for electron trigger and FT+hadron trigger. This work will be led by the trigger and DAQ experts.
  • Complete test plan for tracking trigger checkout:
    • 10 nA. 1M events with DC in the trigger: DAQ configuration PROD, trigger file dc_elec_htcc_1phe_pcal_300.trg
    • 10 nA. 1M events without DC in the trigger: DAQ configuration PROD, trigger file dcno_elec_htcc_1phe_pcal_300.trg
    • 5 nA. 1M events with DC in the trigger: DAQ configuration PROD, trigger file dc_elec_htcc_1phe_pcal_300.trg
    • 5 nA. 1M events without DC in the trigger: DAQ configuration PROD, trigger file dcno_elec_htcc_1phe_pcal_300.trg
  • DC threshold test: ask the DAQ expert to set the DC Region 2 thresholds to 60 mV and take one run (1 h) at 30 nA with elec_htcc_1phe_pcal_300.cnf trigger. Once completed, reverted to the nominal threshold of 45 mV.
  • Carry out FT luminosity response studies with FT-only trigger for 2 hours. This work will be led by FT system experts.
  • Take regular data taking with PROD/elec_htcc_1phe_pcal_300.cnf at 5 nA until 3 am; 2 hours long runs (low current runs for subsystem calibrations).

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:

  1. Follow run plan as outlined by RC
  2. If any concern about beam stability, ask MCC if orbit locks are on (they should be).
  3. 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
  4. 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:

  1. 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=Engineering_Run&oldid=881"