CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
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 {
14 public:
15  FWTEventList() : TEventList() {}
16  FWTEventList(const char* name, const char* title = "", Int_t initsize = 0, Int_t delta = 0) :
17  TEventList(name, title, initsize, delta) {}
18 
19  virtual ~FWTEventList() {}
20 
21  virtual void Enter(Long64_t entry);
22  virtual void Add(const TEventList* list);
23 
24 private:
25  FWTEventList(const FWTEventList&); // stop default
26  const FWTEventList& operator=(const FWTEventList&); // stop default
27 
29 };
30 
31 #endif
dbl * delta
Definition: mlp_gen.cc:36
virtual void Enter(Long64_t entry)
Definition: FWTEventList.cc:55
virtual void Add(const TEventList *list)
Definition: FWTEventList.cc:7
ClassDef(FWTEventList, 0)
std::pair< std::string, MonitorElement * > entry
Definition: ME_MAP.h:8
virtual ~FWTEventList()
Definition: FWTEventList.h:19
const FWTEventList & operator=(const FWTEventList &)
FWTEventList(const char *name, const char *title="", Int_t initsize=0, Int_t delta=0)
Definition: FWTEventList.h:16
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