diff options
| author | rideout <rideout@c78560ca-4b45-4335-b268-5f3340f3cb52> | 2002-07-04 08:41:43 +0000 |
|---|---|---|
| committer | rideout <rideout@c78560ca-4b45-4335-b268-5f3340f3cb52> | 2002-07-04 08:41:43 +0000 |
| commit | 1eac216dcbc813bb0c5acb1d1292563bdec463d0 (patch) | |
| tree | 3f077ce8b5f7be2914d86879453de0cb984811f0 | |
| parent | e8f2677f55b090c781e773476fc3fe25aa41cf60 (diff) | |
typo and formatting fixes
git-svn-id: http://svn.cactuscode.org/arrangements/CactusBase/CartGrid3D/trunk@166 c78560ca-4b45-4335-b268-5f3340f3cb52
| -rw-r--r-- | doc/documentation.tex | 12 |
1 files changed, 5 insertions, 7 deletions
diff --git a/doc/documentation.tex b/doc/documentation.tex index 18dc45e..cca267c 100644 --- a/doc/documentation.tex +++ b/doc/documentation.tex @@ -100,7 +100,7 @@ up the integer {\em grid size\/} ({\it eg} 128), floating-point determined automagically from this information and the \verb|driver::global_nx|, \verb|driver::global_ny|, and \verb|driver::global_nz| grid-size parameters. You should - also chose the \verb|grid::domain| parameter consistent with + also choose the \verb|grid::domain| parameter consistent with all these other parameters. (It's not clear whether or not the code ever explicitly checks this.) \item[{\tt grid::type = "box"}]\mbox{}\\ @@ -124,11 +124,9 @@ There are also a number of optional parameters which can be used to specify whether or not it's ok to have a grid point with an $x$, $y$, and/or $z$ coordinate exactly equal to 0: \begin{description} -\item[{\tt grid::no\_originx}] -\item[{\tt grid::no\_originy}] -\item[{\tt grid::no\_originz}] -\item[{\tt grid::no\_origin}]\mbox{}\\ - These parameters are all deprecated -- don't use them! +\item[{\tt grid::no\_originx}, {\tt grid::no\_originy}, {\tt +grid::no\_originz}, {\tt grid::no\_origin}]\mbox{}\\ + These parameters are all deprecated --- don't use them! \item[{\tt grid::avoid\_originx}]\mbox{}\\ This is a Boolean parameter; if set to true (\verb|grid::avoid_originx = "true"| or @@ -269,7 +267,7 @@ Each grid function can register how it behaves under a coordinate change using function calls in {\tt CartGrid3D}. These symmetry properties can then be used by other thorns, for example {\tt CactusBase/Boundary} uses them to enforce symmetry boundary -conditions across coordinate axis. Symmetries should obviously be +conditions across coordinate axes. Symmetries should obviously be registered before they are used, but since they can be different for different grids, they must be registered {\it after} the {\tt CCTK\_STARTUP} timebin. The usual place to register symmetries |