diff options
| author | allen <allen@57bc7290-fb3d-4efd-a9b1-28e84cce6043> | 2002-08-18 20:10:28 +0000 |
|---|---|---|
| committer | allen <allen@57bc7290-fb3d-4efd-a9b1-28e84cce6043> | 2002-08-18 20:10:28 +0000 |
| commit | 48ab0b9edc8516d26be57e48699e051a1f2d3cd6 (patch) | |
| tree | 0a70312c2affe455d398563fd4366b19bcfbd2cd | |
| parent | 76a16a26a4b916379216b693f329f4093b5dfc5a (diff) | |
remove bad labels
Fixes Cactus/1190
git-svn-id: http://svn.cactuscode.org/arrangements/CactusElliptic/EllBase/trunk@71 57bc7290-fb3d-4efd-a9b1-28e84cce6043
| -rw-r--r-- | doc/documentation.tex | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/documentation.tex b/doc/documentation.tex index bd65ff7..332af7b 100644 --- a/doc/documentation.tex +++ b/doc/documentation.tex @@ -295,8 +295,7 @@ for this elliptic problem has been registered. The registration process is part of the authors thorn, not part of EllBase. There is no need to change code in EllBase. Usually, a author of solver routines will register the routines that register an elliptic equation class -and/or an elliptic solver at STARTUP (see \ref{sec:RFR} for information on - scheduling). If a author registers both, class and solver, you must make +and/or an elliptic solver in the STARTUP timebin. If a author registers both, class and solver, you must make sure, that the elliptic class is registered {\em before} the solver registration takes place. @@ -431,7 +430,7 @@ c We have no storage for M if they are of size one in each direction \end{verbatim} This Fortran solver receives the following arguments: the ``typical'' - CCTK\_ARGUMENTS (see \ref{sec:cctk_Arguments}): {\tt \_CCTK\_ARGUMENTS}, + CCTK\_ARGUMENTS: {\tt \_CCTK\_ARGUMENTS}, the {\em size} of the coefficient matrix: {\tt Mlinear\_lsh}, the coefficient matrix {\tt Mlinear}, the variable to solve for: {\tt var}, and the two arrays with convergence information. |