New Page 1

Running Tracker Monitoring Software in Source-Collector-Client Environment

we need to set up the work space under COSINE to be able to have this environment. The stable version of COSINE to use is COSINE_2_0_3_pre1 which is compatible with ORCA_8_13_0, COBRA_8_5_2

Create Working area

  scramv1 project COSINE COSINE_2_0_3_pre1

Checkout TrackerMonitoring package from ORCA

      cd COSINE_2_1_0_pre3/src
      project ORCA
      cvs co TrackerMonitoring

Compile the Source and tracker specific Client programs which in turn will create all the required libraries.

For Pixel system the Source program is PixelMonitorSource.cpp and is in the TrackerMonitoring/SiPixelFramework/test area

        cd TrackerMonitoring/SiPixelMonFramework/test
        eval `scramv1 runtime -csh`
        scramv1 b

For Silicon Strip system the Source program is MonitorSource.cpp and is in TrackerMonitoring/SiStripFramework/test area

         cd TrackerMonitoring/SiStripMonFramework/test
         eval `scramv1 runtime -csh`
         scramv1 b

Source

One can specify a part of the Strip Tracker structure 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 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

Start the monitoring environment where you need (at the moment) to start first the Collector, HistoServer should already be available from SubfarmManager/PhysicsMonitor/test once "scramv1 runtime " is setup. After that start the Source
- Pixel System go to TrackerMonitoring/SiPixelFramework/test area and start
```
         PixelMonitorSource -c .orcarc [otherwise .orcarc is note loaded :( new feature??]
      
```
- Strip System go to TrackerMonitoringSiStripMonFramework/test area and start
```
   
         MonitorSource -c .orcarc [otherwise .orcarc is note loaded :( new feature??]
      
```
Once the Source(either for Pixel or from Strip) is started one can start the Client. The general purpose ClientsClients are provided by the CMS-DQM group (Web Monitor and IGUANA-CMS client). One can also try the Tracker specific Client (very preliminary and development version) SiStripMonFramework/test/TrackerClient1.cpp (for the Strip system). The digi histograms will be visible in popped up canvas.