1. И ЯN R ИI HADES Collaboration Meeting XIX July 1-5 2008 at GSI in Darmstadt Progress in offline and online QA Offline-QA New dev-s in hhistory Online-QA Omon tries Go4-future A.Sadovsky, T.Solovieva INR RAS (Troitsk)

2. hhistory: Loading QA-files, selecting histogram and looking at it manual quality buttons histo/file viewer control

3. Mean value for the distribution in selected window

4. Monitoring for the shape change of a distribution

5. Distribution of the histogram contents (possibly normalized to another histogramm) user defined interval min/max global/local list and possibility select normalization histogram

6. More information Documentation Download Feedback http://hades-wiki.gsi.de/cgi-bin/viewauth/SimAna/hhistory http://forum.gsi.de/index.php?t=getfile&id=4299&rid=317&S=d1a81a416e0307c35b011639a84e4b40

7. The task was to develop a simple client for online monitoring with following functionality: It should periodically interact with a data processing server and get histograms to show them on via GUI to the user. It should allow data reset on client side without modification on the server side. Parameters should be read from an ASCII configuration file created by the user (histogram names and number of canvas where to draw). Development of new online monitoring client

8. Client-Server prototype The idea of a Client-Server application with ‘spying’ functionality was taken from ROOT example located in $ROOTSYS/tutorials/net/spyserv.C $ROOTSYS/tutorials/net/spy.C Server: processes data, stores histograms, sends a current version of them to the client on request. Client: sends request and draws current histograms.

9. Implementation The resulting GUI application is a *.C macro that can be run via root or after precompile via root. It consists of 1 main and 3 help classes. –Spy (core class) –HistoCoord ( to store histogram coordinates) –HistoPanel ( windows to draw histograms) –PanelInfo ( to store parameters for each panel)

10. Data flow and functions

11. MAIN WINDOW PANELS Online monitoring application prototype realization

12. Functionality Interaction with server: The main advantage of this application is universality, because the whole GUI structure can be designed in the configuration file. The user enters panels, tabs, histogram definitions, species if the histograms should be shown and on which canvas. Data processing: Main window contains functional buttons for connection, timer control, exit and panel buttons. Each panel button opens a new window with defined tabs and canvases. All panels can be closed and opened again.

13. Functionality Interaction with server: The core interacts with the server. It sends every N-seconds a request. It is done with help of ROOT TTimer class. The delay time can be set via input field located in the main window. Data processing: The core gets a TList from the server with current version of histograms. After this it reads all histograms in it and sends them to a definite panel. The panel gets the histogram and draws it on defined tab in defined canvas. One histogram can be drawn multiple times on different panels.

14. Functionality Data reset: One can see only the latest changes in all histograms by making a reset point via ‘Reset’ button. Then the core gets a TList from server with current status histograms and stores it. The next time data comes from server updated histograms will be shown counted this way: Result_histo = Current_histo – Reset_histo

15. Results A realization of GUI client application Omon (Online monitor) was developed It is universal: the whole interface, names can be set in a config-file It is easy to use It has the main functionality and something more but is still simple enough The server side was NOT modified