1 #ifndef FWCore_PythonParameterSet_PythonParameterSet_h
2 #define FWCore_PythonParameterSet_PythonParameterSet_h
53 std::vector<T>
v = getParameter<std::vector<T> >(tracked,
name);
62 std::vector<T>
v = edm::toVector<T>(
value);
94 std::string
const&
data) {
107 unsigned int end,
unsigned int endSub) {
112 unsigned int end,
unsigned int endLumi,
unsigned int endSub) {
113 return edm::EventRange(start, startLumi, startSub, end, endLumi, endSub);
edm::ParameterSet theParameterSet
edm::EventID newEventID(unsigned int run, unsigned int lumi, unsigned int event)
PythonParameterSet getPSet(bool tracked, std::string const &name) const
static PFTauRenderPlugin instance
PythonParameterSet newPSet() const
PythonParameterSet(edm::ParameterSet const &p)
T getParameter(bool tracked, std::string const &name) const
edm::ParameterSet const & pset() const
void addParameters(bool tracked, std::string const &name, boost::python::list value)
unfortunate side effect: destroys the original list!
boost::python::list getParameters(bool tracked, std::string const &name) const
templated on the type of the contained object
boost::python::list getVPSet(bool tracked, std::string const &name)
void addParameter(bool tracked, std::string const &name, T const &value)
edm::LuminosityBlockID newLuminosityBlockID(unsigned int run, unsigned int lumi)
edm::ESInputTag newESInputTag(std::string const &module, std::string const &data)
edm::EventRange newEventRange(unsigned int start, unsigned int startLumi, unsigned int startSub, unsigned int end, unsigned int endLumi, unsigned int endSub)
void addPSet(bool tracked, std::string const &name, PythonParameterSet const &ppset)
boost::python::list toPythonList(const std::vector< T > &v)
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 but the state exists so we define the behavior If all triggers are the negative crieriion will lead to accepting the event(this again matches the behavior of"!*"before the partial wildcard feature was incorporated).The per-event"cost"of each negative criterion with multiple relevant triggers is about the same as!*was in the past
edm::LuminosityBlockRange newLuminosityBlockRange(unsigned int start, unsigned int startSub, unsigned int end, unsigned int endSub)
edm::ParameterSet & pset()
edm::InputTag newInputTag(std::string const &label, std::string const &instance, std::string const &process)
void addNewFileInPath(bool tracked, std::string const &name, std::string const &value)
void addVPSet(bool tracked, std::string const &name, boost::python::list value)
char data[epos_bytes_allocation]
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