defines a collision "tape" (or better a collision file) to be
written.
WHAT(1) >= 100 : A complete dump is written (unformatted) of one or more
of the following:
- all source particles
- all particle trajectories
- all local (pointlike) energy deposition events
- all continuous energy deposition events
- user-defined events
= 0.0 : ignored
=< 0.0 : the default is reset, i.e. no dump is written
> 0.0 and < 100: not allowed! Originally used to request
another form of collision tape. Presently only
the "new" form of collision tape is possible
(the old one being incompatible with the present version of FLUKA).
WHAT(2) = number of the unformatted output unit.
Values of WHAT(2) < 21 must be avoided because of possible
conflicts with FLUKA pre-defined units.
Default: 49
WHAT(3) <= 0: source particles, trajectories, continuous and local
energy losses are all dumped
1: only source particles are dumped
2: only trajectories and continuous energy losses are
dumped
3: only local energy losses are dumped (e.g., heavy recoil
kerma, cut-off energy). Proton recoils are not included
(since recoil protons are transported by FLUKA)
4: source particles, trajectories and continuous
energy losses are dumped
5: source particles and local energy losses are
dumped
6: trajectories and all energy losses (continuous and
local) are dumped
>= 7: source particles, trajectories, continuous and local
energy losses are not dumped (but user-defined dumps
required by WHAT(4) are unaffected)
Default: source particles, trajectories, continuous and
local energy losses are all dumped, provided WHAT(1) >= 100.0
WHAT(4)>= 1: user-defined dumps after collisions are activated
= 0: ignored
< 0: resets to default (user dependent dumps after
collisions are de-activated)
WHAT(5...6) = not used
SDUM = name of the output file (max. 10 characters)
Default (option USERDUMP not given): no dump will be written.
Note: The format of the collision tape, the code number of the
events and the variables written for the different type of
events, are described in 11}.
Be careful, the amount of output can be enormous.
Example:
*...+....1....+....2....+....3....+....4....+....5....+....6....+....7...+...8
USERDUMP 200. 37.0 2.0 TRAKFILE
* It is requested to write a file TRAKFILE, containing all trajectories and
* continuous energy losses, and pre-connected to the logical output unit 37.
