CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
PatMuonAnalyzer.cc
Go to the documentation of this file.
4 
5 
8  edm::BasicAnalyzer::BasicAnalyzer(cfg, fs),
9  muons_(cfg.getParameter<edm::InputTag>("muons"))
10 {
11  hists_["muonPt" ] = fs.make<TH1F>("muonPt" , "pt" , 100, 0., 300.);
12  hists_["muonEta" ] = fs.make<TH1F>("muonEta" , "eta" , 100, -3., 3.);
13  hists_["muonPhi" ] = fs.make<TH1F>("muonPhi" , "phi" , 100, -5., 5.);
14 }
16  edm::BasicAnalyzer::BasicAnalyzer(cfg, fs),
17  muons_(cfg.getParameter<edm::InputTag>("muons")) ,
18  muonsToken_(iC.consumes<std::vector<pat::Muon> >(muons_))
19 {
20  hists_["muonPt" ] = fs.make<TH1F>("muonPt" , "pt" , 100, 0., 300.);
21  hists_["muonEta" ] = fs.make<TH1F>("muonEta" , "eta" , 100, -3., 3.);
22  hists_["muonPhi" ] = fs.make<TH1F>("muonPhi" , "phi" , 100, -5., 5.);
23 }
24 
26 void
28 {
29  // define what muon you are using; this is necessary as FWLite is not
30  // capable of reading edm::Views
31  using pat::Muon;
32 
33  // Handle to the muon collection
35  event.getByLabel(muons_, muons);
36 
37  // loop muon collection and fill histograms
38  for(std::vector<Muon>::const_iterator mu1=muons->begin(); mu1!=muons->end(); ++mu1){
39  hists_["muonPt" ]->Fill( mu1->pt () );
40  hists_["muonEta"]->Fill( mu1->eta() );
41  hists_["muonPhi"]->Fill( mu1->phi() );
42  }
43 }
tuple cfg
Definition: looper.py:293
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
edm::InputTag muons_
input tag for mouns
Abstract base class for FWLite and EDM friendly analyzers.
T * make(const Args &...args) const
make new ROOT object
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
tuple muons
Definition: patZpeak.py:38