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 389d0db7 authored by ext-calvo_p's avatar ext-calvo_p
Browse files

fix ref to beam chapter

parent ce339167
No related branches found
No related tags found
No related merge requests found
......@@ -13,10 +13,10 @@ endif::[]
=== Track Mode
Before starting to track, a link:lines#chp.lines[`LINE`] and a
link:beam#chp.beam[`BEAM`] must be selected. The time step (`DT`) and the
maximal steps to track (`MAXSTEPS`) or `ZSTOP` should be set. This
command causes _OPAL_ to enter "tracking mode", in which it accepts
only the track commands see <<tab_TRACK_Commands>>. In order to perform
link:beam-command#chp.beam-command[`BEAM`] must be selected. The time
step (`DT`) and the maximal steps to track (`MAXSTEPS`) or `ZSTOP` should be
set. This command causes _OPAL_ to enter "tracking mode", in which it accepts
only the track commands (see <<tab_TRACK_Commands>>). In order to perform
several tracks, specify arrays of parameter in `DT`, `MAXSTEPS` and
`ZSTOP`. This can be used to change the time step manually.
......@@ -157,7 +157,7 @@ TRACK, LINE=name, BEAM=name, MAXSTEPS=value, STEPSPERTURN=value;
Particles are tracked in parallel, i.e. the coordinates of all particles
are transformed at each beam element as it is reached.
_OPAL_ leaves *track mode* when it sees the command
_OPAL_ leaves *track mode* when it sees the command
----
ENDTRACK;
......
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