CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
DTKeyedConfigPopConAnalyzer.cc
Go to the documentation of this file.
9 
10 //typedef popcon::PopConAnalyzer<DTKeyedConfigHandler> DTKeyedConfigPopConAnalyzer;
11 class DTKeyedConfigPopConAnalyzer: public popcon::PopConAnalyzer<DTKeyedConfigHandler> {
12  public:
14  popcon::PopConAnalyzer<DTKeyedConfigHandler>( pset ),
15  copyData( pset.getParameter<edm::ParameterSet>("Source").
16  getUntrackedParameter<bool> ( "copyData", true ) )
17  {}
19  virtual void analyze(const edm::Event& e, const edm::EventSetup& s) override{
20 
21  if ( !copyData ) return;
22 
24  std::cout<<"got eshandle"<<std::endl;
25  s.get<DTKeyedConfigListRcd>().get(klh);
26  std::cout<<"got context"<<std::endl;
27  cond::persistency::KeyList const & kl= *klh.product();
29  for ( size_t i = 0; i < list->size(); i++ ) {
30  boost::shared_ptr<DTKeyedConfig> kelem = list->get<DTKeyedConfig>( i );
31  if ( kelem.get() )
32  std::cout << kelem->getId() << std::endl;
33  }
35 
36  }
37  private:
38  bool copyData;
39 };
40 
41 
43 
size_t size() const
Definition: KeyList.h:55
int i
Definition: DBlmapReader.cc:9
#define DEFINE_FWK_MODULE(type)
Definition: MakerMacros.h:17
boost::shared_ptr< T > get(size_t n) const
Definition: KeyList.h:39
static void setList(cond::persistency::KeyList *list)
const T & get() const
Definition: EventSetup.h:56
T const * product() const
Definition: ESHandle.h:86
DTKeyedConfigPopConAnalyzer(const edm::ParameterSet &pset)
virtual void analyze(const edm::Event &e, const edm::EventSetup &s) override
tuple cout
Definition: gather_cfg.py:121
PopConAnalyzer(const edm::ParameterSet &pset)
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 list("!*","!HLTx*"if it matches 2 triggers or more) will accept the event if all the matching triggers are FAIL.It will reject the event if any of the triggers are PASS or EXCEPTION(this matches the behavior of"!*"before the partial wildcard feature was incorporated).Triggers which are in the READY state are completely ignored.(READY should never be returned since the trigger paths have been run