CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
FUShmDQMOutputService.h
Go to the documentation of this file.
1 #ifndef FUShmDQMOutputService_H
2 #define FUShmDQMOutputService_H
3 
29 
30 #include "xdata/UnsignedInteger32.h"
31 
33 {
34  public:
36  edm::ActivityRegistry &actReg);
38 
39  //serviceweb interface
41  void publish(xdata::InfoSpace *);
42 
44  const edm::EventSetup &eventSetup);
45 
46  // test routines to check on timing of various signals
47  void postEndJobProcessing();
49  void preBeginRun(const edm::RunID &runID, const edm::Timestamp &timestamp);
51  bool attachToShm();
52  bool detachFromShm();
53  void reset(){
54  nbUpdates_ = 0;
56  }
57  protected:
59 
61  std::string folderPath);
62 
63  private:
64  void writeShmDQMData(DQMEventMsgBuilder const& dqmMsgBuilder);
65 
66  std::vector<char> messageBuffer_;
71  unsigned int firstLumiSectionSeen_;
78 
80 
81  xdata::UnsignedInteger32 nbUpdates_;
82  char host_name_[255];
83 
84  const std::string input;
85  const std::string dqm;
86 
87  static bool fuIdsInitialized_;
89 
90  bool attach_;
91  public:
92  void setAttachToShm();
93 };
94 
95 #endif
#define Input(cl)
Definition: vmac.h:189
FUShmDQMOutputService(const edm::ParameterSet &pset, edm::ActivityRegistry &actReg)
void postEndLumi(edm::LuminosityBlock const &, edm::EventSetup const &)
void writeShmDQMData(DQMEventMsgBuilder const &dqmMsgBuilder)
std::vector< char > messageBuffer_
edm::StreamDQMSerializer serializeWorker_
unsigned int lumiSectionOfPreviousUpdate_
void publish(xdata::InfoSpace *)
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
evf::FUShmBuffer * shmBuffer_
unsigned int uint32
Definition: MsgTools.h:13
tuple out
Definition: dbtoconf.py:99
xdata::UnsignedInteger32 nbUpdates_
void postEventProcessing(const edm::Event &event, const edm::EventSetup &eventSetup)
void preBeginRun(const edm::RunID &runID, const edm::Timestamp &timestamp)
void postSourceConstructionProcessing(const edm::ModuleDescription &modDesc)
edm::StreamDQMDeserializer deserializeWorker_
void findMonitorElements(DQMEvent::TObjectTable &toTable, std::string folderPath)
#define Output(cl)
Definition: vmac.h:193
void defaultWebPage(xgi::Input *in, xgi::Output *out)
std::map< std::string, std::vector< TObject * > > TObjectTable