CMS 3D CMS Logo
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
HLTBool.cc
Go to the documentation of this file.
1 
11 #include "HLTrigger/HLTfilters/interface/HLTBool.h"
12 #include "FWCore/MessageLogger/interface/MessageLogger.h"
13 #include "FWCore/ParameterSet/interface/ConfigurationDescriptions.h"
14 #include "FWCore/ParameterSet/interface/ParameterSetDescription.h"
15 
16 //
17 // constructors and destructor
18 //
19 HLTBool::HLTBool(const edm::ParameterSet& iConfig) :
20  result_(iConfig.getParameter<bool> ("result"))
21 {
22  LogDebug("HLTBool") << " configured result is: " << result_;
23 }
24 
25 HLTBool::~HLTBool()
26 {
27 }
28 
29 void
30 HLTBool::fillDescriptions(edm::ConfigurationDescriptions& descriptions) {
31  edm::ParameterSetDescription desc;
32  desc.add<bool>("result", false);
33  descriptions.add("hltBool", desc);
34 }
35 
36 //
37 // member functions
38 //
39 
40 // ------------ method called to produce the data ------------
41 bool
42 HLTBool::filter(edm::StreamID, edm::Event & event, edm::EventSetup const & setup) const
43 {
44  return result_;
45 }
LogDebug
#define LogDebug(id)
Definition: MessageLogger.h:501
HLTBool::HLTBool
HLTBool(const edm::ParameterSet &)
Definition: HLTBool.cc:19
HLTBool::fillDescriptions
static void fillDescriptions(edm::ConfigurationDescriptions &descriptions)
Definition: HLTBool.cc:30
HLTBool::~HLTBool
~HLTBool()
Definition: HLTBool.cc:25
edm::ParameterSetDescription::add
ParameterDescriptionBase * add(U const &iLabel, T const &value)
Definition: ParameterSetDescription.h:89
event
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
edm::ConfigurationDescriptions::add
void add(std::string const &label, ParameterSetDescription const &psetDescription)
Definition: ConfigurationDescriptions.cc:65
HLTBool::result_
bool result_
boolean result
Definition: HLTBool.h:37
HLTBool::filter
virtual bool filter(edm::StreamID, edm::Event &, edm::EventSetup const &) const overridefinal
Definition: HLTBool.cc:42
Generated for CMSSW Reference Manual by doxygen 1.8.5