CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
DTSegment4DQuality.h
Go to the documentation of this file.
1 #ifndef Validation_DTSegment4D_H
2 #define Validation_DTSegment4D_H
3 
14 #include "Histograms.h"
19 
20 #include <vector>
21 #include <map>
22 #include <string>
23 
24 namespace edm {
25  class ParameterSet;
26  class Event;
27  class EventSetup;
28 }
29 
30 class TFile;
31 
33 public:
36 
38  virtual ~DTSegment4DQuality();
39 
40  // Operations
41 
43  void analyze(const edm::Event & event, const edm::EventSetup& eventSetup);
44  // Write the histos to file
45  void endJob();
46  void endLuminosityBlock(edm::LuminosityBlock const& lumiSeg,
47  edm::EventSetup const& c);
48 
49 protected:
50 
51 private:
52 
53  // The file which will store the histos
54  //TFile *theFile;
55  // Switch for debug output
56  bool debug;
57  // Root file name
59  //Labels to read from event
62  //Sigma resolution on position
63  double sigmaResX;
64  double sigmaResY;
65  //Sigma resolution on angle
66  double sigmaResAlpha;
67  double sigmaResBeta;
68 
73 
79  bool doall;
80  bool local;
81 };
82 
83 #endif
void analyze(const edm::Event &event, const edm::EventSetup &eventSetup)
Perform the real analysis.
virtual ~DTSegment4DQuality()
Destructor.
edm::InputTag segment4DLabel
DTSegment4DQuality(const edm::ParameterSet &pset)
Constructor.
A set of histograms for efficiency 4D RecHits.
Definition: Histograms.h:1120
void endLuminosityBlock(edm::LuminosityBlock const &lumiSeg, edm::EventSetup const &c)
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::InputTag simHitLabel