CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
DTKeyedConfigCache.h
Go to the documentation of this file.
1 #ifndef CondTools_DT_DTKeyedConfigCache_h
2 #define CondTools_DT_DTKeyedConfigCache_h
3 
17 #include <map>
18 #include <string>
19 #include <vector>
20 
21 class DTKeyedConfig;
23 
24 // ---------------------
25 // -- Class Interface --
26 // ---------------------
27 
29 
30 public:
31 
33  virtual ~DTKeyedConfigCache();
34 
35  int get( const DTKeyedConfigListRcd& keyRecord,
36  int cfgId, const DTKeyedConfig*& obj );
37 
38  void getData( const DTKeyedConfigListRcd& keyRecord,
39  int cfgId, std::vector<std::string>& list );
40 
41  void purge();
42 
43  static const int maxBrickNumber;
44  static const int maxStringNumber;
45  static const int maxByteNumber;
46 
47 private:
48 
51 
52  typedef std::pair<int,const DTKeyedConfig*> counted_brick;
53  std::map<int,counted_brick> brickMap;
57 };
58 #endif
std::map< int, counted_brick > brickMap
void getData(const DTKeyedConfigListRcd &keyRecord, int cfgId, std::vector< std::string > &list)
const DTKeyedConfigCache & operator=(const DTKeyedConfigCache &x)
static const int maxByteNumber
static const int maxBrickNumber
Definition: DDAxes.h:10
std::pair< int, const DTKeyedConfig * > counted_brick
static const int maxStringNumber
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 list("!*","!HLTx*"if it matches 2 triggers or more) will accept the event if all the matching triggers are FAIL.It will reject the event if any of the triggers are PASS or EXCEPTION(this matches the behavior of"!*"before the partial wildcard feature was incorporated).Triggers which are in the READY state are completely ignored.(READY should never be returned since the trigger paths have been run