1 #ifndef FWCore_TFWLiteSelector_TFWLiteSelectorBasic_h
2 #define FWCore_TFWLiteSelector_TFWLiteSelectorBasic_h
39 struct TFWLiteSelectorMembers;
60 virtual void begin(TList*&
in) = 0;
90 virtual void Begin(TTree *) ;
92 virtual void Init(TTree*);
94 virtual Bool_t
Process(Long64_t ) ;
97 virtual Int_t
Version()
const {
return 1; }
101 std::shared_ptr<edm::root::TFWLiteSelectorMembers>
m_;
virtual void terminate(TList &out)=0
virtual ~TFWLiteSelectorBasic()
virtual void preProcessing(const TList *in, TList &out)=0
virtual void SlaveTerminate()
virtual Bool_t Process(Long64_t)
virtual Int_t Version() const
virtual void SlaveBegin(TTree *)
virtual void postProcessing(TList &out)=0
virtual void process(const edm::Event &event)=0
const TFWLiteSelectorBasic & operator=(const TFWLiteSelectorBasic &)
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
void setupNewFile(TFile &)
virtual void Init(TTree *)
std::shared_ptr< edm::root::TFWLiteSelectorMembers > m_
virtual void Begin(TTree *)
virtual void begin(TList *&in)=0
string root
initialization