CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
DTnoiseDBValidation.h
Go to the documentation of this file.
1 #ifndef DTnoiseDBValidation_H
2 #define DTnoiseDBValidation_H
3 
21 
22 #include <string>
23 #include <vector>
24 #include <map>
25 
26 class DTGeometry;
27 class DTChamberId;
28 class DTStatusFlag;
29 class TFile;
30 
32 public:
35 
37  virtual ~DTnoiseDBValidation();
38 
40  void beginRun(const edm::Run& run, const edm::EventSetup& setup);
41  void endRun(edm::Run const&, edm::EventSetup const&);
42  void endJob();
43  void analyze(const edm::Event& event, const edm::EventSetup& setup) {}
44 
45 protected:
46 
47 private:
48  void bookHisto(const DTChamberId&);
49 
51  // The DB label
52  std::string labelDBRef_;
53  std::string labelDB_;
56 
58  std::string outputFileName_;
59 
60  // The DTGeometry
62 
63  // The noise map
66 
67  //the total number of noisy cell
70  // the histos
76  std::map<DTChamberId, MonitorElement*> noiseHistoMap_;
77 
78 };
79 #endif
80 
MonitorElement * wheelHisto_
void beginRun(const edm::Run &run, const edm::EventSetup &setup)
Operations.
std::map< DTChamberId, MonitorElement * > noiseHistoMap_
void bookHisto(const DTChamberId &)
const DTStatusFlag * noiseRefMap_
const DTStatusFlag * noiseMap_
DTnoiseDBValidation(const edm::ParameterSet &pset)
Constructor.
MonitorElement * diffHisto_
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::ESHandle< DTGeometry > dtGeom_
void endRun(edm::Run const &, edm::EventSetup const &)
MonitorElement * stationHisto_
virtual ~DTnoiseDBValidation()
Destructor.
void analyze(const edm::Event &event, const edm::EventSetup &setup)
void setup(std::vector< TH2F > &depth, std::string name, std::string units="")
MonitorElement * layerHisto_
Definition: Run.h:33
MonitorElement * sectorHisto_