Difference between revisions of "HPS 2016 Trigger Commissioning"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | == Phase 0 == | + | == Phase 0: Diagnostics == |
# Aprime Runs for Trigger Diagnostics | # Aprime Runs for Trigger Diagnostics | ||
#* trigger file: HPS/Run2016/v0.trg | #* trigger file: HPS/Run2016/v0.trg | ||
#* 30 minutes at any current | #* 30 minutes at any current | ||
| − | == Phase 1 == | + | == Phase 1: Tuning == |
# ECal Pedestal Runs | # ECal Pedestal Runs | ||
#* About 10 minutes at each beam current: | #* About 10 minutes at each beam current: | ||
| Line 25: | Line 25: | ||
| − | == Phase 2 == | + | == Phase 2: Tuning == |
coming soon | coming soon | ||
Revision as of 17:20, 4 February 2016
Phase 0: Diagnostics
- Aprime Runs for Trigger Diagnostics
- trigger file: HPS/Run2016/v0.trg
- 30 minutes at any current
Phase 1: Tuning
- ECal Pedestal Runs
- About 10 minutes at each beam current:
- 25 nA (or lower)
- 100 nA
- 200 nA
- About 10 minutes at each beam current:
- 20 kHz Pulser Runs
- trigger file: HPS/Run2016/20kHz.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: Tuning
coming soon