Difference between revisions of "HPS 2016 Trigger Commissioning"

From hps run
Jump to: navigation, search
 
(24 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
+
<strike>
 
== Phase 0:  Diagnostics ==
 
== Phase 0:  Diagnostics ==
 
# One Run with Singles & Pairs Triggers
 
# One Run with Singles & Pairs Triggers
#* trigger file:  <tt>HPS/Run2016/v0.trg</tt>
+
#* trigger file:  '''<tt>HPS/Run2016/v0.trg</tt>'''
#* 30 minutes at any current
+
#* 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
 +
</strike>
  
 
== Phase 1:  Preliminary Tuning ==
 
== Phase 1:  Preliminary Tuning ==
 +
<strike>
 +
# Three Singles+Pairs Trigger Runs
 +
#* trigger file:  '''<tt>HPS/Run2016/v0.trg</tt>'''
 +
#** Pair-1 is Kyle's ''tight'' A' trigger
 +
#* '''This trigger configuration should give non-zero rates for all triggers:
 +
#** singles-0, singles-1, pairs-0, pairs-1
 +
#** and 1 kHz pulser
 +
#* 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'')
 +
#* '''Take a snapshot of the trigger scalers at each current'''
 
# ECal Pedestal Runs
 
# ECal Pedestal Runs
 
#* About 10 minutes at each beam current:
 
#* About 10 minutes at each beam current:
Line 11: Line 26:
 
#** 100 nA
 
#** 100 nA
 
#** 200 nA
 
#** 200 nA
# 20 kHz Pulser Runs
+
# Three 20 kHz Pulser Runs
#* trigger file:  '''HPS/Run2016/pulser20kHz.trg'''
+
#* trigger file:  '''<tt>HPS/Run2016/pulser20kHz.trg</tt>'''
 
#* At least 100 Million events (~1 hour) at each beam current:
 
#* At least 100 Million events (~1 hour) at each beam current:
 
#** 25 nA (or lower)
 
#** 25 nA (or lower)
Line 18: Line 33:
 
#** 200 nA
 
#** 200 nA
  
Ideally the pedestal runs should be done first so that they can be used<br>
+
Ideally the pedestal runs above ~50 nA should be done first so that they can be used<br>
to update the pedestals used for the 20 kHz Pulser runs.  This requires<br>
+
to update the pedestals used for the 20 kHz Pulser runs.  For 25 nA, no new pedestals <br>
an ECal expert available, and to then update the trigger files for the<br>
+
are needed for the Pulser runs.  ''Taking pedestal runs requires an ECal expert available,''<br>
subsequent Pulser runs. If this is not the case, the Pulser runs can be<br>
+
''and to then update the trigger files for the subsequent Pulser runs.''  '''If this is not the case,'''<br>
done first with the preconfigured pedestals.
+
'''all the Pulser runs can be done first with the preconfigured pedestals.'''
 
+
</strike>
 
+
== Phase 2:  Final Tuning ==
+
coming soon
+

Latest revision as of 08:26, 9 March 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. Three Singles+Pairs Trigger Runs
    • trigger file: HPS/Run2016/v0.trg
      • Pair-1 is Kyle's tight A' trigger
    • This trigger configuration should give non-zero rates for all triggers:
      • singles-0, singles-1, pairs-0, pairs-1
      • and 1 kHz pulser
    • 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)
    • Take a snapshot of the trigger scalers at each current
  2. ECal Pedestal Runs
    • About 10 minutes at each beam current:
      • 25 nA (or lower)
      • 100 nA
      • 200 nA
  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 above ~50 nA should be done first so that they can be used
to update the pedestals used for the 20 kHz Pulser runs. For 25 nA, no new pedestals
are needed for the Pulser runs. Taking pedestal runs requires an ECal expert available,
and to then update the trigger files for the subsequent Pulser runs. If this is not the case,
all the Pulser runs can be done first with the preconfigured pedestals.