CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
CastorPedestalsAnalysis.h
Go to the documentation of this file.
1 #ifndef CastorPedestalsAnalysis_H
2 #define CastorPedestalsAnalysis_H
3 
13 
27 
32 
33 // #include "CondTools/Hcal/interface/HcalDbOnline.h"
34 
36 // #include "CalibCalorimetry/CastorCalib/interface/CastorCondXML.h"
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 
60  struct NewPedBunch
61  {
63  bool usedflag;
64  float cap[4];
65  float capfc[4];
66  float sig[4][4];
67  float sigfc[4][4];
68  float prod[4][4];
69  float prodfc[4][4];
70  int num[4][4];
71  };
72 
74 {
75  public:
76  //Constructor
78  //Destructor
79  virtual ~CastorPedestalsAnalysis();
80  //Analysis
81  void analyze(const edm::Event & event, const edm::EventSetup& eventSetup);
82 
83  private:
84  //Container for data, 1 per channel
85  std::vector<NewPedBunch> Bunches;
86  //Flag for saving histos
87  bool hiSaveFlag;
88  bool dumpXML;
90  int runnum;
91  int firstTS;
92  int lastTS;
101 
102  TH1F *CASTORMeans;
104 
105  // TH2F *dephist[4];
106  TH2F *dephist;
107 
108  TFile *theFile;
109  bool firsttime;
110 
112 };
113 #endif
114 
void analyze(const edm::Event &event, const edm::EventSetup &eventSetup)
std::vector< NewPedBunch > Bunches
Definition: Event.h:16
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
HcalCastorDetId detid
CastorPedestalsAnalysis(const edm::ParameterSet &ps)