1 #ifndef HLTrigger_HLTfilters_TriggerExpressionData_h
2 #define HLTrigger_HLTfilters_TriggerExpressionData_h
20 namespace triggerExpression {
55 m_throw(config.getParameter<bool>(
"throw")),
77 bool l1tIgnoreMaskAndPrescale,
201 #endif // HLTrigger_HLTfilters_TriggerExpressionData_h
bool l1tConfigurationUpdated() const
bool configurationUpdated() const
The Signals That Services Can Subscribe To This is based on ActivityRegistry and is current per Services can connect to the signals distributed by the ActivityRegistry in order to monitor the activity of the application Each possible callback has some defined which we here list in angle e< void, edm::EventIDconst &, edm::Timestampconst & > We also list in braces which AR_WATCH_USING_METHOD_ is used for those or
void setL1tResultsTag(edm::InputTag const &tag)
Data(const edm::ParameterSet &config, edm::ConsumesCollector &&iC)
const L1TUtmTriggerMenu & l1tMenu() const
Data(edm::InputTag const &hltResultsTag, edm::InputTag const &l1tResultsTag, bool l1tIgnoreMaskAndPrescale, bool doThrow, edm::ConsumesCollector &&iC)
const edm::TriggerNames & hltMenu() const
edm::EDGetTokenT< GlobalAlgBlkBxCollection > m_l1tResultsToken
unsigned long long EventNumber_t
edm::InputTag m_l1tResultsTag
void setL1tIgnoreMaskAndPrescale(bool l1tIgnoreMaskAndPrescale)
bool ignoreL1MaskAndPrescale() const
edm::InputTag m_hltResultsTag
edm::EventNumber_t eventNumber() const
const edm::TriggerResults * m_hltResults
void setHltResultsTag(edm::InputTag const &tag)
edm::EDGetTokenT< edm::TriggerResults > m_hltResultsToken
const edm::TriggerResults & hltResults() const
void setThrow(bool doThrow)
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 std::vector< bool > & l1tResults() const
const L1TUtmTriggerMenu * m_l1tMenu
const std::vector< bool > * m_l1tResults
edm::ParameterSetID m_hltCacheID
bool m_l1tIgnoreMaskAndPrescale
edm::EventNumber_t m_eventNumber
volatile std::atomic< bool > shutdown_flag false
unsigned long long m_l1tCacheID
bool hltConfigurationUpdated() const