CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
DTSegment4DT0Corrector.h
Go to the documentation of this file.
1 #ifndef DTSegment_DTSegment4DT0Corrector_H
2 #define DTSegment_DTSegment4DT0Corrector_H
3 
13 
14 namespace edm {
15  class ParameterSet;
16  class Event;
17  class EventSetup;
18 }
19 
21 
22  public:
25 
27  virtual ~DTSegment4DT0Corrector();
28 
29  // Operations
30 
32  virtual void produce(edm::Event& event, const edm::EventSetup& setup);
33 
34 
35  protected:
36 
37  private:
38 
39  // Switch on verbosity
40  bool debug;
41 
43 
44  // the updator
46 
47 };
48 #endif
49 
50 
DTSegmentUpdator * theUpdator
DTSegment4DT0Corrector(const edm::ParameterSet &)
Constructor.
virtual void produce(edm::Event &event, const edm::EventSetup &setup)
The method which produces the 4D rec segments corrected for t0 offset.
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 ~DTSegment4DT0Corrector()
Destructor.
edm::EDGetTokenT< DTRecSegment4DCollection > recHits4DToken_
void setup(std::vector< TH2F > &depth, std::string name, std::string units="")