CMS 3D CMS Logo

Functions
PI Namespace Reference

Functions

boost::python::list mk_input (const std::string &tagName, cond::Time_t start, cond::Time_t end)
 
boost::python::list mk_input (const std::string &tagName0, cond::Time_t start0, cond::Time_t end0, const std::string &tagName1, cond::Time_t start1, cond::Time_t end1)
 

Function Documentation

◆ mk_input() [1/2]

boost::python::list PI::mk_input ( const std::string &  tagName,
cond::Time_t  start,
cond::Time_t  end 
)
inline

Definition at line 20 of file PayloadInspector.h.

20  {
22  ret.append(boost::python::make_tuple(tagName, std::to_string(start), std::to_string(end)));
23  return ret;
24  }

References end, list(), runTheMatrix::ret, and JetPartonCorrections_cff::tagName.

◆ mk_input() [2/2]

boost::python::list PI::mk_input ( const std::string &  tagName0,
cond::Time_t  start0,
cond::Time_t  end0,
const std::string &  tagName1,
cond::Time_t  start1,
cond::Time_t  end1 
)
inline

Definition at line 25 of file PayloadInspector.h.

30  {
32  ret.append(boost::python::make_tuple(tagName0, std::to_string(start0), std::to_string(end0)));
33  ret.append(boost::python::make_tuple(tagName1, std::to_string(start1), std::to_string(end1)));
34  return ret;
35  }

References list(), and runTheMatrix::ret.

runTheMatrix.ret
ret
prodAgent to be discontinued
Definition: runTheMatrix.py:355
start
Definition: start.py:1
end
#define end
Definition: vmac.h:39
list
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
JetPartonCorrections_cff.tagName
tagName
Definition: JetPartonCorrections_cff.py:12