14 edm::LogInfo(
"HLTEventSelector") <<
"constructed with \n"
16 <<
" #pathnames = " << pathNames_.
size();
35 unsigned int trgSize = trgNames.
size();
47 for ( std::vector<std::string>::const_iterator
i=
pathNames_.begin();
51 if ( index==trgSize ) {
57 if ( hltHandle->accept(index) ) {
58 LogDebug(
"HLTEventSelector") <<
"Event selected by " << *
i;
63 LogDebug(
"HLTEventSelector") <<
"Event rejected";
EDGetTokenT< ProductType > consumes(edm::InputTag const &tag)
T getParameter(std::string const &) const
Strings::size_type size() const
HLTEventSelector(const edm::ParameterSet &pset, edm::ConsumesCollector &&iC)
edm::InputTag triggerResults_
tag for input collection
Strings const & triggerNames() const
unsigned int triggerIndex(std::string const &name) const
edm::EDGetTokenT< edm::TriggerResults > triggerResultsToken_
unsigned int size() const
Get number of paths stored.
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
virtual bool select(const edm::Event &) const
decision of the selector module
std::vector< std::string > pathNames_
trigger path names (ORed)