FLUKA: MGNFIELD
Previous Index Next
MGNFIELD
sets the tracking conditions for transport in magnetic fields and
also may define an homogeneous magnetic field.
See also ASSIGNMAt, STEPSIZE
WHAT(1)
= largest angle in degrees that a charged particle is
allowed to travel in a single step
Default
= 57 deg (but a maximum of 30 deg is recommended!)
WHAT(2)
= upper limit to the error of the boundary iteration in cm
(minimum accuracy accepted in determining a boundary
intersection). It also sets the minimum radius of curvature
for stepping according to WHAT(1)
Default
= 0.05 cm
WHAT(3)
= minimum step length if the step is forced to be smaller
because the angle is larger than WHAT(1)
.
Default
= 0.1 cm
WHAT(4..6)
= Bx, By, Bz components of magnetic field on the
coordinate axes (in tesla).
Default
(Bx = By = Bz = 0.0): user-supplied subroutine
MAGFLD is assumed to provide the actual values (see Notes
2 and 3 below)
SDUM
= RUNGKUTT the 4th order Runge-Kutta-Gill algorithm is
used for dis-homogeneous magnetic fields in vacuum
instead of the standard, arc-like, algorithm
Default
= no SDUM
Default
(option MGNFIELD not given): the defaults indicated for
WHAT(1-6) apply if a magnetic field exists in the current
region because of an ASSIGNMA command.
Notes:
1) If Bx = By = Bz = 0, the user-written subroutine MAGFLD is
called at each step to get the direction cosines and the
module (in tesla) of the magnetic field as a function of
region or of coordinates. A sample subroutine is provided
with the FLUKA code; instructions on how to write
user-supplied routines can be found in 13}.
2) Note that the argument list of subroutine MAGFLD is
( X, Y, Z, T, BTX, BTY, BTZ, B, NREG, IDISC )
where BTX, BTY, BTZ are the DIRECTION COSINES of the magnetic
field at point X, Y, Z, at time T (NOT the components of the
field! The field magnitude is given by B). For this reason, it
is imperative that MAGFLD returns normalised values of BTX,
BTY and BTZ such that the sum of their squares is = 1.0
IN DOUBLE PRECISION.
Three zero values are not accepted: if the field is zero
at the point in question, you must return for instance 0, 0, 1
and B = 0. On the contrary, note that Bx, By, Bz in the
MGNFIELD option, given by WHAT(4)
...WHAT(6)
as described
above, are the field components and not the cosines.
3) Magnetic field tracking is performed only in regions defined
as magnetic field regions by command ASSIGNMAt. It is
strongly recommended to define as such only regions where a
magnetic field effectively exists, due to the less efficient
and accurate tracking algorithm used in magnetic fields.
To define a region as having a magnetic field and to return
systematically B = 0 in that region via subroutine MAGFLD, is
not allowed.
4) The maximum error on the boundary iteration, WHAT(2)
, must be
compatible with the minimum linear dimension of any region.
5) It is recommended to activate also option STEPSIZE inside and
close to regions where a magnetic field is present. That option
can be used to set a minimum and a maximum step size (in cm)
for every region.
6) In case of conflict, WHAT(3)
overrides the step size requested
by option STEPSIZE. Therefore, it is suggested to set it not
larger than the latter. The purpose of this constraint is to
avoid tracking in detail low-energy particles along a helix of
very small radius, by forcing several tours into a single step
(all the energy will be deposited at the same point).
Example (number based):
ASSIGNMAT 2.0 15.0 30.0 5.0 1.0 0.0
MGNFIELD 20.0 0.2 0.10 0.0 0.0 0.0
STEPSIZE -0.05 0.0 20.0 25.0 0.0 0.0
STEPSIZE 0.3 0.0 15.0 0.0 0.0 0.0
The same example, name based:
ASSIGNMAT VACUUM Reg15th Reg30th 5.0 1.0 0.0
MGNFIELD 20.0 0.2 0.10 0.0 0.0 0.0
STEPSIZE -0.05 0.0 Reg20th Reg25th 0.0 0.0
STEPSIZE 0.3 0.0 Reg15th 0.0 0.0 0.0
Previous Index Next
