1 #ifndef Validation_RecoMuon_RecoMuonValidator_H
2 #define Validation_RecoMuon_RecoMuonValidator_H
edm::EDGetTokenT< edm::View< reco::Muon > > muonToken_
edm::EDGetTokenT< TrackingParticleCollection > simToken_
StringCutObjectSelector< reco::Muon > selector_
edm::EDGetTokenT< reco::VertexCollection > primvertexToken_
virtual int countTrackerHits(const reco::Track &track) const
void bookHistograms(DQMStore::IBooker &, edm::Run const &, edm::EventSetup const &) override
TrackingParticleSelector tpSelector_
virtual void analyze(const edm::Event &event, const edm::EventSetup &eventSetup)
MuonServiceProxy * theMuonService
edm::InputTag muAssocLabel_
virtual int countMuonHits(const reco::Track &track) const
const MuonAssociatorByHits * assoByHits
std::string outputFileName_
edm::EDGetTokenT< reco::BeamSpot > beamspotToken_
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
MuonAssociatorByHits::MuonTrackType trackType_
virtual void dqmBeginRun(const edm::Run &, const edm::EventSetup &eventSetup)
std::string subsystemname_
edm::InputTag beamspotLabel_
edm::InputTag primvertexLabel_
std::string muonSelection_
RecoMuonValidator(const edm::ParameterSet &pset)