CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
DTDCSByLumiSummary.h
Go to the documentation of this file.
1 #ifndef DTMonitorClient_DTDCSByLumiSummary_H
2 #define DTMonitorClient_DTDCSByLumiSummary_H
3 
15 
17 
18 #include <map>
19 
20 class DQMStore;
21 class MonitorElement;
23 
25 
26 public:
27 
30 
32  virtual ~DTDCSByLumiSummary();
33 
34 
35 private:
36 
37  // Operations
38  virtual void beginJob();
40  virtual void analyze(const edm::Event& event, const edm::EventSetup& setup);
41  virtual void endLuminosityBlock(const edm::LuminosityBlock& lumi, const edm::EventSetup& setup);
42  virtual void endRun(const edm::Run& run, const edm::EventSetup& setup);
43  virtual void endJob() ;
44 
46 
49 
50  std::vector<DTTimeEvolutionHisto*> hDCSFracTrend;
51  std::vector<MonitorElement*> totalDCSFractionWh;
52 
53  std::map<int, std::vector<float> > dcsFracPerLumi;
54 
55 };
56 
57 
58 #endif
59 
virtual void endRun(const edm::Run &run, const edm::EventSetup &setup)
tuple lumi
Definition: fjr2json.py:35
std::vector< DTTimeEvolutionHisto * > hDCSFracTrend
MonitorElement * globalHVSummary
virtual void beginLuminosityBlock(const edm::LuminosityBlock &lumi, const edm::EventSetup &setup)
virtual void beginJob()
MonitorElement * totalDCSFraction
DTDCSByLumiSummary(const edm::ParameterSet &pset)
Constructor.
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
virtual void endLuminosityBlock(const edm::LuminosityBlock &lumi, const edm::EventSetup &setup)
virtual void analyze(const edm::Event &event, const edm::EventSetup &setup)
virtual ~DTDCSByLumiSummary()
Destructor.
std::map< int, std::vector< float > > dcsFracPerLumi
std::vector< MonitorElement * > totalDCSFractionWh
void setup(std::vector< TH2F > &depth, std::string name, std::string units="")
Definition: Run.h:41