10 std::vector<std::string> psetNames;
12 for (
unsigned int i=0;
i!=psetNames.size();++
i){
25 for (;it!=it_end;++it) it->second->setHolder(hn);
31 for (;it!=it_end;++it) it->second->print();
38 ss<<std::setw(10)<<
event.id().run()<<
" : " 39 <<std::setw(10)<<
event.id().event();
40 for (;it!=it_end;++it) {
41 if (it->second->compute(event))
42 ss<<
" : "<<it->first<<
"="<<(*it->second)(
event);
44 ss<<
" : "<<it->first<<
" N/A";
54 edm::LogError(
"VariableHelper")<<
"I don't know anything named: "<<name
55 <<
" list of available variables follows.";
T getParameter(std::string const &) const
VariableHelper(const edm::ParameterSet &iConfig, edm::ConsumesCollector &iC)
const CachingVariable * variable(std::string name) const
std::map< std::string, const CachingVariable * > variables_
std::string printValues(const edm::Event &event) 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 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
void setHolder(std::string hn)
size_t getParameterSetNames(std::vector< std::string > &output, bool trackiness=true) const
std::map< std::string, const CachingVariable * >::const_iterator iterator
T get(const Candidate &c)