CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
MuonSegmentMatcher.h
Go to the documentation of this file.
1 #ifndef RecoMuon_GlobalTrackingTools_GlobalMuonRefitter_H
2 #define RecoMuon_GlobalTrackingTools_GlobalMuonRefitter_H
3 
5 
10 
15 
18 
19 namespace edm {class Event; class EventSetup;}
20 namespace reco {class TransientTrack;}
21 
22 class MuonServiceProxy;
23 
25 
26  public:
27 
30 
32  virtual ~MuonSegmentMatcher();
33 
35  std::vector<const DTRecSegment4D*> matchDT (const reco::Track& muon, const edm::Event& event);
36 
37  std::vector<const CSCSegment*> matchCSC(const reco::Track& muon, const edm::Event& event);
38 
39  std::vector<const RPCRecHit*> matchRPC(const reco::Track& muon, const edm::Event& event);
40 
41  protected:
42 
43  private:
46 
48  edm::InputTag trackTags_; //used to select what tracks to read from configuration file
52 
56 
57  double dtRadius_;
58 
61 
62 };
63 #endif
edm::InputTag trackTags_
const edm::Event * theEvent
edm::EDGetTokenT< RPCRecHitCollection > rpcRecHitsToken
MuonSegmentMatcher(const edm::ParameterSet &, edm::ConsumesCollector &iC)
constructor with Parameter Set and MuonServiceProxy
std::vector< const CSCSegment * > matchCSC(const reco::Track &muon, const edm::Event &event)
const MuonServiceProxy * theService
edm::InputTag RPCHitTags_
edm::EDGetTokenT< CSCSegmentCollection > allSegmentsCSCToken
edm::InputTag DTSegmentTags_
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
edm::InputTag CSCSegmentTags_
std::vector< const RPCRecHit * > matchRPC(const reco::Track &muon, const edm::Event &event)
virtual ~MuonSegmentMatcher()
destructor
edm::EDGetTokenT< DTRecSegment4DCollection > dtRecHitsToken
std::vector< const DTRecSegment4D * > matchDT(const reco::Track &muon, const edm::Event &event)
perform the matching
edm::InputTag TKtrackTags_