CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
DTConfigPluginHandler.h
Go to the documentation of this file.
1 #ifndef DTConfigPluginHandler_H
2 #define DTConfigPluginHandler_H
3 
14 //----------------------
15 // Base Class Headers --
16 //----------------------
18 
19 //------------------------------------
20 // Collaborating Class Declarations --
21 //------------------------------------
22 
23 
24 //---------------
25 // C++ Headers --
26 //---------------
27 #include <string>
28 #include <map>
29 
30 // ---------------------
31 // -- Class Interface --
32 // ---------------------
33 
35 
36  public:
37 
40  virtual ~DTConfigPluginHandler();
41 
44  static void build();
46 
48  virtual int get( const edm::EventSetup& context,
49  int cfgId, const DTKeyedConfig*& obj );
50  virtual int get( const DTKeyedConfigListRcd& keyRecord,
51  int cfgId, const DTKeyedConfig*& obj );
52  virtual void getData( const edm::EventSetup& context,
53  int cfgId, std::vector<std::string>& list );
54  virtual void getData( const DTKeyedConfigListRcd& keyRecord,
55  int cfgId, std::vector<std::string>& list );
56 
57  void purge();
58 
59  static int maxBrickNumber;
60  static int maxStringNumber;
61  static int maxByteNumber;
62 
63  private:
64 
70 
71  typedef std::pair<int,const DTKeyedConfig*> counted_brick;
72  std::map<int,counted_brick> brickMap;
76 
77 };
78 
79 #endif // DTConfigPluginHandler_H
80 
81 
const DTConfigPluginHandler & operator=(const DTConfigPluginHandler &x)
std::map< int, counted_brick > brickMap
std::pair< int, const DTKeyedConfig * > counted_brick
tuple obj
Example code starts here #.
Definition: VarParsing.py:655
static void build()
build static object
void purge()
purge db copy
virtual void getData(const edm::EventSetup &context, int cfgId, std::vector< std::string > &list)
Definition: DDAxes.h:10
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