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 
12 
26 
31 
32 // #include "CondTools/Hcal/interface/HcalDbOnline.h"
33 
35 // #include "CalibCalorimetry/CastorCalib/interface/CastorCondXML.h"
37 
38 #include "TFile.h"
39 #include "TProfile.h"
40 #include "TH1.h"
41 #include "TH2.h"
42 #include "TCanvas.h"
43 #include "TStyle.h"
44 
45 #include <math.h>
46 #include <iostream>
47 #include <map>
48 #include <iomanip>
49 #include <fstream>
50 #include <vector>
51 #include <string>
52 
53 namespace edm {
54  class ParameterSet;
55  class Event;
56  class EventSetup;
57 }
58 
59  struct NewPedBunch
60  {
62  bool usedflag;
63  float cap[4];
64  float capfc[4];
65  float sig[4][4];
66  float sigfc[4][4];
67  float prod[4][4];
68  float prodfc[4][4];
69  int num[4][4];
70  };
71 
73 {
74  public:
75  //Constructor
77  //Destructor
78  virtual ~CastorPedestalsAnalysis();
79  //Analysis
80  void analyze(const edm::Event & event, const edm::EventSetup& eventSetup);
81 
82  private:
83  //Container for data, 1 per channel
84  std::vector<NewPedBunch> Bunches;
85  //Flag for saving histos
86  bool hiSaveFlag;
87  bool dumpXML;
89  int runnum;
90  int firstTS;
91  int lastTS;
92  std::string ROOTfilename;
93  std::string pedsADCfilename;
94  std::string pedsfCfilename;
95  std::string widthsADCfilename;
96  std::string widthsfCfilename;
97  std::string XMLfilename;
98  std::string XMLtag;
99  std::string ZSfilename;
100 
101  TH1F *CASTORMeans;
103 
104  // TH2F *dephist[4];
105  TH2F *dephist;
106 
107  TFile *theFile;
108  bool firsttime;
109 };
110 #endif
111 
void analyze(const edm::Event &event, const edm::EventSetup &eventSetup)
std::vector< NewPedBunch > Bunches
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)