49 LogTrace(
"Muon|RecoMuon|StandAloneMuonProducer")<<
"constructor called"<<endl;
69 string typeOfBuilder = parameterSet.
getParameter<
string>(
"MuonTrajectoryBuilder");
70 if(typeOfBuilder ==
"StandAloneMuonTrajectoryBuilder")
72 else if(typeOfBuilder ==
"DirectMuonTrajectoryBuilder")
74 else if(typeOfBuilder ==
"Exhaustive")
77 LogWarning(
"Muon|RecoMuon|StandAloneMuonProducer") <<
"No Trajectory builder associated with "<<typeOfBuilder
78 <<
". Falling down to the default (StandAloneMuonTrajectoryBuilder)";
85 produces<reco::TrackCollection>().setBranchAlias(theAlias +
"Tracks");
86 produces<reco::TrackCollection>(
"UpdatedAtVtx").setBranchAlias(theAlias +
"UpdatedAtVtxTracks");
87 produces<TrackingRecHitCollection>().setBranchAlias(theAlias +
"RecHits");
88 produces<reco::TrackExtraCollection>().setBranchAlias(theAlias +
"TrackExtras");
89 produces<reco::TrackToTrackMap>().setBranchAlias(theAlias +
"TrackToTrackMap");
91 produces<std::vector<Trajectory> >().setBranchAlias(theAlias +
"Trajectories");
92 produces<TrajTrackAssociationCollection>().setBranchAlias(theAlias +
"TrajToTrackMap");
97 LogTrace(
"Muon|RecoMuon|StandAloneMuonProducer")<<
"StandAloneMuonProducer destructor called"<<endl;
98 if (theService)
delete theService;
99 if (theTrackFinder)
delete theTrackFinder;
106 LogTrace(metname)<<endl<<endl<<endl;
107 LogTrace(metname)<<
"Stand Alone Muon Reconstruction Started"<<endl;
110 LogTrace(metname)<<
"Taking the seeds: "<<theSeedCollectionLabel.label()<<endl;
112 event.getByLabel(theSeedCollectionLabel,seeds);
115 theService->update(eventSetup);
119 LogTrace(metname)<<
"Track Reconstruction"<<endl;
120 theTrackFinder->reconstruct(seeds,event);
123 <<
"================================"
T getParameter(std::string const &) const
virtual void produce(edm::Event &, const edm::EventSetup &)
reconstruct muons
const std::string metname
virtual ~StandAloneMuonProducer()
destructor
StandAloneMuonProducer(const edm::ParameterSet &)
constructor with config
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