EMU Reference Histogram Comparison Unit

18
EMU Reference Histogram Comparison Unit R. Cavanaugh, V. Barashko, A. Korytov

description

EMU Reference Histogram Comparison Unit. R. Cavanaugh, V. Barashko, A. Korytov. EMU DQM Architecture. Warning display GUI. Plot display GUI. Unpacking Analysis. DQM unpacking analysis. Display server HIST concentrator HIST-REF comp. unit. Problem correlator. DQM unpacking - PowerPoint PPT Presentation

Transcript of EMU Reference Histogram Comparison Unit

Page 1: EMU Reference Histogram Comparison Unit

EMU Reference Histogram Comparison Unit

R. Cavanaugh, V. Barashko,

A. Korytov

Page 2: EMU Reference Histogram Comparison Unit

EMU DQM Architecture

DQMunpackinganalysis

DATA

DQMunpackinganalysis

DATA

DQMcontrol

andmonitor

Display serverHIST concentrator

HIST-REF comp. unit

DQM DB

DQM DBinterface

DQM contr/mon log

HIST files REF files DQM problem reports

actions

Problemcorrelator

Run Control

Warningdisplay

GUI

UnpackingAnalysisDATA

Plotdisplay

GUI

?

DQM active problems

cond/config DB

DQMcontrol

andmonitor

(Dec 11, 2004)

Page 3: EMU Reference Histogram Comparison Unit

EMU DQM Architecture

DQMunpackinganalysis

DATA

DQMunpackinganalysis

DATA

DQMcontrol

andmonitor

Display serverHIST concentrator

HIST-REF comp. unit

DQM DB

DQM DBinterface

DQM contr/mon log

HIST files REF files DQM problem reports

actions

Problemcorrelator

Run Control

Warningdisplay

GUI

UnpackingAnalysisDATA

Plotdisplay

GUI

?

DQM active problems

cond/config DB

Reference Histogram Comparisons

DQMcontrol

andmonitor

(Dec 11, 2004)

Page 4: EMU Reference Histogram Comparison Unit

Different EMU Types of Histograms & Canvases

• EMU DQM Canvas (Histograms) Hierarchy– DDU

• CSC Chamber (ID by crate and slot of DMB)– ALCT

» 8 canvases– CFEB

» 4 canvases– CLCT

» 9 canvases– SYNC

» 5 canvases– DMB

» 5 canvases– CSC Efficiency canvas

• 14 DDU canvases

• Total of 46 different “types” of canvases per DDU– Each canvas contains 1 or more histograms– Each DDU contains several chambers– Not yet finished defining additional canvases…

• “Summary” : produces a (global) high-level report – for all tests with references or rules– for all “types” of canvases – for all chambers.

Page 5: EMU Reference Histogram Comparison Unit

Different Kinds of Tests using Different Reference Sources

• Static Reference Sources– A Previous Run– Ideal Conditions (from detector knowledge)– etc

• Dynamic Reference Sources– Current Run– Rules (from detector knowledge)– Etc– Important because running conditions often change

• Tests– Current Run vs. A Previous Run– Current Run vs. Ideal Conditions– Current Run vs. Current Run– Current Run vs. Rules– etc

ME1

ME2

ME3

ME4

DT-10

DT-11

e.g. within a run, comparechamber performance againstexpected similar chambers

Page 6: EMU Reference Histogram Comparison Unit

Current Design from EMU DQM Architecture

• RefHistComparator produces summary report every ~5 min

– Updates DB

• RefServer continuously updates histos

– Sends reference canvases to Display GUI

• Display GUI should be as light as possible

– Should be agnostic about different canvases and references

• GUI easier to maintain and always works

– All the hard work is done on the DisplayServer

OnlineServer

REF-HISTComparator

Unit

DisplayServer

histolist

GUI Display

OnlineStream

Static etc

“Database”

Summary

Ref0Server

Ref1Server

Ideal

RefNServer

Page 7: EMU Reference Histogram Comparison Unit

Current Design Thoughts

• Design a base class container for reference canvases of all chambers– Of a particular canvas type!

• Design different reference comparison classes for each “type” of canvas

• For each canvas “type”, specify associated– References– Rules– Tests– (local) Summary Results

Page 8: EMU Reference Histogram Comparison Unit

Current Design Thoughts

Contains reference canvases (of a certain type) for all chambers

Page 9: EMU Reference Histogram Comparison Unit

Current Design Thoughts

Rules and Tests used to comparereference to online canvasesassociated with a certain type

Page 10: EMU Reference Histogram Comparison Unit

Current Design Thoughts

Produce summary report for all tests performed for this particular type of canvas

Page 11: EMU Reference Histogram Comparison Unit

Current Design Thoughts

List of all tests performed on alltypes of canvases

Page 12: EMU Reference Histogram Comparison Unit

Current Design Thoughts

Produce global summary report for all tests performed for all types of canvases

Page 13: EMU Reference Histogram Comparison Unit

Current Design Thoughts

Buffers to be sent to GUI to compare online canvases with different references (0,1,…,N)

Page 14: EMU Reference Histogram Comparison Unit

Current Design from EMU DQM Architecture

• RefHistComparator produces summary report every ~5 min

– Updates DB

• RefServer continuously updates histos

– Sends reference canvases to Display GUI

• Display GUI should be as light as possible

– Should be agnostic about different canvases and references

• GUI easier to maintain and always works

– All the hard work is done on the DisplayServer

OnlineServer

REF-HISTComparator

Unit

DisplayServer

histolist

GUI Display

OnlineStream

Static etc

“Database”

Summary

Ref0Server

Ref1Server

Ideal

RefNServer

Page 15: EMU Reference Histogram Comparison Unit

histolist

HistoDisplay

Current Implementation

• Given an online histogram, RefHistComp can – Find & read static corresponding reference

histogram– Send reference histogram to GUI for human

comparison

• RefHistComp does not yet– Automatically compare online with

reference– Produce summary report– Fully work with Dynamic References

EmuMonitor

Data.bin

OnlineServer

REF-HISTComparator

Unit

EmuDisplayServer

Ref.root

9091

9092

9093

Detector

Ref0Server

Ref1Server

Page 16: EMU Reference Histogram Comparison Unit
Page 17: EMU Reference Histogram Comparison Unit
Page 18: EMU Reference Histogram Comparison Unit

Conclusion

• The Ref-Hist Comparator Unit is designed to– Allow comparisons with a variety of different references

• Both manual and automatic• Both static and dynamic

– Periodically produce summary report of problems • Based on rules & tests

• Current prototype is still rather basic– Not all functionality is implemented / debugged

• E.g. Dynamic refs are prototyped, but not yet ready for release– Still iterating on final design (which may depend on CMS DQM)– Currently being tested & used in the EMU slice test

• Prototype is somewhat particular to current EMU DQM Package

• Interested to understand better how these ideas fit in with the overall CMS DQM picture