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