test
CMS 3D CMS Logo
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
HLTGetRaw.cc
Go to the documentation of this file.
1 
10 #include "FWCore/MessageLogger/interface/MessageLogger.h"
11 #include "FWCore/Utilities/interface/InputTag.h"
12 #include "DataFormats/Common/interface/Handle.h"
13 #include "HLTrigger/HLTanalyzers/interface/HLTGetRaw.h"
14 
15 //
16 // constructors and destructor
17 //
18 HLTGetRaw::HLTGetRaw(const edm::ParameterSet& ps) :
19  rawDataCollection_( ps.getParameter<edm::InputTag>("RawDataCollection") ),
20  rawDataToken_( consumes<FEDRawDataCollection>(rawDataCollection_) )
21 {
22 }
23 
24 HLTGetRaw::~HLTGetRaw()
25 {
26 }
27 
28 void
29 HLTGetRaw::fillDescriptions(edm::ConfigurationDescriptions& descriptions) {
30  edm::ParameterSetDescription desc;
31  desc.add<edm::InputTag>("RawDataCollection", edm::InputTag("rawDataCollector"));
32  descriptions.add("hltGetRaw", desc);
33 }
34 
35 //
36 // member functions
37 //
38 
39 // ------------ method called to analyze the data ------------
40 void
41 HLTGetRaw::analyze(edm::StreamID sid, edm::Event const & event, edm::EventSetup const & setup) const
42 {
43  edm::Handle<FEDRawDataCollection> rawDataHandle ;
44  event.getByToken(rawDataToken_, rawDataHandle );
45 
46  LogDebug("DigiInfo") << "Loaded Raw Data Collection: " << rawDataCollection_;
47 }
LogDebug
#define LogDebug(id)
Definition: MessageLogger.h:501
HLTGetRaw::HLTGetRaw
HLTGetRaw(const edm::ParameterSet &)
Definition: HLTGetRaw.cc:18
HLTGetRaw::~HLTGetRaw
~HLTGetRaw()
Definition: HLTGetRaw.cc:24
HLT_25ns10e33_v2_cff.InputTag
tuple InputTag
Definition: HLT_25ns10e33_v2_cff.py:58467
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
HLTGetRaw::analyze
virtual void analyze(edm::StreamID, edm::Event const &, edm::EventSetup const &) const overridefinal
Definition: HLTGetRaw.cc:41
HLTGetRaw::fillDescriptions
static void fillDescriptions(edm::ConfigurationDescriptions &descriptions)
Definition: HLTGetRaw.cc:29
HLTGetRaw::rawDataToken_
edm::EDGetTokenT< FEDRawDataCollection > rawDataToken_
Definition: HLTGetRaw.h:39
HLTGetRaw::rawDataCollection_
edm::InputTag rawDataCollection_
Definition: HLTGetRaw.h:38
edm::ConfigurationDescriptions::add
void add(std::string const &label, ParameterSetDescription const &psetDescription)
Definition: ConfigurationDescriptions.cc:65
Generated for CMSSW Reference Manual by doxygen 1.8.5