Difference between revisions of "Run Group A"

From clas12-run
Jump to navigation Jump to search
Line 105: Line 105:
 
''(last update 2/20 - 1:15 AM)''
 
''(last update 2/20 - 1:15 AM)''
  
*<font color=red> '''When beam to Fraday Cup the Fast Shut Dow: Upstream, Midstream, Downstream, BOM and Solenoid shoudl be always Unmasked '''
+
*<font color=red> '''When beam to Faraday Cup the Fast Shut Dow: Upstream, Midstream, Downstream, BOM and Solenoid should be always Unmasked '''
 
*'''Always monitor the rates on the Halo counters when they are tuning beam to the other halls'''
 
*'''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>
 +
 +
*When beam is available, notify beamline expert and run coordinator. Then check beam profile by performing harp scans. Call PDL to ramp up solenoid and torus to 100%, with negative inbending.
 +
*Once the beam profile is satisfying, call beamline expert to perform Moller run.
 +
*After the Moller run, turn off HVs of all detectors. Then send beam to the Faraday Cup with empty target. <font color=red> Make sure Upstream, Midstream, Downstream, BOM and Solenoid FSDs are Unmasked with appropriate thresholds. </font>
 +
*Once the beam is going to the Faraday cup, call MCC to stop the beam and fill the target.
 +
*Set correct FSD thresholds for 50nA and then ask MCC to send 50 nA.
 +
*Except for SVT, turn on HVs for all detectors. Call SVT expert to turn ON SVT.
 +
 +
*If beam does not suffer too many trips (no more than one trip per 5 minutes and no longer than 1 minute), take data with random trigger for 2 hours (trigger file to be specified). Then switch to luminosity scan. Take the following runs:
 +
** 5 nA - 4 hours (3.5 M events)
 +
** 10 nA - 2 hours (3.5 M events)
 +
** 35 nA - 0.5 h  (6 M events)
 +
** 50 nA - 0.5 h  ( 8.5 M events)
 +
** 75 nA - 0.5 h  (12M events).
 +
 +
* If beam is too unstable, take data in PROD configuration with trigger file "trigger_v10" at 50 nA.
  
 
<!-- === Updated March 6, 9:39 ===
 
<!-- === Updated March 6, 9:39 ===

Revision as of 19:19, 22 March 2018

[edit]


Clas12design.png