1. Tracker Visualization Tool: integration in ORCA Maria S. Mennea, Giuseppe Zito University & INFN Bari, Italy Tracker b-tau Cosmic Challenge preparation (Tracker week, June 2005)

2. Introduction Classically monitoring is based on a histogram presenter that would show a set of histograms and tables updated regularly. The CMS tracker has more than 50 millions channels organized in 16540 modules each one being a complete detector. Its monitoring requires many thousands of histograms to be computed every few minutes. It could be useful to people in charge for monitoring to have also a representation that shows all modules at once in a single computer screen with single modules information coded in some way. This representation should be useful as a special tracker event display for the cosmic challenge and tests that are now done for integration and commissioning

3. This "tracker map" is obtained disassembling the whole tracker and assembling it again on a flat surface putting the single modules in positions which are connected to their spatial position. The tracker map How to build a detector map!

4. Advantages of a tracker map 1. Data from each one of the data sources can be represented on the map. For example the single module can be shown in a colour code:  number of dead channels from construction database  total number of rechits hitting the module in the last 100 events readout  result of a comparison between the last histogram and a control histogram 2. Holes or hot spots in the map can pinpoint detector problems 3. May be used to request more data by using an interactive interface (possibility to zoom)

5. Current status  Tool now available in IGUANACMS demonstrative use offline global view of data on POOL  Now we have a “Tracker Map” implemented in SVG format which runs in Orca without need to load special graphics software  Next step: online use of the Tool attempt to use it in the general monitoring framework (C. Leonidopoulos) idea: data producer in ORCA (Sources), fill 2D histogram (x= Layer Id ; y= Module Id) with a monitoring information, send it to the client which fills the SVG file with the information and visualize it

6. To build the tracker map the user will import only two classes and a txt file which is the javascript interface for the SVG image TrackerMap class, TmModule class, trackermap.txt file How to use the tool (like an histogram) … TrackerMap *tkMap = new TrackerMap(); … //loop on events //loop on DetUnit tkMap->fill( (*idet), value ); … tkMap->print( flag ); … fill the TrackerMap save on disk in SVG format allocation of map In user analysis file

7. Svgmap.svg (image) Integrated signal from 50 events

8. Svgmap.svg (source file) <!DOCTYPE svg PUBLIC “-//W3C//DTD SVG 1.1//EN“ "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <![CDATA[ … ]]>...... … Javascript user Interface is loaded from trackermap.txt Incremented by fill(); Number identifying module (layer*100000+ring*1000+module) 1….41 normally start from 1 except for TEC for stereo module > 100 Polygons created by tool ( print(); ) 16540 lines, one for each module

9. Image reference frame y x xsize 2*ysize Each layer has a different reference frame defined by xmin xmax, ymin, ymax x y xmax xmin ymin ymax  0360°

10. Future improvements  The tracker map can display in colour only a single information but you can store many information for each module in the value field. These informations will be shown after the user selects the module with the mouse  Connect to each module an image accessible via url (for example an histogram) and show the image when the mouse is over  Customization for cosmic challenge (only 500 modules and around 5 layers)  Possibility to fill complete layer or ring with same value  Possibility to define different colour gradients or colour palettes.

11. Summary  Simplified version of tracker map now available in IGUANACMS is now implemented in Orca without need to load special graphics software  It should be useful as a special tracker event display for the cosmic challenge and tests that are now done for integration and commissioning  The code is represented by 2 classes and around 500 lines total size. The tracker map is seen by the user as a normal histogram to be filled with some quantity defined for each module. When you save the tracker map, an SVG file (a normal text file created with cout) is saved on disc.  You can look at SVG file with a browser with a Adobe plugin installed. The image saved includes a minimum graphics interface with zoom and possibility to pick each module getting information about module position inside tracker and value of quantity represented for the module.  Plan to propose this tool to the software group for the possible integration in the common monitoring framework.