diff options
| author | jthorn <jthorn@0a4070d5-58f5-498f-b6c0-2693e757fa0f> | 2005-06-13 15:54:57 +0000 |
|---|---|---|
| committer | jthorn <jthorn@0a4070d5-58f5-498f-b6c0-2693e757fa0f> | 2005-06-13 15:54:57 +0000 |
| commit | 8902dd74f1f5669dc1d49dd7a4474a545b2cd30c (patch) | |
| tree | 3db62698d43f561f465d1f58c0823950d72f623b | |
| parent | a4226e9f55f3ecbc0e52ce7e96d86dd9ab2959b3 (diff) | |
typo fix
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinInitialData/IDAxiBrillBH/trunk@77 0a4070d5-58f5-498f-b6c0-2693e757fa0f
| -rw-r--r-- | doc/documentation.tex | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/documentation.tex b/doc/documentation.tex index 96444be..0331d01 100644 --- a/doc/documentation.tex +++ b/doc/documentation.tex @@ -222,7 +222,7 @@ stack, whose size depends on the $\eta$ and $\theta$ resolutions. For high resolutions these arrays may exceed system- and/or shell-imposed limits on the maximum stack size, causing the code to crash (core-dump). In an ideal world, someone would fix the offending code to allocate -large arrays on the heap. Unless/Until that happens, you can either +large arrays on the heap. Unless/until that happens, you can either use lower resolution :(, or try raising the operating-system and/or shell stack-size limits. For example, using \verb|tcsh| the shell command \verb|limit| |