Difference: VeloDataMonitor (9 vs. 10)

Revision 102006-07-21 - ArasPapadelis

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

The VeloDataMonitor packages

Line: 141 to 141
 VeloClusterDataMonitor.OutputNtuple Turns on/off the output of a ntuple
VeloClusterDataMonitor.OccupancyHistos Turns on/off the average clusters occupancy histos (one histogram per sensor)
VeloClusterDataMonitor.MultiplicityHistos Turns on/off the average cluster multiplicity histos (one histogram per sensor)
Deleted:
<
<
VeloClusterDataMonitor.UserHistos Turns on/off any histograms added by the user to to the userHistos() area in the VeloClusterDataMonitor.cpp source code
  In VeloTrackDataMonitor.opts you can change the following

VeloTrackDataMonitor.EventDisplay Turns on/off the 3D "event display" histos and the XY hitmap histos.
VeloTrackDataMonitor.SelectedEvent 1= Selects which event will be plotted in the "selected" 3D event display histogram.
VeloTrackDataMonitor.ExtrapResidHistos Turns on/off a lot of histograms dealing with residuals between track sensor intercept points and clusters locations.

Deleted:
<
<
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.

Additionally, you need to add the following option when you are using PatVeloFilterClusters to exlude sensors from the pattern recognition (beam telescope mode):

Line: 156 to 154
 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

Changed:
<
<
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.
>
>
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 will find the source code in the src directory of Velo/VeloClusterDataMonitor.
  The VeloClusterDataMonitor class is derived from the GaudiTupleAlg class, which provides an interface for creating histograms and ntuples. Here's how to fill a histogram:
Line: 171 to 169
  The histogram name can be an int or a std::string while the histogram title should be a std::string that describes the contents of the histogram in a sentence. There are plenty of examples of how this is done in the source files.
Changed:
<
<
It might be a good idea to separate your own histograms from the rest of the code. In that way it will be much easier for you to migrate to new version of the package. A method called userHistos() is available for this purpose. There is an option called UserHistos (see section above on options) with which you can choose if this method should be called or not.
>
>
It might be a good idea to separate your own histograms from the rest of the code. In that way it will be much easier for you to migrate to new version of the package. Depending on which version of the monitoring packages you use, there are different ways of doing this:

  • VeloClusterDataMonitor and VeloTrackDataMonitor v1r4 or higher: In the src directory you will find files for the class called Cluster(Track)DataMoniUserHistos. This class is derived from VeloCluster(Track)DataMonitor and has knowledge about the track and cluster containers. Add your own hacks to this class and don't forget to add the algorithm to the run sequence. Here is an example from Vetra where you can see how the algorithm TrackDataMoniUserHistos has been added to the run sequence:

ApplicationMgr.DLLs += { "VeloTrackDataMonitor"  };
ClusterAndTrackMoni.Members += { "VeloTrackDataMonitor" 
                                ,"TrackDataMoniUserHistos"
};
 
Deleted:
<
<
Don't forget to set UserHistos = true if you have added histogram code in the userHistos() method
 

Useful to know

To plot information about the clusters and tracks you need to familiarise yourself with classes like DeVelo, DeVeloSensor, VeloCluster, Track and VeloChannelID. Here's some documentation from the CVS repository and the Doxygen pages ( warning, this link may be pointing to an old version of LHCb).
 
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