1 #ifndef PhysicsTools_MVAComputer_MVAModuleHelper_h
2 #define PhysicsTools_MVAComputer_MVAModuleHelper_h
23 #include <boost/bind.hpp>
32 namespace PhysicsTools {
42 template<
typename Object>
48 {
return object.compute(name); }
61 template<
class Record,
typename Object,
62 class Filler = MVAModuleHelperDefaultFiller<Object> >
85 name(name),
filler(name) {}
87 name(name),
filler(name), value(value) {}
89 inline bool update(
const Object &
object)
const
92 return !std::isfinite(
value);
108 template<
class Record,
typename Object,
class Filler>
115 if (cache.update(container,
label.c_str()) && cache)
119 template<
class Record,
typename Object,
class Filler>
124 setup.
get<
Record>().
get(esLabel, handle);
126 if (cache.update(container,
label.c_str()) && cache)
130 template<
class Record,
typename Object,
class Filler>
134 const std::vector<PhysicsTools::Calibration::Variable> &vars =
137 for(std::vector<PhysicsTools::Calibration::Variable>::const_iterator
138 iter = vars.begin(); iter != vars.end(); ++iter)
139 if (std::strncmp(iter->name.c_str(),
"__", 2) != 0)
143 template<
class Record,
typename Object,
class Filler>
145 const Object &
object)
const
149 return cache->eval(
values);
152 template<
class Record,
typename Object,
class Filler>
164 bind(std::plus<int>(), _1,
169 list.
add(kTargetId, target);
170 list.
add(kWeightId, weight);
171 for(
typename std::vector<Value>::const_iterator iter =
values.begin();
172 iter !=
values.end(); ++iter)
173 list.
add(iter->getName(), iter->getValue());
180 #endif // PhysicsTools_MVAComputer_MVAModuleHelper_h
reco::JetExtendedAssociation::JetExtendedData Value
T const * product() const
void setup(std::vector< TH2F > &depth, std::string name, std::string units="")
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