CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
DQMEventMsgBuilder.h
Go to the documentation of this file.
1 #ifndef IOPool_Streamer_DQMEventMsgBuilder_h
2 #define IOPool_Streamer_DQMEventMsgBuilder_h
3 
42 
44 
45 
46 // ------------------ dqm event message builder ----------------
47 
49 {
50  public:
52  edm::Timestamp timeStamp,
53  uint32 lumiSection, uint32 updateNumber,
54  uint32 adler32_chksum,
55  const char* host_name,
56  std::string const& releaseTag,
57  std::string const& topFolderName,
58  const DQMEvent::TObjectTable& monitorElementsBySubFolder);
59 
60  uint32 bufferSize() const { return bufSize_; }
61  uint8* startAddress() const { return buf_; }
62  uint32 headerSize() const { return eventAddr_-buf_; }
64  void setFUProcessId(uint32);
65  void setFUGuid(uint32);
66  void setMergeCount(uint32);
67  uint8* eventAddress() const { return eventAddr_; }
68  void setEventLength(uint32 len);
69  uint32 size() const;
70 
71  private:
75 };
76 
77 #endif
uint32 bufferSize() const
static int const bufSize
Definition: Guid.cc:24
uint8 * eventAddress() const
DQMEventMsgBuilder(void *buf, uint32 bufSize, uint32 run, uint32 event, edm::Timestamp timeStamp, uint32 lumiSection, uint32 updateNumber, uint32 adler32_chksum, const char *host_name, std::string const &releaseTag, std::string const &topFolderName, const DQMEvent::TObjectTable &monitorElementsBySubFolder)
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
unsigned int uint32
Definition: MsgTools.h:13
void setCompressionFlag(uint32)
void setEventLength(uint32 len)
unsigned char uint8
Definition: MsgTools.h:11
uint8 * startAddress() const
std::map< std::string, std::vector< TObject * > > TObjectTable
uint32 headerSize() const