Resolve Trigger objects issues

NWUHEP / ntupleProducer

Northwestern ntuplizer tools for use with CMSSW.

https://twiki.cern.ch/twiki/bin/view/CMS/UserCodeNWUntupleProducer

4 stars 4 forks source link

Resolve Trigger objects issues #18

Closed andreypz closed 9 years ago

andreypz commented 11 years ago

At some point we need to address trigger objects saved in the ntuples.

Some ideas:

Instead of hlt-trigger name store a ULong64 bit that tells which trigger this object belongs to. (Should correspond to the savedTriggerNames array)
This is assuming that the same object can belong to different triggers (should check)

pollackscience commented 11 years ago

I agree, nate really screwed this whole thing up and inconvenienced everyone

andreypz commented 10 years ago

Problem with adding the trigger object is to match them to the HLT trigger path. There is no such functionality. Instead you need to know the name of the last filter of the HLT path and through that match the trigger object. Not clear how to get those filter names for each HLT path. More info here: https://twiki.cern.ch/twiki/bin/view/CMSPublic/SWGuideHLTAnalysis