1 #include <boost/shared_ptr.hpp>
19 namespace triggerExpression {
25 event.getByToken(
token, handle);
35 template <
typename R,
typename T>
39 setup.get<
R>().
get(handle);
const L1GtTriggerMask * m_l1tTechMask
const L1GtTriggerMask * m_l1tAlgoMask
Strings const & triggerNames() const
ParameterSetID const & parameterSetID() const
const edm::TriggerResults * m_hltResults
edm::EDGetTokenT< edm::TriggerResults > m_hltResultsToken
const edm::TriggerNames * m_hltMenu
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
bool setEvent(const edm::Event &event, const edm::EventSetup &setup)
const L1GlobalTriggerReadoutRecord * m_l1tResults
T const * product() const
T const * product() const
edm::ParameterSetID m_hltCacheID
edm::EDGetTokenT< L1GlobalTriggerReadoutRecord > m_l1tResultsToken
edm::EventNumber_t m_eventNumber
std::shared_ptr< cms::Exception > whyFailed() const
const L1GtTriggerMenu * m_l1tMenu
unsigned long long m_l1tCacheID
void setup(std::vector< TH2F > &depth, std::string name, std::string units="")