diff options
author | tradke <tradke@ff385933-4943-42dc-877b-ffc776028de6> | 2007-04-27 12:34:54 +0000 |
---|---|---|
committer | tradke <tradke@ff385933-4943-42dc-877b-ffc776028de6> | 2007-04-27 12:34:54 +0000 |
commit | 557ad97a32dd12d155d243e5279bbcbf352b8cca (patch) | |
tree | 5c5067127c99e523f528d83f24956b616517e9c9 | |
parent | 01afd6f3d409fc294fff0cf65ec0c3caaf65b2cd (diff) |
fix wording in description of verbose output
git-svn-id: http://svn.cactuscode.org/arrangements/CactusUtils/NaNChecker/trunk@82 ff385933-4943-42dc-877b-ffc776028de6
-rw-r--r-- | doc/documentation.tex | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/documentation.tex b/doc/documentation.tex index 5ad1df6..6dd4068 100644 --- a/doc/documentation.tex +++ b/doc/documentation.tex @@ -71,9 +71,10 @@ Currently these actions can be to just print a level 1 warning message telling you where NaNs/Infs were found and how many (for grid array variables).\\ - For grid arrays it will also print information with the array index - (in fortran order) for all NaN/Inf elements, depending on the value of - the keyword parameter {\tt verbose}. You can limit the number of + If the keyword parameter {\tt verbose} is set to {\tt "all"} then for each + grid array it will also print the grid indices (in Fortran notation) + and the physical coordinates for all NaN/Inf elements found. + You can limit the number of such warnings by setting the {\tt NanChecker::report\_max} parameter. \item{\tt terminate} |