35 m_L3CollectionLabel( parameterSet.getParameter<
InputTag>(
"InputObjects") )
39 produces<RecoChargedCandidateCollection>();
62 for (
unsigned int i=0;
i<muons->size();
i++) {
63 TrackRef tkref = (*muons)[
i].innerTrack();
65 Particle::Charge
q = tkref->charge();
71 pid = q < 0 ? 13 : -13;
77 candidates->push_back(cand);
80 event.put(candidates);
edm::EDGetTokenT< reco::MuonCollection > muonToken_
Abs< T >::type abs(const T &t)
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 ~L3MuonCandidateProducerFromMuons()
destructor
L3MuonCandidateProducerFromMuons(const edm::ParameterSet &)
constructor with config
std::vector< RecoChargedCandidate > RecoChargedCandidateCollection
collectin of RecoChargedCandidate objects
static const std::string category("Muon|RecoMuon|L3MuonCandidateProducerFromMuons")
std::shared_ptr< cms::Exception > whyFailed() const
virtual void produce(edm::StreamID, edm::Event &, const edm::EventSetup &) const override
produce candidates
void setTrack(const reco::TrackRef &r)
set reference to track
edm::InputTag m_L3CollectionLabel
ParameterSet const & parameterSet(Provenance const &provenance)
math::PtEtaPhiELorentzVectorF LorentzVector