CDF event simulation
The CDF event simulation consists of two programs, cdf2sim and
ProductionExe. The former interfaces to Pythia/Isajet/Herwig/etc., is
responsible for filling the generator 4 vector information in the CDF
data structure, and interfaces to GEANT and is responsible for filling detector raw data information in the CDF data structure. Thus running cdf2sim gives you MC truth information and raw detector hit information. The latter reads in
the root file produced by cdf2sim containing this event structure, and runs
reconstruction (track finding, cluster finding, jet finding, missing energy
calculations, level 3 trigger calculations etc.). After filling the appropriate
CDF banks, the data is written out, again in the form of a root file.
To run cdf2sim
To run cdf2sim you need a .tcl file of directives. These are:
- Instructions defining the generator that will be used (eg. module talk Pythia )
- Directives to the generator to define the type of events that will be
generated, any kinematic cuts etc.
- Directives to GEANT defining which CDF data banks you will fill (this is a standard list and does not need to be touched)
- Directives specifying the name and location of the output root file.
An example .tcl file can be found in /scsi10/cdf/anyes/tcl/tt_Pythia.tcl. As the name implies it generates ttbar events, using Pythia as a generator.
Copy this to an area on your own directory and make any modifications for
different processes/ different output file names that you want.
To run cdf2sim with a given .tcl file; type
cdf2sim my_tcl_file
To run ProductionExe
To run ProductionExe you need a .tcl file of directives. These are:
- Directives specifying the name and location of input (root) files, as produced by cdf2sim
- Configuration of jet reconstruction algorithms
- Configuration of reconstruction path (ie. all modules that will be accessed in reconstruction need to be specified here. This seems to be a standard list)
- Directives specifying the name and location of output (root) files
- Some configuration for monitoring histograms. I doubt this is really needed, but I have not taken it out.
An example .tcl file can be found in
/scsi10/cdf/anyes/tcl/tt_Prod.tcl . As the name implies it
generates reconstructed (dst) ttbar events, using the cdf2sim ttbar events as
input.
Copy this to an area on your own directory and make any mod
ifications for
different processes/ different output file names that you want.
To run ProductionExe with a given .tcl file; type
ProductionExe my_tcl_file
Useful Links