1 #ifndef DPGanalysis_SiStripTools_TinyEvent_H
2 #define DPGanalysis_SiStripTools_TinyEvent_H
20 explicit TinyEvent(
const unsigned int event,
const unsigned int orbit,
const int bx):
75 return (dorb*3564 + (
int)
_bx - (int)se.
_bx) * sign;
95 #endif // DPGanalysis_SiStripTools_TinyEvent_H
long long absoluteBXinCycle(const int bx0) const
int operator<(const TinyEvent &other) const
std::vector< TinyEvent > TinyEventCollection
TinyEvent(const TinyEvent &se)
TinyEvent(const unsigned int event, const unsigned int orbit, const int bx)
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
TinyEvent & operator=(const TinyEvent &se)
long long absoluteBX() const
long long deltaBX(const TinyEvent &se) const
int isNextOf(const TinyEvent &se) const
int operator==(const TinyEvent &other) const
long long deltaBXinCycle(const TinyEvent &se, const int bx0) const
TinyEvent(const unsigned int event, const int orbit, const int bx)