Detailed L3 Beam Test Plan Spring 2017

From GlueXWiki
Jump to: navigation, search


Goals

- Find event rate/data rate limits of current system is capable of maintaining - Test L3 infrastructure under beam conditions for extended period


Conditions

 - 100nA-1000nA , 5mm collimator, JD70-100 58 um
 - Standard L1 trigger: FCAL_BCAL_PS_m9.cnf
 - L3 CODA config.: hd_all.L3.tsg
 - Detector settings for high intensity running
  + CDC HV?
  + TOF HV?
  + …

Step by step instructions

1. Take short run (5 min.) using non-L3 config to establish baseline. This will be hd_all.tsg
 1a. Record event rate, data rate, and lifetime.
2. Test non-rejection rate maximum
 2a. Start at low current mode (50nA) and verify system works with high livetime 
 2b. Gradually increase beam current until livetime drops to 50% or less
 2c. Identify bottleneck (farm, disk, …)
3. Test 75% rejection rate limits
 3a. Edit $DAQ_HOME/config/farm/run_hdl3.py to set L3:FRACTION_TO_KEEP=0.25
 3b. Raise and lower beam current to find where livetime is at 90% and 50% points.
       - record beam current, data rate, event rate, and livetime for each. 
       - Identify bottleneck (farm, disk, …)
4. Test 75% rejection rate limits with wire-based tracking and BCAL cluster finding turned on.
   This will mimic an algorithm with CPU usage.
 4a. Edit $DAQ_HOME/config/farm/run_hdl3.py and uncomment appropriate lines
 4b. Repeat 3b.
5. Test using trivial rejection algorithm
 5a. Edit $DAQ_HOME/config/farm/run_hdl3.py, restoring to state prior to item 3 above
 5b. Edit $DAQ_HOME/config/farm/run_hdl3.py to turn on trivial rejection algorithm
 5c. Repeat 3b.
6. Do long term test by restoring to the state of “2” and running for at least 1 hour.