CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
CompositeTSG.h
Go to the documentation of this file.
1 #ifndef RecoMuon_TrackerSeedGenerator_CompositeTSG_H
2 #define RecoMuon_TrackerSeedGenerator_CompositeTSG_H
3 
15 
16 class TrackingRegion;
17 class MuonServiceProxy;
18 class TrackerTopology;
19 
21 
22 public:
23  typedef std::vector<TrajectorySeed> BTSeedCollection;
24  typedef std::pair<const Trajectory*, reco::TrackRef> TrackCand;
25 
26  CompositeTSG(const edm::ParameterSet &pset);
27  virtual ~CompositeTSG();
28 
30  void init(const MuonServiceProxy *service);
32  void setEvent(const edm::Event &event);
33 
35  virtual void trackerSeeds(const TrackCand&, const TrackingRegion&, const TrackerTopology *, BTSeedCollection &) =0;
36 
37  protected:
38 
39  unsigned int nTSGs() { return theTSGs.size();}
40  std::vector<TrackerSeedGenerator*> theTSGs;
41  std::vector<std::string> theNames;
43 
45 };
46 
47 
48 #endif
CompositeTSG(const edm::ParameterSet &pset)
Definition: CompositeTSG.cc:7
std::pair< const Trajectory *, reco::TrackRef > TrackCand
virtual void trackerSeeds(const TrackCand &, const TrackingRegion &, const TrackerTopology *, BTSeedCollection &)=0
provides the seeds from the TSGs: must be overloaded
virtual ~CompositeTSG()
Definition: CompositeTSG.cc:27
std::vector< TrajectorySeed > BTSeedCollection
Definition: CompositeTSG.h:23
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
std::vector< TrackerSeedGenerator * > theTSGs
Definition: CompositeTSG.h:40
void init(const MuonServiceProxy *service)
initialized the TSGs
Definition: CompositeTSG.cc:32
std::string theCategory
Definition: CompositeTSG.h:42
std::vector< TrajectorySeed > BTSeedCollection
const MuonServiceProxy * theProxyService
Definition: CompositeTSG.h:44
unsigned int nTSGs()
Definition: CompositeTSG.h:39
std::vector< std::string > theNames
Definition: CompositeTSG.h:41
std::pair< const Trajectory *, reco::TrackRef > TrackCand
Definition: CompositeTSG.h:24
void setEvent(const edm::Event &event)
set the event to the TSGs
Definition: CompositeTSG.cc:39