1 #ifndef DTOccupancyTest_H
2 #define DTOccupancyTest_H
bool runOnNoiseOccupancies
std::map< int, MonitorElement * > wheelHistos
void analyze(const edm::Event &event, const edm::EventSetup &context)
Analyze.
bool runOnInTimeOccupancies
int runOccupancyTest(TH2F *histo, const DTChamberId &chId, float &chamberPercentage)
MonitorElement * summaryHisto
std::string nameMonitoredHisto
virtual ~DTOccupancyTest()
Destructor.
void beginLuminosityBlock(edm::LuminosityBlock const &lumiSeg, edm::EventSetup const &context)
DTOccupancyTest(const edm::ParameterSet &ps)
Constructor.
std::string getMEName(std::string histoTag, const DTChamberId &chId)
Get the ME name.
void beginRun(edm::Run const &run, edm::EventSetup const &context)
BeginRun.
bool runOnAllHitsOccupancies
void endLuminosityBlock(edm::LuminosityBlock const &lumiSeg, edm::EventSetup const &context)
DQM Client Diagnostic.
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::ESHandle< DTGeometry > muonGeom
void bookHistos(const int wheelId, std::string folder, std::string histoTag)
book the summary histograms
std::set< DTLayerId > monitoredLayers
std::string topFolder() const
MonitorElement * glbSummaryHisto