...
With these settings the trigger primitives within the trigger window look like this:
How the trigger delay should be set?
The proposed trigger delay settings are fine in case all the trigger primitives are enabled (allowed to open the trigger window), but in the BeamTest only external trigger can open the window so in roughtly half of the event that have an internal trigger we will not see this trigger primitive in the summary word. This can be a problem if people want to study trigger efficiency.
So a second option for trigger settings (to be used in case of ext trigger only) is to delay the internal treq by 6 ticks to make the peak in the center of trigger window, and reduce the tack in a consstent way:
- CAL treq_delay = 0x6
- TKR treq_delay = 0x8
- CAL tack_delay ~ 0x27-0x28 (nominal reduced by 6 tiks)
- TKR tack_delay = 0x0 (nominal - no way to reduce it)
- delay_ext_trig = 0x8