PatMuonAnalyzer(const edm::ParameterSet &cfg, TFileDirectory &fs)
default constructor
void analyze(const edm::EventBase &event)
everything that needs to be done during the event loop
void endJob()
everything that needs to be done after the event loop
edm::InputTag muons_
input tag for mouns
edm::EDGetTokenT< std::vector< pat::Muon > > muonsToken_
How EventSelector::AcceptEvent() decides whether to accept an event for output otherwise it is excluding the probing of A single or multiple positive and the trigger will pass if any such matching triggers are PASS or EXCEPTION[A criterion thatmatches no triggers at all is detected and causes a throw.] A single negative with an expectation of appropriate bit checking in the decision and the trigger will pass if any such matching triggers are FAIL or EXCEPTION A wildcarded negative criterion that matches more than one trigger in the trigger but the state exists so we define the behavior If all triggers are the negative crieriion will lead to accepting the event(this again matches the behavior of"!*"before the partial wildcard feature was incorporated).The per-event"cost"of each negative criterion with multiple relevant triggers is about the same as!*was in the past
std::map< std::string, TH1 * > hists_
histograms
virtual ~PatMuonAnalyzer()
default destructor
void beginJob()
everything that needs to be done before the event loop
Example class that can be used to analyze pat::Muons both within FWLite and within the full framework...
edm::Service< TFileService > fs
1.8.5
