53 #ifndef IOPool_Streamer_EventMessage_h 54 #define IOPool_Streamer_EventMessage_h 86 uint32 protocolVersion()
const;
90 uint32 origDataSize()
const;
92 uint32 droppedEventsCount()
const;
94 void l1TriggerBits(std::vector<bool>& put_here)
const;
95 void hltTriggerBits(
uint8* put_here)
const;
const uint8 * eventData() const
uint8 * startAddress() const
uint32 adler32_chksum() const
uint32 eventLength() const
uint32 headerSize() 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
uint32 hostName_len() const