New Page 1

The Monitoring Elements (MEs) for the Silicon Strip Tracker can be subdivided according to the tasks at different levels (commissioning, zero-suppression, digi, reconstructed hits, tracking....) and also according to the geometrical structure of the tracker (tracker as a whole, TIB-TOB-TEC-TID, layers, discs, rod, string, detector modules). The Tracker Monitoring Software creates and fills these MEs in the "TrackerMonitoring" package inside ORCA. The package contains following sub-packages

SiStripMonFramework : contains the container class Histogrammer which holds the list of MEs for Tracker, Layer, Rod/String and Module. Each of these contains the list of ME for with different tasks at that geomtrical level
SiStripMonTracking : defines the MEs related to Tracking (work on going)
SiStripMonRecHit : defines MEs for Reconstructed Hit and Digi
SiStripMonZeroSuppression : the MEs for Pedestal and Noise (for Raw data runs) are defined here
SiStripMonCommissioning : defines commissioning MEs
SiPixelMonFramework : defines the MEs for the Pixel tracker and fills them

These MEs ar booked using the interface provided in via the DaqPrototype interface to ROOT in COBRA

The package depends heavily to Tracker/SiStripConnectivity for the geometrical structure and the connection informations. The MEs are arranged in folders following the geometrical structure of the Tracker. In each level of structure there is a Header with useful information as string. In case of detector module the Header contains the full connection info like Fec #, Ring#, CCU #.....Fed# and x-y-z position, DetUnit # etc.

The Source and Client: In TrackerMonitoring/SiStripFrameWork/test, an example code to be used as "Source" (MonitorSource.cpp) is provided. It works inside ORCA with simulated events in COBRA driven loop.

Users are strongly requested to use the general purpose "Clients" provided by the CMS-DQM group (Web Monitor and IGUANA-CMS client). There are three example clients provided in the same area for tracker specific tasks

TrackerClient1.cpp a very simple client which can be used to view Digi histograms in a popped-up root canvas
TrackerClient2.cpp can be used to book and plot a summary ME (histogram) from a number of MEs booked and filled in the source
TrackerClient3.cpp demonstrates the collation of same MEs coming from different sources (multi source case)

The Parameters : needed for running are defined in the .orcarc file in TrackerMonitoring/SiStripMonFramework/test area.

One can specify a part of the Tracker structure (for Silicon Strip) where the monitoring histograms will be booked. This is done using TrackerMonitoring:TrackerStructureCreation and TrackerMonitoring:TrackerSubStructureCreation simple configurables
- to create the only layer #1 of TIB one should use
```
            TrackerMonitoring:TrackerStructureCreation = TIDF
            TrackerMonitoring:TrackerSubStructureCreation = Disc_1
          
```
- to create the whole Tracker structure only layer #1
```
            TrackerMonitoring:TrackerStructureCreation = ALL
            TrackerMonitoring:TrackerSubStructureCreation = ALL
          
```

One can switch ON/OFF a certain type of histogram booking (in Silicon Strip) setting true/false values (respectively) to the following simple configurables

            TrackerMonitoring:DigiHistograms = true 
            TrackerMonitoring:RecHitHistograms = true 
            TrackerMonitoring:CommissioningHistograms = false  
            TrackerMonitoring:TrackingHistograms = false                        
            TrackerMonitoring:ZeroSuppressionHistograms = false

Following simple configurable parameters define Address, Port # of the machine where the collector will run needed by the source , Update delays .. etc in the DQM framework

            Monitoring:AutoInstantiate = 1 
            MonitorServer:Address=localhost 
            MonitorServer:Port=9090 
            MonitorUpdateDelay=5000                        
            FilterUnitName=FU0

Running Source-Client : to start the monitoring, (at the moment) you need (at the moment) to start first the Collector

          HistoServer

which should already be available from SubfarmManager/PhysicsMonitor/test once "scramv1 runtime " is setup. After that start the Source

       MonitorSource -c .orcarc

and then start the Client (TrackerClient1 for example). You should be able to see digi histograms in a popped up canvas.

Running Multiple Sources : Start the Collector in a machine and use the corresponding name in the .orcarc parameter MonitorServer:Address instead of "localhost". Now the source can be started with this .orcarc and for the next (an so on) source(s) you should just change FilterUnitName in the .orcarc file. Once all the sources are started you can start the Client (TrackerClient3)