Difference between revisions of "HPS 2016 Trigger Commissioning"
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
Ideally the pedestal runs should be done first so that they can be used<br> | Ideally the pedestal runs 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. ''This requires<br> |
an ECal expert available, and to then update the trigger files for the<br> | an ECal expert available, and to then update the trigger files for the<br> | ||
subsequent Pulser runs. If this is not the case, the Pulser runs can be<br> | subsequent Pulser runs. If this is not the case, the Pulser runs can be<br> | ||
| − | done first with the preconfigured pedestals. | + | done first with the preconfigured pedestals.'' |
== Phase 2: Final Tuning == | == Phase 2: Final Tuning == | ||
coming soon | coming soon | ||
Revision as of 08:37, 7 February 2016
Phase 0: Diagnostics
- 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
- 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/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