test
CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
SiStripBadModuleFedErrService.h
Go to the documentation of this file.
1 #ifndef SiStripESSources_SiStripBadModuleFedErrService_h
2 #define SiStripESSources_SiStripBadModuleFedErrService_h
3 // -*- C++ -*-
4 //
5 //
6 #include <string>
7 
16 
17 class MonitorElement;
18 class SiStripQuality;
19 
20 class SiStripBadModuleFedErrService : public SiStripDepCondObjBuilderBase<SiStripBadStrip, SiStripFedCabling> {
21 
22 public:
23 
26 
28  void getMetaDataString(std::stringstream& ss);
29 
31  virtual bool checkForCompatibility(std::string ss);
32 
33  void getObj(SiStripBadStrip* & obj, const SiStripFedCabling * cabling){obj = readBadComponentsFromFed(cabling);}
34  uint32_t getRunNumber() const;
35 
36 private:
37 
38 
40  bool openRequestedFile();
41  void getFedBadChannelList(MonitorElement* me, std::vector<std::pair<uint16_t, uint16_t>>& list);
42  float getProcessedEvents();
43 
45 
48 };
49 #endif
void getObj(SiStripBadStrip *&obj, const SiStripFedCabling *cabling)
void getMetaDataString(std::stringstream &ss)
Used to fill the logDB.
SiStripBadModuleFedErrService(const edm::ParameterSet &, const edm::ActivityRegistry &)
SiStripBadStrip * readBadComponentsFromFed(const SiStripFedCabling *cabling)
Contains cabling info at the device level, including DetId, APV pair numbers, hardware addresses...
void getFedBadChannelList(MonitorElement *me, std::vector< std::pair< uint16_t, uint16_t >> &list)
virtual bool checkForCompatibility(std::string ss)
Check is the transfer is needed.
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