Code indexing in gitaly is broken and leads to code not being visible to the user. We work on the issue with highest priority.

Skip to content
Snippets Groups Projects
Commit da33e75e authored by ext-calvo_p's avatar ext-calvo_p
Browse files

Merge branch '42-documentation-for-geometry-acting-as-particle-termination' into 'master'

Resolve "Documentation for Geometry acting as particle termination"

Closes #42

See merge request OPAL/documentation/manual!61
parents 9df98f6b f1aa60e0
No related branches found
No related tags found
No related merge requests found
...@@ -216,8 +216,8 @@ ENABLEHDF5:: ...@@ -216,8 +216,8 @@ ENABLEHDF5::
If true (default), HDF5 read and write is enabled. If true (default), HDF5 read and write is enabled.
ASCIIDUMP:: ASCIIDUMP::
If true, instead of HDF5, ASCII output is generated for the following If true, instead of HDF5, ASCII output is generated for the following
elements: Probe, Collimator, Monitor, Stripper and global elements: Probe, Collimator, Monitor, Stripper, Geometry,
losses. Beam stripping losses and global losses.
BOUNDPDESTROYFQ:: BOUNDPDESTROYFQ::
The frequency to do `boundp_destroy` to delete lost particles. Default The frequency to do `boundp_destroy` to delete lost particles. Default
10 10
......
...@@ -1464,6 +1464,11 @@ BSCALE: ...@@ -1464,6 +1464,11 @@ BSCALE:
Scale factor for the magnetic field map. Scale factor for the magnetic field map.
SYMMETRY:: SYMMETRY::
Defines symmetrical fold number of the B field map data. Defines symmetrical fold number of the B field map data.
GEOMETRY::
Defines the boundary geometry in order to use it for
particle termination (see Chapter link:geometry#chp.geometry[Geometry]).
The particles hitting on the `GEOMETRY` will be deleted, and they are recorded in the
HDF5 file _<GEOM>.h5_ (or ASCII if link:control#sec.control.option[`ASCIIDUMP`] is true).
FMLOWE:: FMLOWE::
Minimal energy [GeV] the fieldmap can accept. Used in `GAUSSMATCHED` distribution. Minimal energy [GeV] the fieldmap can accept. Used in `GAUSSMATCHED` distribution.
FMHIGHE:: FMHIGHE::
......
...@@ -13,9 +13,10 @@ endif::[] ...@@ -13,9 +13,10 @@ endif::[]
== Geometry == Geometry
At present the `GEOMETRY` command is still an *experimental feature* At present the `GEOMETRY` command is still an *experimental feature*
which is not to be used by the general user. It can only be used to which is not to be used by the general user. It can be used to act as
specify boundaries for the `SAAMG` Solver. The command can be used in two a terminator for particles that cross the geometry surface and to specify
modes: boundaries conditions for the `SAAMG` field solver. The command can be
used in two modes:
1. specify a H5hut file holding the surface mesh of a complicated 1. specify a H5hut file holding the surface mesh of a complicated
boundary geometry boundary geometry
...@@ -68,5 +69,11 @@ Name: GEOMETRY, TOPO=ELLIPTIC, LENGTH=1.0, A=0.005, B=0.005; ...@@ -68,5 +69,11 @@ Name: GEOMETRY, TOPO=ELLIPTIC, LENGTH=1.0, A=0.005, B=0.005;
---- ----
The geometry element must later be passed to the link:fieldsolvers#sec.fieldsolvers.fieldsolvercmd[fieldsolver command]. The geometry element must later be passed to the link:fieldsolvers#sec.fieldsolvers.fieldsolvercmd[fieldsolver command].
If only particle termination is desired, any solver can be used and
it is not necessary to specify the geometry in the field solver command.
In the link:track#sec.track.particles[`RUN` command] the boundary geometry has
always to be specified in order to load it and use it for particle termination.
// EOF // EOF
\ No newline at end of file
...@@ -186,18 +186,18 @@ METHOD:: ...@@ -186,18 +186,18 @@ METHOD::
be used. For the time being the following methods are known: be used. For the time being the following methods are known:
+ +
* `PARALLEL-T` * `PARALLEL-T`
This method puts _OPAL_ in _OPAL-t_ mode see Chapter link:opalt#chp.opalt[_OPAL-t_]. This method puts _OPAL_ in _OPAL-t_ mode (see Chapter link:opalt#chp.opalt[_OPAL-t_]).
* `CYCLOTRON-T` * `CYCLOTRON-T`
This method puts _OPAL_ in _OPAL-cycl_ mode see Chapter link:opalcycl#chp.opalcycl[_OPAL-cycl_]. This method puts _OPAL_ in _OPAL-cycl_ mode (see Chapter link:opalcycl#chp.opalcycl[_OPAL-cycl_]).
* `STATISTICAL-ERRORS` * `STATISTICAL-ERRORS`
This is a method to let _OPAL_ run multiple times in parallel while This is a method to let _OPAL_ run multiple times in parallel while
adding imperfections to alignment and other physical quantities. adding imperfections to alignment and other physical quantities.
FIELDSOLVER:: FIELDSOLVER::
The field solver to be used see Chapter link:fieldsolvers#chp.fieldsolvers[Field Solver]. The field solver to be used (see Chapter link:fieldsolvers#chp.fieldsolvers[Field Solver]).
DISTRIBUTION:: DISTRIBUTION::
The particle distribution to be used see Chapter link:distribution#chp.distribution[Distribution]. The particle distribution to be used (see Chapter link:distribution#chp.distribution[Distribution]).
BEAM:: BEAM::
The particle beam see Chapter link:beam-command#chp.beam-command[Beam Command] to be used is specified. The particle beam (see Chapter link:beam-command#chp.beam-command[Beam Command]) to be used is specified.
TURNS:: TURNS::
The number of turns (integer) to be tracked (default: 1, namely single The number of turns (integer) to be tracked (default: 1, namely single
bunch). bunch).
...@@ -235,6 +235,11 @@ MB_ETA:: ...@@ -235,6 +235,11 @@ MB_ETA::
The scale parameter for binning in multi-bunch mode (default: 0.01). Only The scale parameter for binning in multi-bunch mode (default: 0.01). Only
used in `MB_BINNING=GAMMA`. Only available in _OPAL-cycl_. used in `MB_BINNING=GAMMA`. Only available in _OPAL-cycl_.
+ +
BOUNDARYGEOMETRY::
The boundary geometry specification is used for
particle termination (see Chapter link:geometry#chp.geometry[Geometry]).
+
TRACKBACK:: TRACKBACK::
The particles are tracked backward in time if `TRUE`. The particles are tracked backward in time if `TRUE`.
Only available in _OPAL-t_. Default is `FALSE`. Only available in _OPAL-t_. Default is `FALSE`.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment