Difference: VeloDataMonitor (8 vs. 9)

Revision 92006-07-19 - ArasPapadelis

Line: 1 to 1
 
META TOPICPARENT name="VELOSoftware"

The VeloDataMonitor packages

Added:
>
>
Latest update on 19 July 2006 by Aras Papadelis
 

Introduction

Line: 20 to 22
 

Installation

Added:
>
>
NB, with the release of Vetra v2r1 there is no longer any need for installing the monitoring packages on your home account, unless you want to add your own hacks to the monitoring code. If you want to run the data monitoring from Brunel you still need to follow these instructions:

For now, let's assume that we are running Vetra.

 The installation procedure is identical for the two packages. Let's install VeloClustersDataMonitor:
Changed:
<
<
  1. Go to your cmt directory
>
>
  1. Make sure that you have Vetra installed.
  2. Go to your cmt directory (probably ~/cmtuser)
  > cd ~/cmtuser
Changed:
<
<
  1. Set the LHCb environment
    > LHCbEnv (choose the latest version, or whatever version you prefer)
>
>
  1. Set the Vetra environment
    > VetraEnv (choose the latest version, or whatever version you prefer)
 
  1. Get the latest version from CVS:
    > getpack Velo/VeloClusterDataMonitor (select the head version for the latest)
  2. Compile your new package:
Line: 33 to 39
  > cmt config
> source setup.csh
> make
Changed:
<
<
  1. If everything is OK, the program should now compile without complaints. You have installed VeloClusterDataMonitor! Before you can repeat this procedure for VeloTrackDataMonitor you also need to execute this step:
    >RecEnv
>
>
  1. If everything is OK, the program should now compile without complaints. You have installed VeloClusterDataMonitor! Now repeat this procedure if you want to install VeloTrackDataMonitor.
 
Changed:
<
<

Running from Brunel

OK, now we want to run the algorithm from somewhere, for example Brunel or Vetra. I will use Brunel in this example. I assume that you have Brunel installed.
>
>

Running the monitoring...

...in Brunel

OK, now we want to run the algorithm from somewhere, for example Brunel or Vetra. If you are running Vetra you can skip this section. Here I will show how to run the monitoring from Brunel. I assume that you have Brunel installed.
 
  1. Make sure that the Brunel environment is set using BrunelEnv.
  2. Edit the Brunel requirements file:
    > cd $BRUNELROOT/cmt
Line: 46 to 52
 
  1. Add the line
    use VeloClusterDataMonitor v* Velo -no_auto_imports (add a second line with VeloTrackDataMonitor if you want to install that too)
  2. Save the file, exit the editor and type
Added:
>
>
> cmt config
  > source setup.csh (if you don't get any error messages here that means you're doing just fine)
> make
  1. Brunel will now recompile with VeloClusterDataMonitor (and VeloTrackDataMonitor if you added it in step 3)
Line: 53 to 60
  You should now be able to run VeloDataMonitor from Brunel!
Added:
>
>

...in Vetra

If you are using Vetra v2r2 or higher running the high level monitoring should be a piece of cake! The default Zero Suppressed data (ZS) options files that come with Vetra take care of most of the stuff for you. I've prepared a special page for how to run Vetra over ZS data here

Trouble shooting

One of the common errors that you may get is that Vetra / Brunel reports: ERROR  ----  Track Container retrieved but EMPTY ---

This usually means two things:

  1. No tracks can be found because the sensors have not been mapped properly. Read more about this sensor remapping here
  2. You are using the wrong pattern recognition. For simulated beam-beam collision data files you need to use the "LHCb Pattern Recognition" (PatVeloRTracking and PatVeloSpaceTracking) and for ACDC simulated and real data you most likely need to use the generic pattern recognition (PatVeloGeneric). From Vetra this can be set by choosing which of the two tracking options files that should be included: VetraTracking.opts or VetraGenericTracking.opts.
 

Using the packages

The VeloDataMonitor packages will produce a lot of histograms. If you are running with a full VELO detector, expect at least a couple of hundred of them. If you are interested in studying the data on an event by event basis the cluster information can be written to a ntuple by simply setting an option in the VeloClusterDataMonitor options file ( No ntuple output is implemented for the track information at this point but if anyone wants it I can add it easily /Aras P).
Changed:
<
<
  1. Let's start by simply running Brunel with the monitoring package and the default settings. At the end of the run, Brunel will produce a root file. Open it.
>
>
  1. Let's start by simply running Vetra with the monitoring packages and the default settings. At the end of the run, Brunel/Vetra will produce a root file. Open it.
 
  1. Open a TBrowser (with TBrowser a for example) and open the file. If everything worked properly you should see the directories VeloClusterDataMonitor and VeloTrackDataMonitor in the file. If you don't have VeloTrackDataMonitor in the file it is probably because no tracks where found in the run.

If you turn on the "Detailed" view you will see a description to each histogram. The histogram descriptions are hopefully self explanatory. Here's an example:

Line: 133 to 151
 VeloTrackDataMonitor.UserHistos Same as for VeloClusterDataMonitor.opts
VeloTrackDataMonitor.TrackLocation ="Rec/Track/Velo" Sets the location of the track container, in case you want to use a different track set for any reason.
Added:
>
>
Additionally, you need to add the following option when you are using PatVeloFilterClusters to exlude sensors from the pattern recognition (beam telescope mode):

VeloTrackDataMonitor.TestSensors ={sensor1, sensor2, ... , sensorN} (where sensorX is an integer corresponding to the sensor number that was excluded by PatVeloFilterClusters).

 

Adding your own histograms and hacking the code

If you aren't happy with the standard set of histograms it's very easy for you to add your own custom histograms or custom hacks to the monitoring source code. If we use VeloClusterDataMonitor as an example, you need to go to the src directory of Velo/VeloClusterDataMonitor and edit the files VeloClusterDataMonitor.cpp and VeloClusterDataMonitor.h.
Line: 158 to 180
 
Changed:
<
<
-- Aras Papadelis - 29 May 2006
>
>
-- Aras Papadelis - 19 July 2006
 
META FILEATTACHMENT attr="h" autoattached="1" comment="Cluster size" date="1148921229" name="clustersize.gif" path="clustersize.gif" size="6439" user="arasp" version="1.1"
META FILEATTACHMENT attr="h" autoattached="1" comment="TBrowser example" date="1148918554" name="TBrowser.jpg" path="TBrowser.jpg" size="76919" user="arasp" version="1.2"
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback