|
|
Go to the documentation of this file.
72 m_triggerPattern(m_bunchCrossings.
size(),
false),
73 m_daqPartitions(
config.getParameter<unsigned
int>(
"daqPartitions")),
76 m_triggerMasked(
false),
77 m_ignoreL1Mask(
config.getParameter<
bool>(
"ignoreL1Mask")),
81 std::vector<int>
pattern(
config.getParameter<std::vector<int> >(
"triggerPattern"));
83 throw cms::Exception(
"Configuration") <<
"\"bunchCrossings\" and \"triggerPattern\" parameters do not match";
85 for (
unsigned int i = 0;
i <
pattern.size(); ++
i)
94 desc.add<
std::string>(
"triggerBit",
"L1Tech_RPC_TTU_pointing_Cosmics.v0");
96 std::vector<int> temp1;
103 desc.add<std::vector<int> >(
"bunchCrossings", temp1);
105 desc.add<
unsigned int>(
"daqPartitions", 1);
106 desc.add<
bool>(
"ignoreL1Mask",
false);
107 desc.add<
bool>(
"invert",
false);
108 desc.add<
bool>(
"throw",
true);
110 std::vector<int> temp1;
117 desc.add<std::vector<int> >(
"triggerPattern", temp1);
119 descriptions.
add(
"hltLevel1Pattern",
desc);
136 AlgorithmMap::const_iterator
entry;
146 <<
"requested L1 trigger \"" <<
m_triggerBit <<
"\" does not exist in the current L1 menu";
186 const std::vector<bool>&
word =
bool check(const edm::EventSetup &iSetup)
edm::InputTag m_gtReadoutRecord
edm::ESWatcher< L1GtTriggerMaskTechTrigRcd > m_watchTechnicalMask
#define DEFINE_FWK_MODULE(type)
void add(std::string const &label, ParameterSetDescription const &psetDescription)
std::vector< int > m_bunchCrossings
static void fillDescriptions(edm::ConfigurationDescriptions &descriptions)
edm::ESWatcher< L1GtTriggerMenuRcd > m_watchL1Menu
~HLTLevel1Pattern() override
unsigned int m_daqPartitions
const std::vector< unsigned int > & gtTriggerMask() const
get the trigger mask
const DecisionWord & decisionWord(int bxInEventValue) const
unsigned int m_triggerNumber
edm::EDGetTokenT< L1GlobalTriggerReadoutRecord > m_gtReadoutRecordToken
edm::ESWatcher< L1GtTriggerMaskAlgoTrigRcd > m_watchPhysicsMask
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::EventID const &, edm::Timestamp const & > We also list in braces which AR_WATCH_USING_METHOD_ is used for those or
const TechnicalTriggerWord & technicalTriggerWord(int bxInEventValue) const
HLTLevel1Pattern(const edm::ParameterSet &)
std::vector< int > m_triggerPattern
bool filter(edm::Event &, const edm::EventSetup &) override