Difference between revisions of "HPS 2016 Trigger Commissioning"

From hps run
Jump to navigation Jump to search
Line 21: Line 21:
 
#** 25 nA (or lower)
 
#** 25 nA (or lower)
 
#** 100 nA
 
#** 100 nA
#** 200 nA
+
#** 200 nA (If dead time is greater than 25%, lower the beam current)
 
# Three 20 kHz Pulser Runs
 
# Three 20 kHz Pulser Runs
 
#* trigger file:  '''<tt>HPS/Run2016/pulser20kHz.trg</tt>'''
 
#* trigger file:  '''<tt>HPS/Run2016/pulser20kHz.trg</tt>'''

Revision as of 15:24, 12 February 2016

Phase 0: Diagnostics

  1. One Run with Singles & Pairs Triggers
    • trigger file: HPS/Run2016/v0.trg
    • 30 minutes at any fixed current of 25 nA or greater
    • This trigger configuration should give non-zero rates for all triggers:
      • singles-0, singles-1, pairs-0, pairs-1

Phase 1: Preliminary Tuning

  1. ECal Pedestal Runs
    • About 10 minutes at each beam current:
      • 25 nA (or lower)
      • 100 nA
      • 200 nA
  2. Three Singles+Pairs Trigger Runs
    • trigger file: HPS/Run2016/v0.trg
    • This trigger configuration should give non-zero rates for all triggers:
      • singles-0, singles-1, pairs-0, pairs-1
    • 10 minutes at each beam current:
      • 25 nA (or lower)
      • 100 nA
      • 200 nA (If dead time is greater than 25%, lower the beam current)
  3. Three 20 kHz Pulser Runs
    • trigger file: HPS/Run2016/pulser20kHz.trg
    • At least 100 Million events (~1 hour) at each beam current:
      • 25 nA (or lower)
      • 100 nA
      • 200 nA

Ideally the pedestal runs should be done first so that they can be used
to update the pedestals used for the 20 kHz Pulser runs. This requires
an ECal expert available, and to then update the trigger files for the
subsequent Pulser runs. If this is not the case, the Pulser runs can
be done first with the preconfigured pedestals.

Phase 2: Final Tuning

coming soon