Go to the documentation of this file. 1 #ifndef FWCore_PyDevParameterSet_Python11ParameterSet_h
2 #define FWCore_PyDevParameterSet_Python11ParameterSet_h
3 #include <pybind11/pybind11.h>
49 std::vector<T>
v = getParameter<std::vector<T> >(tracked,
name);
56 std::vector<T>
v = cmspython3::toVector<T>(
value);
93 unsigned int startSub,
95 unsigned int endSub) {
void addVPSet(bool tracked, std::string const &name, pybind11::list value)
Python11ParameterSet newPSet() const
edm::ParameterSet theParameterSet
unsigned int LuminosityBlockNumber_t
edm::InputTag newInputTag(std::string const &label, std::string const &instance, std::string const &process)
std::string dump(unsigned int indent=0) const
T getParameter(bool tracked, std::string const &name) const
unsigned long long EventNumber_t
void addPSet(bool tracked, std::string const &name, Python11ParameterSet const &ppset)
edm::LuminosityBlockRange newLuminosityBlockRange(unsigned int start, unsigned int startSub, unsigned int end, unsigned int endSub)
pybind11::list getVPSet(bool tracked, std::string const &name)
void addParameters(bool tracked, std::string const &name, pybind11::list value)
unfortunate side effect: destroys the original list!
static PFTauRenderPlugin instance
Python11ParameterSet(edm::ParameterSet const &p)
pybind11::list getParameters(bool tracked, std::string const &name) const
templated on the type of the contained object
edm::LuminosityBlockID newLuminosityBlockID(unsigned int run, unsigned int lumi)
void addNewFileInPath(bool tracked, std::string const &name, std::string const &value)
char data[epos_bytes_allocation]
edm::ESInputTag newESInputTag(std::string const &module, std::string const &data)
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
edm::EventRange newEventRange(edm::RunNumber_t start, edm::LuminosityBlockNumber_t startLumi, edm::EventNumber_t startSub, edm::RunNumber_t end, edm::LuminosityBlockNumber_t endLumi, edm::EventNumber_t endSub)
edm::ParameterSet const & pset() const
void addParameter(bool tracked, std::string const &name, T const &value)
pybind11::list toPython11List(const std::vector< T > &v)
Python11ParameterSet getPSet(bool tracked, std::string const &name) const
edm::ParameterSet & pset()
edm::EventID newEventID(edm::RunNumber_t run, edm::LuminosityBlockNumber_t lumi, edm::EventNumber_t event)