1 #ifndef RecoMuon_TrackerSeedGenerator_CompositeTSG_H
2 #define RecoMuon_TrackerSeedGenerator_CompositeTSG_H
25 typedef std::pair<const Trajectory*, reco::TrackRef>
TrackCand;
41 std::vector<TrackerSeedGenerator*>
theTSGs;
std::pair< const Trajectory *, reco::TrackRef > TrackCand
CompositeTSG(const edm::ParameterSet &pset, edm::ConsumesCollector &IC)
virtual void trackerSeeds(const TrackCand &, const TrackingRegion &, const TrackerTopology *, BTSeedCollection &)=0
provides the seeds from the TSGs: must be overloaded
std::vector< TrajectorySeed > BTSeedCollection
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
void init(const MuonServiceProxy *service)
initialized the TSGs
std::vector< TrajectorySeed > BTSeedCollection
const MuonServiceProxy * theProxyService
std::vector< std::string > theNames
std::pair< const Trajectory *, reco::TrackRef > TrackCand
void setEvent(const edm::Event &event)
set the event to the TSGs