Data formats in HLTrigger
Complete:
Event content definition
Filters are available to select/skim events based on L1 trigger bits (class
HLTLevel1Seed
) or on HLT trigger bits (class
HLTHighLevel
) - the user just has to configure the module instance by supplying the list of L1 trigger names or HLT trigger names s/he is interested in.
A single filter (see
TriggerResultsFilter) also exists, able to skim on both L1 and HLT results.
HLT trigger collections (in RECO and AOD) |
TriggerResults |
edm::TriggerResults |
One EDproduct per HLT table: the HLT decision - global, and for each HLT trigger path: Ready (ie, Not Run), Pass (Accept), Fail (Reject), Error (Exception) |
hltTriggerSummaryAOD |
trigger::TriggerEvent |
One EDproduct per HLT table - contains L3 collections and L3 filter decisions |
hltTriggerSummaryRAW |
trigger::TriggerEventWithRefs |
One EDproduct for each HLT path in the HLT table - contains Ref links pointing to the original HLT collections and records filter decisions |
HLT filter module label |
trigger::TriggerFilterObjectWithRefs |
one of these by every HLT filter module - transient - used to provide information put into persistent TriggerEvent or TriggerEventWithRefs |
hltTimer |
edm::EventTime containing a vector of edm::ModuleTime |
Simple class for Rate/CPU/Wall time benchmarking of algorithms - generic, not HLT specific |
hltPathTimer |
HLTPerformanceInfo |
Advanced class for Rate/CPU/Wall time benchmarking of the HLT table |
Review status
Responsible: Christos Leonidopoulos, Martin Gruenewald
Last reviewed by: