16 using namespace muonisolation;
20 theTrackCollectionTag(par.getParameter<edm::
InputTag>(
"inputTrackCollection")),
21 theDepositLabel(par.getUntrackedParameter<string>(
"DepositLabel")),
22 theDiff_r(par.getParameter<double>(
"Diff_r")),
23 theDiff_z(par.getParameter<double>(
"Diff_z")),
24 theDR_Max(par.getParameter<double>(
"DR_Max")),
25 theDR_Veto(par.getParameter<double>(
"DR_Veto")),
26 theBeamlineOption(par.getParameter<string>(
"BeamlineOption")),
27 theBeamSpotLabel(par.getParameter<edm::
InputTag>(
"BeamSpotLabel")),
28 theNHits_Min(par.getParameter<unsigned int>(
"NHits_Min")),
29 theChi2Ndof_Max(par.getParameter<double>(
"Chi2Ndof_Max")),
30 theChi2Prob_Min(par.getParameter<double>(
"Chi2Prob_Min")),
31 thePt_Min(par.getParameter<double>(
"Pt_Min"))
52 static std::string
metname =
"MuonIsolation|TrackExtractor";
56 deposit.setVeto(
veto(muonDir) );
57 deposit.addCandEnergy(muon.
pt());
62 LogTrace(metname)<<
"***** TRACK COLLECTION SIZE: "<<tracksH->size();
64 double vtx_z = muon.
vz();
65 LogTrace(metname)<<
"***** Muon vz: "<<vtx_z;
76 beamPoint = beamSpotH->position();
77 LogTrace(metname)<<
"Extracted beam point at "<<beamPoint<<std::endl;
81 LogTrace(metname)<<
"Using beam point at "<<beamPoint<<std::endl;
93 LogTrace(metname)<<
"all tracks: "<<tracksH->size()<<
" selected: "<<sel_tracks.size();
96 TrackSelector::result_type::const_iterator tkI = sel_tracks.begin();
97 for (; tkI != sel_tracks.end(); ++tkI) {
99 LogTrace(metname) <<
"This track has: pt= " << tk->
pt() <<
", eta= "
100 << tk->
eta() <<
", phi= "<<tk->
phi();
102 deposit.addDeposit(dirTrk, tk->
pt());
const std::string metname
std::list< const reco::Track * > result_type
double phi() const
azimuthal angle of momentum vector
double eta() const
pseudorapidity of momentum vector
vector< ParameterSet > Parameters
double pt() const
track transverse momentum
math::XYZPoint Point
point in the space
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
double vz() const
z coordinate of the reference point on track
std::vector< Veto > Vetos
muonisolation::Range< float > Range