ASCII input file

ASCII format

This format is supposed to be used in case if an external event generator provides a list of reaction products with particle ID, momentum and start position (vertex).

Preparing an input file

The input file is described event-wise with one line of a header, followed by lines describing the content, one entry per primary particle. The structure is as following:

eventNumber  multiplicity  0.  0.
flag  Z  A  px  py  pz  vx  vy  vz  mass

• eventNumber - index of an event, usually starts at 0
• multiplicity - number of primary particles, which should match number of lines describing those particles
• "0. 0." - not used, but has to be in the header
• flag - 1 if an elementary particle (described with PDG code) or -1 - if a fragment
• Z - 0 if an elementary particle or charge in case of fragment
• A - PDG code for a particle or A for a fragment
• px py pz - total momentum (LAB) in GeV/c
• vx vy vz - start position (vertex) in cm
• mass - mass of a particle in GeV/c2

Example

Below is an example of an event with 1 fragment and 4 neutrons:

0     5   0.   0.
 -1   50      128     -0.0024691    0.0197320  155.5612335    0.00  0.00  0.00   127.910537
  1    0     2112      0.0023880   -0.0037039    1.2324538    0.00  0.00  0.00   0.939565379
  1    0     2112      0.0074641    0.0036909    1.2642491    0.00  0.000  0.00   0.939565379
  1    0     2112     -0.0062601   -0.0140930    1.2316210    0.00  0.00  0.00   0.939565379
  1    0     2112     -0.0011230   -0.0056258    1.2183754    0.00  0.00  0.00   0.939565379

Usage

Files are to be placed in R3BRoot/input directory. To use in simulation, in the file r3bsim.C line 40:

TString fGene = "ascii";

and line 113:

OutFile, ParFile, "Name_Of_the_Input_File", 335566);

The filename should be relative to R3BRoot/input directory.