1 #ifndef EFFICIENCYANALYZER_H
2 #define EFFICIENCYANALYZER_H
MonitorElement * h_passProbes_pfIsoTightMu_nVtx
MonitorElement * h_passProbes_EB_pfIsoTightMu_pt
MonitorElement * h_passProbes_EB_pfIsodBTightMu_nVtx
edm::EDGetTokenT< reco::TrackCollection > theTrackCollectionLabel_
MonitorElement * h_failProbes_TightMu_pt
MonitorElement * h_allProbes_eta
MonitorElement * h_allProbes_EE_TightMu_nVtx
edm::ParameterSet parameters
MonitorElement * h_passProbes_EB_detIsoTightMu_pt
edm::EDGetTokenT< reco::VertexCollection > theVertexLabel_
MonitorElement * h_passProbes_pfIsodBTightMu_nVtx
MonitorElement * h_allProbes_EB_TightMu_pt
edm::EDGetTokenT< reco::BeamSpot > theBeamSpotLabel_
MonitorElement * h_passProbes_EE_pfIsoTightMu_nVtx
MonitorElement * h_passProbes_EE_detIsoTightMu_pt
void bookHistograms(DQMStore::IBooker &, edm::Run const &, edm::EventSetup const &) override
MonitorElement * h_allProbes_pt
MonitorElement * h_allProbes_EB_pt
MonitorElement * h_passProbes_TightMu_EB_pt
MonitorElement * h_passProbes_EE_pfIsoTightMu_pt
MonitorElement * h_passProbes_EB_pfIsoTightMu_nVtx
MonitorElement * h_passProbes_TightMu_hp_eta
MuonServiceProxy * theService
MonitorElement * h_allProbes_EE_pt
MonitorElement * h_passProbes_TightMu_eta
MonitorElement * h_passProbes_EE_detIsoTightMu_nVtx
MonitorElement * h_passProbes_TightMu_phi
MonitorElement * h_failProbes_TightMu_phi
MonitorElement * h_passProbes_TightMu_pt
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
MonitorElement * h_allProbes_EB_TightMu_nVtx
MonitorElement * h_passProbes_TightMu_EE_pt
void analyze(const edm::Event &event, const edm::EventSetup &eventSetup)
MonitorElement * h_passProbes_EB_detIsoTightMu_nVtx
MonitorElement * h_passProbes_EE_pfIsodBTightMu_nVtx
MonitorElement * h_passProbes_EE_pfIsodBTightMu_pt
MonitorElement * h_allProbes_TightMu_pt
MonitorElement * test_TightMu_Minv
MonitorElement * h_passProbes_EB_pfIsodBTightMu_pt
MonitorElement * h_passProbes_detIsoTightMu_nVtx
MonitorElement * h_failProbes_TightMu_eta
MonitorElement * h_allProbes_hp_eta
edm::EDGetTokenT< reco::MuonCollection > theMuonCollectionLabel_
virtual ~EfficiencyAnalyzer()
MonitorElement * h_allProbes_EE_TightMu_pt
MonitorElement * h_allProbes_phi
EfficiencyAnalyzer(const edm::ParameterSet &pset)
MonitorElement * h_allProbes_TightMu_nVtx
MonitorElement * h_passProbes_pfIsodBTightMu_pt
MonitorElement * h_passProbes_detIsoTightMu_pt
MonitorElement * h_passProbes_pfIsoTightMu_pt