CMS 3D CMS Logo
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
ExhaustiveMuonTrajectoryBuilder.h
Go to the documentation of this file.
1 #ifndef ExhaustiveMuonTrajectoryBuilder_h
2 #define ExhaustiveMuonTrajectoryBuilder_h
3 
10 #include "FWCore/Framework/interface/ESHandle.h"
11 #include "RecoMuon/TrackingTools/interface/MuonTrajectoryBuilder.h"
12 #include "RecoMuon/StandAloneTrackFinder/interface/StandAloneTrajectoryBuilder.h"
13 #include "RecoMuon/TrackingTools/interface/MuonSeedFromRecHits.h"
14 
15 #include "FWCore/Framework/interface/ConsumesCollector.h"
16 
17 class ExhaustiveMuonTrajectoryBuilder : public MuonTrajectoryBuilder
18 {
19 public:
20  ExhaustiveMuonTrajectoryBuilder(const edm::ParameterSet & pset, const MuonServiceProxy*,edm::ConsumesCollector& );
21  virtual ~ExhaustiveMuonTrajectoryBuilder();
22 
24  virtual TrajectoryContainer trajectories(const TrajectorySeed&);
25 
27  virtual CandidateContainer trajectories(const TrackCand&);
28 
30  virtual void setEvent(const edm::Event& event);
31 
32 
33 private:
34  void clean(TrajectoryContainer & trajectories) const;
35 
36  StandAloneMuonTrajectoryBuilder theTrajBuilder;
37  MuonSeedFromRecHits theSeeder;
38  const MuonServiceProxy *theService;
39 
40 };
41 
42 #endif
43 
MuonTrajectoryBuilder::CandidateContainer
MuonCandidate::CandidateContainer CandidateContainer
Definition: MuonTrajectoryBuilder.h:24
MuonTrajectoryBuilder::TrackCand
std::pair< const Trajectory *, reco::TrackRef > TrackCand
Definition: MuonTrajectoryBuilder.h:25
ExhaustiveMuonTrajectoryBuilder::setEvent
virtual void setEvent(const edm::Event &event)
pass the Event to the algo at each event
Definition: ExhaustiveMuonTrajectoryBuilder.cc:60
ExhaustiveMuonTrajectoryBuilder::theTrajBuilder
StandAloneMuonTrajectoryBuilder theTrajBuilder
Definition: ExhaustiveMuonTrajectoryBuilder.h:36
MuonTrajectoryBuilder::TrajectoryContainer
MuonCandidate::TrajectoryContainer TrajectoryContainer
Definition: MuonTrajectoryBuilder.h:23
event
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
ExhaustiveMuonTrajectoryBuilder::clean
void clean(TrajectoryContainer &trajectories) const
Definition: ExhaustiveMuonTrajectoryBuilder.cc:66
ExhaustiveMuonTrajectoryBuilder::trajectories
virtual TrajectoryContainer trajectories(const TrajectorySeed &)
return a container of the reconstructed trajectories compatible with a given seed ...
Definition: ExhaustiveMuonTrajectoryBuilder.cc:21
ExhaustiveMuonTrajectoryBuilder::ExhaustiveMuonTrajectoryBuilder
ExhaustiveMuonTrajectoryBuilder(const edm::ParameterSet &pset, const MuonServiceProxy *, edm::ConsumesCollector &)
Definition: ExhaustiveMuonTrajectoryBuilder.cc:7
Generated for CMSSW Reference Manual by doxygen 1.8.5