Go to the documentation of this file. 1 #ifndef DTUserKeyedConfigHandler_H
2 #define DTUserKeyedConfigHandler_H
33 namespace persistency {
77 std::shared_ptr<coral::ISessionProxy>
isession;
80 static bool sameConfigList(
const std::vector<DTConfigKey>& cfgl,
const std::vector<DTConfigKey>& cfgr);
85 #endif // DTUserKeyedConfigHandler_H
DTUserKeyedConfigHandler(const edm::ParameterSet &ps)
const cond::persistency::KeyList * keyList
~DTUserKeyedConfigHandler() override
static bool sameConfigList(const std::vector< DTConfigKey > &cfgl, const std::vector< DTConfigKey > &cfgr)
void chkConfigList(const std::map< int, bool > &userBricks)
std::string brickContainer
std::vector< DTConfigKey > userConf
std::string id() const override
std::string onlineConnect
void setList(const cond::persistency::KeyList *list)
std::string onlineAuthentication
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
void getNewObjects() override
std::shared_ptr< coral::ISessionProxy > isession
bool userDiscardedKey(int key)