CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
HcalPedestalMCWidths.h
Go to the documentation of this file.
1 #ifndef HcalPedestalMCWidths_H
2 #define HcalPedestalMCWidths_H
3 
13 
27 
32 
34 
38 
39 #include "TFile.h"
40 #include "TProfile.h"
41 #include "TH1.h"
42 #include "TH2.h"
43 #include "TCanvas.h"
44 #include "TStyle.h"
45 
46 #include <math.h>
47 #include <iostream>
48 #include <map>
49 #include <iomanip>
50 #include <fstream>
51 #include <vector>
52 #include <string>
53 
54 namespace edm {
55  class ParameterSet;
56  class Event;
57  class EventSetup;
58 }
59 
61  {
63  bool usedflag;
64  float sig[4][10][10];
65  float prod[4][10][10];
66  int num[4][10][10];
67  };
68 
70 {
71  public:
72  //Constructor
74  //Destructor
75  virtual ~HcalPedestalMCWidths();
76  //Analysis
77  void analyze(const edm::Event & event, const edm::EventSetup& eventSetup);
78 
79  private:
80  //Container for data, 1 per channel
81  std::vector<MCWidthsBunch> Bunches;
82  //Flag for saving histos
85 
86  int runnum;
87 
88  TProfile *HBMeans[10];
89  TProfile *HEMeans[10];
90  TProfile *HFMeans[10];
91  TProfile *HOMeans[10];
92 
94 
95  TFile *theFile;
96  bool firsttime;
97  bool histflag;
98 
102 };
103 #endif
104 
int num[4][10][10]
HcalPedestalMCWidths(const edm::ParameterSet &ps)
edm::InputTag hbheDigiCollectionTag_
edm::InputTag hoDigiCollectionTag_
float sig[4][10][10]
std::vector< MCWidthsBunch > Bunches
const HcalTopology * theTopology
edm::InputTag hfDigiCollectionTag_
void analyze(const edm::Event &event, const edm::EventSetup &eventSetup)
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
float prod[4][10][10]