1 #ifndef HLTrigger_HLTfilters_TriggerExpressionData_h
2 #define HLTrigger_HLTfilters_TriggerExpressionData_h
21 namespace triggerExpression {
62 m_throw(config.getParameter<bool>(
"throw")),
88 bool l1techIgnorePrescales,
245 #endif // HLTrigger_HLTfilters_TriggerExpressionData_h
bool l1tConfigurationUpdated() const
void setDaqPartitions(unsigned int daqPartitions)
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
const L1GtTriggerMask * m_l1tTechMask
void setL1tResultsTag(edm::InputTag const &tag)
Data(const edm::ParameterSet &config, edm::ConsumesCollector &&iC)
const L1GtTriggerMask & l1tTechMask() const
void setL1tIgnoreMask(bool l1tIgnoreMask)
const edm::TriggerNames & hltMenu() const
unsigned long long EventNumber_t
bool ignoreL1Mask() const
edm::InputTag m_l1tResultsTag
const L1GtTriggerMask * m_l1tAlgoMask
const L1GlobalTriggerReadoutRecord & l1tResults() const
const L1GtTriggerMenu & l1tMenu() const
edm::InputTag m_hltResultsTag
unsigned int m_daqPartitions
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
void setL1techIgnorePrescales(bool l1techIgnorePrescales)
Data(edm::InputTag const &hltResultsTag, edm::InputTag const &l1tResultsTag, unsigned int daqPartitions, bool l1tIgnoreMask, bool l1techIgnorePrescales, bool doThrow, edm::ConsumesCollector &&iC)
const L1GlobalTriggerReadoutRecord * m_l1tResults
bool m_l1techIgnorePrescales
unsigned int daqPartitions() const
bool setEvent(const edm::Event &event, const edm::EventSetup &setup)
edm::ParameterSetID m_hltCacheID
edm::EDGetTokenT< L1GlobalTriggerReadoutRecord > m_l1tResultsToken
edm::EventNumber_t m_eventNumber
bool ignoreL1TechPrescales() const
volatile std::atomic< bool > shutdown_flag false
const L1GtTriggerMenu * m_l1tMenu
unsigned long long m_l1tCacheID
void setup(std::vector< TH2F > &depth, std::string name, std::string units="")
bool hltConfigurationUpdated() const
const L1GtTriggerMask & l1tAlgoMask() const