CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
DiMuonHistograms.h
Go to the documentation of this file.
1 #ifndef DIMUONHISTOGRAMS_H
2 #define DIMUONHISTOGRAMS_H
3 
11 /* Base Class Headers */
12 #include <memory>
13 #include <fstream>
25 
26 
28 
29  public:
30  /* Constructor */
32 
33  /* Destructor */
34  virtual ~DiMuonHistograms() ;
35 
36  /* Operations */
37  void beginJob (DQMStore *dbe);
38  void analyze(const edm::Event & event, const edm::EventSetup& eventSetup);
39 
40  protected:
42 
43  // Switch for verbosity
45 
46  // STA Label
51 
52  //histo binning parameters
53  int etaBin;
54  int etaBBin;
55  int etaEBin;
57 
58  //Defining relevant eta regions
60 
61  double EtaCutMin;
62  double EtaCutMax;
63  double etaBMin;
64  double etaBMax;
65  double etaECMin;
66  double etaECMax;
67 
68  //Defining the relevant invariant mass regions
69  double LowMassMin;
70  double LowMassMax;
71  double HighMassMin;
72  double HighMassMax;
73 
74  std::vector<MonitorElement*> GlbGlbMuon_LM;
75  std::vector<MonitorElement*> GlbGlbMuon_HM;
76  std::vector<MonitorElement*> StaTrkMuon_LM;
77  std::vector<MonitorElement*> StaTrkMuon_HM;
78  std::vector<MonitorElement*> TrkTrkMuon_LM;
79  std::vector<MonitorElement*> TrkTrkMuon_HM;
80 
81  std::vector<MonitorElement*> TightTightMuon;
82  std::vector<MonitorElement*> SoftSoftMuon;
83 
84 };
85 #endif
86 
std::string metname
MuonServiceProxy * theService
std::vector< MonitorElement * > GlbGlbMuon_LM
void analyze(const edm::Event &event, const edm::EventSetup &eventSetup)
edm::ParameterSet parameters
std::vector< MonitorElement * > SoftSoftMuon
std::vector< MonitorElement * > TrkTrkMuon_LM
void beginJob(DQMStore *dbe)
Inizialize parameters for histo binning.
std::vector< MonitorElement * > StaTrkMuon_LM
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
edm::InputTag vertexTag
DiMuonHistograms(const edm::ParameterSet &pset, MuonServiceProxy *theService)
std::vector< MonitorElement * > TrkTrkMuon_HM
edm::InputTag theSTACollectionLabel
edm::InputTag bsTag
virtual ~DiMuonHistograms()
std::vector< MonitorElement * > StaTrkMuon_HM
std::vector< MonitorElement * > GlbGlbMuon_HM
std::vector< MonitorElement * > TightTightMuon
std::string EtaName