You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The text to the section "Changes to data flow in Run2" contains the following sentence:
That is to say, any tracks or detector responses that don't form part of the decay that the trigger lines uses to evaluate its selection is thrown away.
"Trigger lines" is plural, but the following verb "uses" is singular. Unfortunately I cannot correct this because I really don't know what the right answer is.
Are tracks really thrown away until they contribute to trigger any of the L0, Hlt1, oder Hlt2 lines? Doesn't that throw away a lot of good TIS events?
The text was updated successfully, but these errors were encountered:
Addressing the last question: yes, TIS events are thrown away by definition. The Turbo stream is equivalent to the stripping, in this sense: you can't ask for events that are ‘stripping TIS’. You have to compute the trigger efficiencies (assuming that's what you'd like TIS for) using simulation.
Migrated from lhcb/starterkit#26, by @KonstantinSchubert.
The text to the section "Changes to data flow in Run2" contains the following sentence:
That is to say, any tracks or detector responses that don't form part of the decay that the trigger lines uses to evaluate its selection is thrown away.
"Trigger lines" is plural, but the following verb "uses" is singular. Unfortunately I cannot correct this because I really don't know what the right answer is.
Are tracks really thrown away until they contribute to trigger any of the L0, Hlt1, oder Hlt2 lines? Doesn't that throw away a lot of good TIS events?
The text was updated successfully, but these errors were encountered: