Skip to content

Trigger object type - useful for the application of trigger scale factors #12

@rmanzoni

Description

@rmanzoni

Each muon of the tau candidate now carries with it, as an attribute, the trigger object to which it is matched. This is valid for each trigger that is tested.

For example, for the main tau3mu trigger HLT_DoubleMu3_Trk_Tau3mu_v* (notice _v* is dropped)

triplet.mu1().best_trig_match['HLT_DoubleMu3_Trk_Tau3mu']
triplet.mu2().best_trig_match['HLT_DoubleMu3_Trk_Tau3mu']
triplet.mu3().best_trig_match['HLT_DoubleMu3_Trk_Tau3mu']

similarly, if another trigger, such as HLT_IsoMu24_v*, is tested, you'll also find

triplet.mu1().best_trig_match['HLT_IsoMu24']
triplet.mu2().best_trig_match['HLT_IsoMu24']
triplet.mu3().best_trig_match['HLT_IsoMu24']

If a given muon of the tripled did not match to any trigger object, for instance, because you only care about a one- or two- prong trigger, then you'll get None.

The trigger object types are defined here
http://cmslxr.fnal.gov/source/DataFormats/HLTReco/interface/TriggerTypeDefs.h

The most relevant to our case are:

TriggerMuon = +83,
TriggerTrack = +91,

This information can be accessed this way

triplet.mu1().best_trig_match['HLT_DoubleMu3_Trk_Tau3mu'].triggerObjectTypes()[0]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions