CMS 3D CMS Logo

DTUserKeyedConfigHandler.h
Go to the documentation of this file.
1 #ifndef DTUserKeyedConfigHandler_H
2 #define DTUserKeyedConfigHandler_H
3 
14 //----------------------
15 // Base Class Headers --
16 //----------------------
18 
19 //------------------------------------
20 // Collaborating Class Declarations --
21 //------------------------------------
25 #include <memory>
26 #include <string>
27 
28 namespace coral {
29  class ISessionProxy;
30 }
31 
32 namespace cond {
33  namespace persistency {
34  class KeyList;
35  }
36 }
37 
38 //---------------
39 // C++ Headers --
40 //---------------
41 
42 
43 // ---------------------
44 // -- Class Interface --
45 // ---------------------
46 
48 
49  public:
50 
54 
57  ~DTUserKeyedConfigHandler() override;
58 
61  void getNewObjects() override;
63  std::string id() const override;
64 
65  static void setList( cond::persistency::KeyList* list );
66 
67  private:
68 
69  int dataRun;
75  std::vector<DTConfigKey> userConf;
76  bool writeKeys;
77  bool writeData;
79 
81  std::shared_ptr<coral::ISessionProxy> isession;
82  void chkConfigList( const std::map<int,bool>& userBricks );
83  bool userDiscardedKey( int key );
84  static bool sameConfigList( const std::vector<DTConfigKey>& cfgl,
85  const std::vector<DTConfigKey>& cfgr );
86 
88 
89 };
90 
91 
92 #endif // DTUserKeyedConfigHandler_H
93 
94 
95 
96 
97 
98 
std::vector< DTConfigKey > userConf
static cond::persistency::KeyList * keyList
Definition: Binary.h:9
Definition: plugin.cc:24
std::shared_ptr< coral::ISessionProxy > isession
cond::persistency::ConnectionPool connection
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