Main Page Namespace List Class Hierarchy Compound List File List Namespace Members Compound Members

analysis_utilities Documentation

analysis_utilities: a D0 software package

Version v00-01-04

The analysis_utilities CVS package contains several utilities for performing data analysis using DST or TMB as input. These utilities are considered to be of general use for the entire collaboration and are therefore kept in a public package.

All the utilities are available from the D0analysis namespace, the corresponding library code is contained inside the libanalysis_utilities.a library.

Framework packages

The following framework packages are available inside the analysis_utilities cvs package:

RegD0TriggerFilter : perform either event filtering or event tagging based on the names of the L3 triggers which have fired in the event (the two options cannot be used simultaneously)

To perform event filtering (skip the rest of the processing for the current event, if it passes a list of triggers):

To use this filter add to the string Packages = "................ " line of the main framework RCP file a trigsel entry right after the RCP controlling the input of data and eventually the unpacking of the TMB.

Also add the following line :

RCP trigsel = <analysis_utilities D0TriggerFilter>

For each event the trigger information is then decoded (using as input either the L3Chunk if it is available [DST,TMB in the future], or from the TMBTriggerChunk [current version of the TMB]) and if one of the triggers fired in the event matches one of the triggers requested by the user, then the processing of that event continues with the packages which follow trigsel in the string Packages = "................ " line of the main framework RCP file. Otherwise the processing continues with the following event.

The user can control the list of triggers which are used for selectively processing the events in two ways:

storing the list of triggers in the analysis_utilities/rcp/D0TriggerSelector.rcp file (the name of this file can be changed by editing the name of the file corresponding in the D0TriggerFilter.rcp file above). For example the following line:

string Triggers = ( "EM_HI" "EM_HI_2CEM5" )

tells the D0TriggerFilter package to select events which pass either the "EM_HI" or the "EM_HI_2CEM5" triggers. An empty list, given by either:

string Triggers = ( )

or by

string Triggers = ( "*" )

means that all the events will pass the trigger selection (this is the current default)

passing the list of triggers through the command line, using the -filter_triggers option. For example to process through D0reco either the "EM_HI" or the "EM_HI_2CEM5" triggers the user would have to give the following command (this option is available only for versions of D0reco greater than p12.02.00 and t02.30.00): only the events passing

D0reco_x -filter_triggers EM_HI EM_HI_2CEM5 ..................

This option is also available from the D0tools script: in this case the user should type

runchunkanalyze -filter_triggers= EM_HI,EM_HI_2CEM5

(a comma separated list of triggers)

To perform event tagging (skip the rest of the processing for the current event, if it passes a list of triggers, this options has been added in t02.35.00 and p13.00.00):

You need to edit the RCP file analysis_utilities/rcp/D0TriggerFilter.rcp and change the two lines:

bool filter = true
bool tagevent = false

bool filter = false
bool tagevent = true

and eventually change the name of the EDM event tag in the line

string event_tag_name = "trigger-select"

To use this event tagging functionality add to the string Packages = "................ " line of the main framework RCP file a trigsel entry right after the RCP controlling the input of data and eventually the unpacking of the TMB.
Also add the following line :

RCP trigsel = <analysis_utilities D0TriggerFilter>

For each event the trigger information is then decoded (using as input either the L3Chunk if it is available [DST,TMB in the future], or from the TMBTriggerChunk [current version of the TMB]) and if one of the triggers fired in the event matches one of the triggers requested by the user, then the event is tagged.
The user can control the list of triggers which are used for event tagging in two ways:

storing the list of triggers in the analysis_utilities/rcp/D0TriggerSelector.rcp file (the name of this file can be changed by editing the name of the file corresponding in the D0TriggerFilter.rcp file above). For example the following line:

string Triggers = ( "EM_HI" "EM_HI_2CEM5" )

tells the D0TriggerFilter package to tag events which pass either the "EM_HI" or the "EM_HI_2CEM5" triggers. An empty list, given by either:

string Triggers = ( )

or by

string Triggers = ( "*" )

means that all the events will pass the trigger selection and be tagged (this is the current default)

passing the list of triggers through the command line, using the -tag_triggers option. For example to process through D0reco either the "EM_HI" or the "EM_HI_2CEM5" triggers the user would have to give the following command (this option is available only for versions of D0reco greater than p12.02.00 and t02.30.00): only the events passing

D0reco_x -tag_triggers EM_HI EM_HI_2CEM5 ..................

This option is also available from the D0tools script: in this case the user should type

runchunkanalyze -filter_triggers= EM_HI,EM_HI_2CEM5

(a comma separated list of triggers)

The main limitation of this package is that it does not yet allow to select events which have Mark and Pass triggers (which are not available - currently - in the thumbnail). This limitation will be removed in a future version of the code.

................................

Classes

The description below includes links to the code contained in this package.

The physical components include:

D0TriggerFilter (Doxygen documentation, header, source, RCP file)
D0TriggerSelector (Doxygen documentation, header, source, RCP file)

If you have comments on this documentation E-mail: mverzocc@fnal.gov

Generated at Thu Oct 3 11:50:14 2002 for analysis_utilities by