CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
TrajectoryBuilder.h
Go to the documentation of this file.
1 #ifndef TrackingTools_PatternTools_TrajectoryBuilder_h
2 #define TrackingTools_PatternTools_TrajectoryBuilder_h
3 
8 
9 class TrajectorySeed;
10 
19 public:
20 
21  typedef std::vector<Trajectory> TrajectoryContainer;
22  typedef TrajectoryContainer::iterator TrajectoryIterator;
23 
24  virtual ~TrajectoryBuilder() {};
25 
26  virtual TrajectoryContainer trajectories(const TrajectorySeed&) const = 0;
27 
28  virtual void trajectories(const TrajectorySeed& seed, TrajectoryContainer &out) const {
30  out = std::move(ret);
31  }
32 
36  virtual void rebuildSeedingRegion(const TrajectorySeed&,
37  TrajectoryContainer& result) const {
38  LogDebug("TrajectoryBuilding")
39  << "WARNING: you are using a trajectory builder which is not overloading the rebuildSeedingRegion method because there is not an implementation yet: output TrajectoryContainer is equal to inputTrajectoryContainer";
40  }
41 
42  virtual void setEvent(const edm::Event& event) const = 0;
43  virtual void unset() const {};
44 };
45 
46 
47 #endif
#define LogDebug(id)
virtual void rebuildSeedingRegion(const TrajectorySeed &, TrajectoryContainer &result) const
std::vector< Trajectory > TrajectoryContainer
tuple result
Definition: query.py:137
virtual void trajectories(const TrajectorySeed &seed, TrajectoryContainer &out) const
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
virtual void unset() const
virtual TrajectoryContainer trajectories(const TrajectorySeed &) const =0
virtual ~TrajectoryBuilder()
tuple out
Definition: dbtoconf.py:99
virtual void setEvent(const edm::Event &event) const =0
TrajectoryContainer::iterator TrajectoryIterator