#include <memory>
#include <string>
#include <vector>
#include <sstream>
#include <fstream>
#include <iostream>
#include <TH2F.h>
#include <TROOT.h>
#include <TFile.h>
#include <TSystem.h>
#include "DataFormats/FWLite/interface/Handle.h"
#include "DataFormats/PatCandidates/interface/Muon.h"
#include "DataFormats/PatCandidates/interface/Jet.h"
#include "FWCore/FWLite/interface/FWLiteEnabler.h"
Go to the source code of this file.
|
int | main (int argc, char *argv[]) |
|
int main |
( |
int |
argc, |
|
|
char * |
argv[] |
|
) |
| |
CALO JETS
PF JETS
Definition at line 19 of file PatMcMatchFWLiteAnalyzer.cc.
References fwlite::Event::atEnd(), gather_cfg::cout, FWLiteEnabler::enable(), event(), fwlite::Handle< T >::getByLabel(), i, iEvent, fwrapper::jets, patZpeak::muons, GetRecoTauVFromDQM_MC_cff::outFile, reco::LeafCandidate::pt(), and fwlite::Event::toBegin().
30 gSystem->Load(
"libFWCoreFWLite" );
34 TH2F* muonPt_ =
new TH2F(
"muonPt",
"Muon Pt", 60, 0., 300., 60, 0., 300. );
35 muonPt_->SetXTitle(
"gen." );
36 muonPt_->SetYTitle(
"reco." );
37 TH2F* jetPt_ =
new TH2F(
"jetPt",
"Jet Pt", 100, 0., 500., 100, 0., 500. );
38 jetPt_->SetXTitle(
"gen." );
39 jetPt_->SetYTitle(
"reco." );
42 TFile* inFile = TFile::Open(
"file:edmPatMcMatch.root" );
59 if( iEvent==1000 )
break;
62 if(iEvent>0 && iEvent%25==0){
63 std::cout <<
" processing event: " << iEvent << std::endl;
74 for(
unsigned i=0;
i<muons->size(); ++
i){
77 muonPt_->Fill( genMuon->
pt(), (*muons)[
i].pt() );
81 for(
unsigned i=0;
i<jets->size(); ++
i){
84 jetPt_->Fill( genJet->
pt(), (*jets)[
i].pt() );
100 TFile
outFile(
"rootPatMcMatch.root",
"recreate" );
101 outFile.mkdir(
"analyzeMcMatchPat");
102 outFile.cd(
"analyzeMcMatchPat");
virtual double pt() const
transverse momentum
void getByLabel(const P &iP, const char *iModuleLabel, const char *iProductInstanceLabel=0, const char *iProcessLabel=0)
static void enable()
enable automatic library loading
Jets made from MC generator particles.
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