CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
PhysicsObjectsMonitor.h
Go to the documentation of this file.
1 #ifndef DQM_PhysicsObjectMonitoring_PhysicsObjectsMonitor_H
2 #define DQM_PhysicsObjectMonitoring_PhysicsObjectsMonitor_H
3 
14 // Base Class Headers
16 
20 
21 
22 namespace edm {
23  class ParameterSet;
24  class Event;
25  class EventSetup;
26 }
27 
28 class TFile;
29 class TH1F;
30 class TH2F;
31 
33 public:
36 
38  virtual ~PhysicsObjectsMonitor();
39 
40  // Operations
41 
42  void analyze(const edm::Event & event, const edm::EventSetup& eventSetup);
43 
44  virtual void beginJob() ;
45  virtual void endJob() ;
46 protected:
47 
48 private:
49  std::string theRootFileName;
52 
53 
54  std::string theSTAMuonLabel;
56 
57  // Histograms Simulation
60 
61  // Histograms MTCC data
76 
77 
78  // Counters
81 
82  std::string theDataType;
83 
84 };
85 #endif
86 
PhysicsObjectsMonitor(const edm::ParameterSet &pset)
Constructor.
void analyze(const edm::Event &event, const edm::EventSetup &eventSetup)
virtual ~PhysicsObjectsMonitor()
Destructor.
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