Tracker Iguanabased

1

• Tracker Iguana-based
• monitoring and visualization

M.S. Mennea A. Regano G. Zito University
INFN Bari - Italy
Tracker/btau Workshop CERN - 26 October 2004
2
Our goal (1)
We would like to have at the beginning of CMS
data taking

• Iguanacms running in the control room as a
  general purpose event display
• to look at the last event read and cross-check
• tracker data with other detectors data

• accumulate events option in Iguanacms
• to make a fast check for hot spots or holes

1
3
Our goal (2)

• Specialized representation of tracker (tracker
  map)
• should run all time on computer screens and be
  constantly updated
• to allow a fast overall check and an
  additional cross-check of
• normal automatic monitoring
  procedures that send alarms in
• case of problems
• to summarize the information of the thousands
  of histograms
• needed to monitor the tracker and
  make more easy the
• access to these
• should run both in the control room in Iguanacms
  and on Internet by using a light client (Java
  program/web browser)
• to allow to reach the experts everywhere and
  have feedback
• on the control room situation in a
  reasonable time (few minutes)

2
4
Our goal (3)

• To make more easy the task of providing the data
  for Iguanacms and tracker map it would be
  advisable but not necessary to define a unique
  and standard interface to all information needed
  for tracker monitoring
• Construction database
• DDD
• Conditions database
• Event
• Histograms

By unique we intend that you dont have learn a
new API for each item, by standard we intend web
services protocol
3
5
Going to the level of the single channel
The tracker map can be thought as a scatter plot
with an entry for each module. It can be zoomed
in order to see single channels. At this level we
can introduce many different representations of
information, for example Drawing fired
strips Writing the value of the information
represented A popup menu should allow the
user to tailor the representation to his needs.
At the module level it should be possible also to
look directly at normal histograms using this map
only as a convenient way to access the relevant
histograms (clicking on module and get all
modules histograms)
4
6
Possible uses of Tracker map

• Display event in tracker
• Display last few events accumulated
• Display temperatures, voltages and
• other data from conditions database
• Display dead strips and other data
• from construction database
• Display result of global check of tracker by
  comparing last module histogram with reference
  histogram

5
7
What we have now in Iguanacms (1)

• Iguanacms is a generic display for CMS
  data.

Iguanacms_1_10_0
We have added a CustomTracker part with three
main features that can be useful for tracker
monitoring
6
8
What we have now in Iguanacms (2)

• 1. Numbering of each tracker module, clicking on
  it you can known its position.

Example
Module 115 of ring 12 in TIB 1
2. Easy way to select each detector part down to
the module level. Stereo pair modules can be
selected separately.
7
9
What we have now in Iguanacms (3)

• 3. A first implementation of the tracker map.
  This map represents all 17000 tracker modules
  with the following schema

1
2
1
2
1
3
2
3
4
5
6
7
8
9
z
2
3
4
2
4
6
PXB
1
TIB
TOB
3
2
1
1
3
5
PXE
-z
TEC
TID
1
2
1
1
2
3
2
3
4
5
6
7
8
9
This map cannot be zoomed, but you can go to the
level of the single channel (selecting a single
layer)
8
10
What we have now in Iguanacms (4)

• Iguanacms runs on lxplus but it is too slow
  there. You have to install it on your desktop
  with a suitable graphics card. This is now
  relatively easy using XCMSI.
• We didnt introduce any change from the previous
  version. Our main task now is to support this
  CustomTracker part through new releses of
  Iguana/Iguanacms.

A first use of CustomTracker has been to check
the tracker description in DDD.
9
11
Light visualization implementation (1)
Built a prototype (Java program named Tmon) that
implements the same tracker map that we have in
Iguanacms.
The tests were done with data taken from
construction database and from Montecarlo events
dataset.
10
12
Light visualization implementation (2)
This prototype has been tested by using web
services implemented with Tomcat Axis Castor.

System Architecture
11
13
Light visualization implementation (4)
Result encouraging
We can read and display the data in the tracker
in around 10 seconds. The same time is needed to
load xml tracker description. We dont use
directly the DDD this is too complex for our
purposes and still incomplete. We use a simpler
tracker description with the data extracted from
DDD and saved in a single xml file
Examples of response time with events of
different size
In the future we would like to check also if it
is possible to replace this Java client with a
web browser with the Adobe SVG plugin. Instead
of sending the event we send directly the tracker
map in SVG. The code of java is available on line
for tests but is REALLY a prototype.
12
14
Summary

• Tracker map and other features that can be useful
  in monitoring are already available in
  CustomTracker part of Iguanacms. Try them and let
  us know what you think. We will support them and
  (slowly) modify them following your suggestions.
  
• Prototype of light visualization client developed
  to test access of monitoring data from Internet
• What we are trying to do is a kind of high level
  monitoring that will require all the low level
  monitoring working to be of use. For this reason
  it is not urgent but it must be working in the
  control room by start of data taking. It could
  be made a lot easier if we develop a standard
  interface (of web service type or other) to all
  data and services necessary for monitoring

More detail in our web site www.ba.infn.it/men
nea/cms
13