CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
DTResolutionAnalysisTask.h
Go to the documentation of this file.
1 #ifndef DTResolutionAnalysisTask_H
2 #define DTResolutionAnalysisTask_H
3 
22 
23 
24 #include <string>
25 #include <map>
26 #include <vector>
27 
28 class DQMStore;
29 class MonitorElement;
30 class DTGeometry;
31 
33 public:
36 
38  virtual ~DTResolutionAnalysisTask();
39 
41  void beginRun(const edm::Run&, const edm::EventSetup&);
42 
44  void beginLuminosityBlock(edm::LuminosityBlock const& lumiSeg, edm::EventSetup const& context) ;
45 
47  void endJob();
48 
49  // Operations
50  void analyze(const edm::Event& event, const edm::EventSetup& setup);
51 
52 
53 protected:
54 
55 private:
57 
59 
62 
63  u_int32_t thePhiHitsCut;
64  u_int32_t theZHitsCut;
65 
66  // Lable of 4D segments in the event
67  std::string theRecHits4DLabel;
68 
69  // Book a set of histograms for a give chamber
70  void bookHistos(DTSuperLayerId slId);
71  // Fill a set of histograms for a give chamber
72  void fillHistos(DTSuperLayerId slId,
73  float distExtr,
74  float residual);
75 
76  std::map<DTSuperLayerId, std::vector<MonitorElement*> > histosPerSL;
77 
78  // top folder for the histograms in DQMStore
79  std::string topHistoFolder;
80 
81 };
82 #endif
83 
void analyze(const edm::Event &event, const edm::EventSetup &setup)
void beginRun(const edm::Run &, const edm::EventSetup &)
BeginRun.
void beginLuminosityBlock(edm::LuminosityBlock const &lumiSeg, edm::EventSetup const &context)
To reset the MEs.
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
std::map< DTSuperLayerId, std::vector< MonitorElement * > > histosPerSL
void fillHistos(DTSuperLayerId slId, float distExtr, float residual)
DTResolutionAnalysisTask(const edm::ParameterSet &pset)
Constructor.
void bookHistos(DTSuperLayerId slId)
void setup(std::vector< TH2F > &depth, std::string name, std::string units="")
virtual ~DTResolutionAnalysisTask()
Destructor.
edm::ESHandle< DTGeometry > dtGeom
Definition: Run.h:33