1 #ifndef RecoMuon_TrackingTools_MuonTrajectoryBuilder_H
2 #define RecoMuon_TrackingTools_MuonTrajectoryBuilder_H
17 namespace edm {
class Event;}
27 typedef std::pair<const Trajectory*, reco::TrackRef>
TrackCand;
MuonCandidate::CandidateContainer CandidateContainer
std::vector< Trajectory * > TrajectoryContainer
std::pair< const Trajectory *, reco::TrackRef > TrackCand
MuonCandidate::TrajectoryContainer TrajectoryContainer
virtual TrajectoryContainer trajectories(const TrajectorySeed &)=0
return a container of the reconstructed trajectories compatible with a given seed ...
virtual void setEvent(const edm::Event &event)=0
pass the Event to the algo at each event
MuonTrajectoryBuilder()
constructor
std::vector< MuonCandidate * > CandidateContainer
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 ~MuonTrajectoryBuilder()
destructor
1.8.5
