1 #ifndef EFFICIENCYANALYZER_H
2 #define EFFICIENCYANALYZER_H
MuonServiceProxy * theService
MonitorElement * h_failProbes_TightMu_pt
MonitorElement * h_allProbes_eta
edm::ParameterSet parameters
MonitorElement * h_allProbes_pt
MonitorElement * h_passProbes_TightMu_hp_eta
MonitorElement * h_passProbes_TightMu_eta
MonitorElement * h_passProbes_TightMu_phi
MonitorElement * h_failProbes_TightMu_phi
MonitorElement * h_passProbes_TightMu_pt
MonitorElement * h_passProbes_TightMu_barrel_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
edm::InputTag theMuonCollectionLabel
void analyze(const edm::Event &event, const edm::EventSetup &eventSetup)
MonitorElement * h_passProbes_TightMu_endcap_pt
void beginJob(DQMStore *dbe)
Inizialize parameters for histo binning.
MonitorElement * test_TightMu_Minv
edm::InputTag theTrackCollectionLabel
MonitorElement * h_failProbes_TightMu_eta
MonitorElement * h_allProbes_hp_eta
virtual ~EfficiencyAnalyzer()
MonitorElement * h_allProbes_phi
MonitorElement * h_allProbes_endcap_pt
EfficiencyAnalyzer(const edm::ParameterSet &pset, MuonServiceProxy *theService)
edm::InputTag theSTACollectionLabel
MonitorElement * h_allProbes_barrel_pt