38 throw(std::runtime_error);
41 throw(std::runtime_error);
44 throw(std::runtime_error);
void setTaskList(int list)
void setNumEvents(int num)
void setMonRunOutcomeDef(const MonRunOutcomeDef &outcomeDef)
int getTaskOutcome() const
MonRunOutcomeDef getMonRunOutcomeDef() const
void setRootfileName(std::string name)
void writeDB(const EcalLogicID *ecid, const MonRunDat *item, MonRunIOV *iov)
void setTaskOutcome(int outcome)
void fetchData(std::map< EcalLogicID, MonRunDat > *fillMap, MonRunIOV *iov)
MonRunOutcomeDef m_outcomeDef
std::string m_rootfileName
std::string getRootfileName() const
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