Defines some I/O parameters relevant to the heavy ion event generator DPMJET
Option DPMJET is useful only for development work: generally the user does
not need this option - to request activation of DPMJET use the command
EVENTYPE
See also BME, EVENTYPE, MYRQMD, PHYSICS, RQMD
WHAT(1) : format of the required pre-processed Glauber parameters.
A complete set of projectile-target combinations for the entire
FLUKA energy range is utilised. To revert to the original DPMJET
format set this value to 1. See also Note 2 below.
Default = 0.0
WHAT(2) : allows to change the logical unit number which is assigned to the
DPMJET output.
Default = 19.0
WHAT(3) : selects the level of output verbosity for DPMJET. The default
corresponds to minimal output. If this value is set to 1.0,
initialisation and minor error messages are printed. In addition,
one can request information about the DPMJET common block (the
internal list of objects considered by DPMJET). If set equal to
2.0 all the available information is output, if set equal to 3.0
only information about final residual nuclei is output, and if
set to 4.0 information about all final state objects is written.
Default = 0.0
WHAT(4)-WHAT(6) : not used
SDUM : not used
Default (option DPMJET not given): all the above defaults apply
Notes:
1) FLUKA utilises DPMJET and a heavily modified version of a
RQMD-2.4 implementation (H. Sorge [Sor89, Sor89a, Sor95]) in order
to simulate heavy ion interactions.
2) Glauber parameter sets in the original ASCII format can be generated
by running the stand-alone DPMJET program. Only up to 10 different
projectile/target combinations can be initialised per run. Parameter
sets in excess of the first 10 combinations will be provided by the
default mechanism.
Examples:
*...+....1....+....2....+....3....+....4....+....5....+....6....+....7...
DPMJET 0.0 71. 4.
* running with the pre-processed, full matrix of Glauber parameter sets
* but requesting more verbose output for DPMJET: initialisation related
* messages, all error messages and information about final state objects
* in the DPMJET common block.
* DPMJET is told not to read any specific input options.
* All output will be found in file connected to logical unit 71 instead
* of 19 (under Linux this file would be named fort.71)
*
