CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
FragKey.h
Go to the documentation of this file.
1 #ifndef EventFilter_StorageManager_FragKey_h
2 #define EventFilter_StorageManager_FragKey_h
3 
4 // -*- C++ -*-
5 
6 /*
7  */
8 
10 
11 namespace stor
12 {
13 
14  struct FragKey
15  {
17  FragKey(uint8 msgcode, uint32 run, uint32 event, uint32 secondaryId):
18  code_(msgcode), run_(run), event_(event), secondaryId_(secondaryId) {}
19  FragKey(uint8 msgcode, uint32 run, uint32 event, uint32 secondaryId,
20  uint32 originatorPid, uint32 originatorGuid):
21  code_(msgcode), run_(run), event_(event), secondaryId_(secondaryId),
22  originatorPid_(originatorPid), originatorGuid_(originatorGuid) {}
23  bool operator<(FragKey const& b) const {
24  if(code_ != b.code_) return code_ < b.code_;
25  if(run_ != b.run_) return run_ < b.run_;
26  if(event_ != b.event_) return event_ < b.event_;
29  return secondaryId_ < b.secondaryId_;
30  }
31  // the data for the key
35  // the secondary ID is populated with different values depending
36  // on the context. For EVENT messages, the output module ID is used.
37  // For DQMEVENT messages, the folder ID is used.
41  };
42 
43 }
44 
45 #endif
uint32 originatorPid_
Definition: FragKey.h:39
FragKey(uint8 msgcode, uint32 run, uint32 event, uint32 secondaryId)
Definition: FragKey.h:17
uint32 event_
Definition: FragKey.h:34
uint32 originatorGuid_
Definition: FragKey.h:40
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
uint8 code_
Definition: FragKey.h:32
uint32 run_
Definition: FragKey.h:33
unsigned int uint32
Definition: MsgTools.h:13
double b
Definition: hdecay.h:120
uint32 secondaryId_
Definition: FragKey.h:38
unsigned char uint8
Definition: MsgTools.h:11
FragKey(uint8 msgcode, uint32 run, uint32 event, uint32 secondaryId, uint32 originatorPid, uint32 originatorGuid)
Definition: FragKey.h:19
bool operator<(FragKey const &b) const
Definition: FragKey.h:23