CMS 3D CMS Logo

FWTEventList.h
Go to the documentation of this file.
1 #ifndef Fireworks_Core_FWTEventList_h
2 #define Fireworks_Core_FWTEventList_h
3 
4 // There was a bug in ROOT ... fixed on Dec 9 2009:
5 // http://root.cern.ch/viewcvs/trunk/tree/tree/src/TEventList.cxx?view=log
6 //
7 // We need to keep this intermediate class until we switch to
8 // root-5.26 or later.
9 
10 #include "TEventList.h"
11 
12 class FWTEventList : public TEventList {
13 public:
14  FWTEventList() : TEventList() {}
15  FWTEventList(const char* name, const char* title = "", Int_t initsize = 0, Int_t delta = 0)
16  : TEventList(name, title, initsize, delta) {}
17 
18  ~FWTEventList() override {}
19 
20  void Enter(Long64_t entry) override;
21  void Add(const TEventList* list) override;
22 
23 private:
24  FWTEventList(const FWTEventList&); // stop default
25  const FWTEventList& operator=(const FWTEventList&); // stop default
26 
28 };
29 
30 #endif
FWTEventList::Enter
void Enter(Long64_t entry) override
Definition: FWTEventList.cc:57
FWTEventList::operator=
const FWTEventList & operator=(const FWTEventList &)
mps_splice.entry
entry
Definition: mps_splice.py:68
FWTEventList::~FWTEventList
~FWTEventList() override
Definition: FWTEventList.h:18
FWTEventList::FWTEventList
FWTEventList()
Definition: FWTEventList.h:14
FWTEventList::ClassDefOverride
ClassDefOverride(FWTEventList, 0)
FWTEventList::Add
void Add(const TEventList *list) override
Definition: FWTEventList.cc:7
FWTEventList::FWTEventList
FWTEventList(const char *name, const char *title="", Int_t initsize=0, Int_t delta=0)
Definition: FWTEventList.h:15
dumpMFGeometry_cfg.delta
delta
Definition: dumpMFGeometry_cfg.py:25
FWTEventList
Definition: FWTEventList.h:12
overlapproblemtsosanalyzer_cfi.title
title
Definition: overlapproblemtsosanalyzer_cfi.py:7
Skims_PA_cff.name
name
Definition: Skims_PA_cff.py:17
list
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 list("!*", "!HLTx*" if it matches 2 triggers or more) will accept the event if all the matching triggers are FAIL. It will reject the event if any of the triggers are PASS or EXCEPTION(this matches the behavior of "!*" before the partial wildcard feature was incorporated). Triggers which are in the READY state are completely ignored.(READY should never be returned since the trigger paths have been run