CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
DigiAccumulatorMixMod.h
Go to the documentation of this file.
1 #ifndef SimGeneral_MixingModule_DigiAccumulatorMixMod_h
2 #define SimGeneral_MixingModule_DigiAccumulatorMixMod_h
3 // -*- C++ -*-
4 //
5 // Package: MixingModule
6 // Class : DigiAccumulatorMixMod
7 //
16 //
17 // Original Author: Werner Sun
18 // Created: Tue Sep 20 17:33:33 CEST 2011
19 //
20 
21 // system include files
22 #include <vector>
23 
24 // user include files
25 
26 // forward declarations
27 
28 namespace edm {
29  class Event;
30  class EventPrincipal;
31  class EventSetup;
32  class LuminosityBlock;
33  class Run;
34 }
35 
37 
39 
40  public:
42 
43  virtual ~DigiAccumulatorMixMod();
44 
45  // ---------- const member functions ---------------------
46 
47  // ---------- static member functions --------------------
48 
49  // ---------- member functions ---------------------------
50  // Perform algorithm setup for each event before any signal/pileup events are processed.
51  virtual void initializeEvent(edm::Event const& event, edm::EventSetup const& setup) = 0;
52 
53  // Accumulate digis or other data for each signal event.
54  virtual void accumulate(edm::Event const& event, edm::EventSetup const& setup) = 0;
55 
56  // Accumulate digis or other data for each pileup event, one at a time.
57  virtual void accumulate(PileUpEventPrincipal const& event, edm::EventSetup const& setup) = 0;
58 
59  // 1. Finalize digi collections or other data for each event.
60  // 2. Put products in Event with appropriate instance labels
61  virtual void finalizeEvent(edm::Event& event, edm::EventSetup const& setup) = 0; // event is non-const
62 
63  // Perform any necessary actions before pileup events for a given bunch crossing are processed.
64  virtual void initializeBunchCrossing(edm::Event const& event, edm::EventSetup const& setup, int bunchCrossing) {}
65 
66  // Perform any necessary actions after pileup events for a given bunch crossing are processed.
67  // This may include putting bunch crossing specific products into the event.
68  virtual void finalizeBunchCrossing(edm::Event& event, edm::EventSetup const& setup, int bunchCrossing) {}
69 
70  virtual void beginRun(edm::Run const& run, edm::EventSetup const& setup) {}
71  virtual void endRun(edm::Run const& run, edm::EventSetup const& setup) {}
72  virtual void beginLuminosityBlock(edm::LuminosityBlock const& lumi, edm::EventSetup const& setup) {}
73  virtual void endLuminosityBlock(edm::LuminosityBlock const& lumi, edm::EventSetup const& setup) {}
74 
75  private:
76  DigiAccumulatorMixMod(DigiAccumulatorMixMod const&); // stop default
77 
78  DigiAccumulatorMixMod const& operator=(DigiAccumulatorMixMod const&); // stop default
79 
80  // ---------- member data --------------------------------
81 };
82 
83 #endif
virtual void initializeEvent(edm::Event const &event, edm::EventSetup const &setup)=0
virtual void accumulate(edm::Event const &event, edm::EventSetup const &setup)=0
virtual void endRun(edm::Run const &run, edm::EventSetup const &setup)
virtual void finalizeEvent(edm::Event &event, edm::EventSetup const &setup)=0
tuple lumi
Definition: fjr2json.py:35
virtual void initializeBunchCrossing(edm::Event const &event, edm::EventSetup const &setup, int bunchCrossing)
virtual void beginLuminosityBlock(edm::LuminosityBlock const &lumi, edm::EventSetup const &setup)
virtual void endLuminosityBlock(edm::LuminosityBlock const &lumi, edm::EventSetup const &setup)
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 beginRun(edm::Run const &run, edm::EventSetup const &setup)
virtual void finalizeBunchCrossing(edm::Event &event, edm::EventSetup const &setup, int bunchCrossing)
DigiAccumulatorMixMod const & operator=(DigiAccumulatorMixMod const &)
void setup(std::vector< TH2F > &depth, std::string name, std::string units="")
Definition: Run.h:36