5 #ifndef NTUPLEROOTFILE_
6 #define NTUPLEROOTFILE_
26 virtual int getJmohep(
int j,
int idx)
const;
27 virtual int getJdahep(
int j,
int idx)
const;
28 virtual double getPhep(
int j,
int idx)
const;
29 virtual double getVhep(
int j,
int idx)
const;
virtual int getNevhep() const
virtual int getJsdhep(int j) const
virtual int getJsmhep(int j) const
virtual ~NtupleROOTFile()
virtual int getJdahep(int j, int idx) const
virtual double getVhep(int j, int idx) const
virtual int getIsthep(int j) const
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 int getId() const
virtual int getEntries() const
virtual void setEvent(int event) const
virtual int getNhep() const
virtual int getIdhep(int j) const
virtual double getPhep(int j, int idx) const
virtual int getJmohep(int j, int idx) const