1 #ifndef Validation_RecoMuon_RecoMuonValidator_H
2 #define Validation_RecoMuon_RecoMuonValidator_H
edm::InputTag glbMuAssocLabel_
edm::InputTag staMuLabel_
virtual int countTrackerHits(const reco::Track &track) const
TrackAssociatorBase * staMuAssociator_
TrackingParticleSelector tpSelector_
virtual void analyze(const edm::Event &event, const edm::EventSetup &eventSetup)
edm::InputTag trkMuAssocLabel_
MuonServiceProxy * theMuonService
virtual int countMuonHits(const reco::Track &track) const
std::string outputFileName_
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 void beginRun(const edm::Run &, const edm::EventSetup &eventSetup)
TrackAssociatorBase * trkMuAssociator_
edm::InputTag glbMuLabel_
TrackAssociatorBase * glbMuAssociator_
edm::InputTag staMuAssocLabel_
edm::InputTag trkMuLabel_
RecoMuonValidator(const edm::ParameterSet &pset)