CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
MuonAssociatorByHits.h
Go to the documentation of this file.
1 #ifndef MuonAssociatorByHits_h
2 #define MuonAssociatorByHits_h
3 
15 
18 
19 #include <memory>
20 
21 namespace muonAssociatorByHitsDiagnostics {
22  class InputDumper;
23 }
24 
26 
27  public:
28 
31 
32  // Originally from TrackAssociatorBase from where this class used to inherit from
35  const edm::Event * event ,
36  const edm::EventSetup * setup ) const {
38  for (unsigned int j=0; j<tCH->size();j++)
39  tc.push_back(tCH->refAt(j));
40 
42  for (unsigned int j=0; j<tPCH->size();j++)
44 
45  return associateRecoToSim(tc,tpc,event,setup);
46  }
47 
50  const edm::Event * event ,
51  const edm::EventSetup * setup ) const {
53  for (unsigned int j=0; j<tCH->size();j++)
54  tc.push_back(tCH->refAt(j));
55 
57  for (unsigned int j=0; j<tPCH->size();j++)
59 
60  return associateSimToReco(tc,tpc,event,setup);
61  }
62 
63 
64  /* Associate SimTracks to RecoTracks By Hits */
68  const edm::Event * event = 0, const edm::EventSetup * setup = 0) const;
69 
73  const edm::Event * event = 0, const edm::EventSetup * setup = 0) const;
74 
75 
76  private:
80 
81  std::unique_ptr<muonAssociatorByHitsDiagnostics::InputDumper> diagnostics_;
82 };
83 
84 #endif
edm::ParameterSet const conf_
MuonAssociatorByHits(const edm::ParameterSet &conf, edm::ConsumesCollector &&iC)
ProductID id() const
Definition: HandleBase.cc:15
TrackerHitAssociator::Config trackerHitAssociatorConfig_
std::unique_ptr< muonAssociatorByHitsDiagnostics::InputDumper > diagnostics_
int j
Definition: DBlmapReader.cc:9
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
tuple conf
Definition: dbtoconf.py:185
reco::RecoToSimCollection associateRecoToSim(edm::Handle< edm::View< reco::Track > > &tCH, edm::Handle< TrackingParticleCollection > &tPCH, const edm::Event *event, const edm::EventSetup *setup) const
void push_back(const RefToBase< T > &)
void push_back(value_type const &ref)
Add a Ref&lt;C, T&gt; to the RefVector.
Definition: RefVector.h:62
virtual reco::SimToRecoCollection associateSimToReco(edm::Handle< edm::View< reco::Track > > &tCH, edm::Handle< TrackingParticleCollection > &tPCH, const edm::Event *event, const edm::EventSetup *setup) const
MuonAssociatorByHitsHelper helper_
void setup(std::vector< TH2F > &depth, std::string name, std::string units="")