aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorjthorn <jthorn@f88db872-0e4f-0410-b76b-b9085cfa78c5>2006-10-04 11:34:45 +0000
committerjthorn <jthorn@f88db872-0e4f-0410-b76b-b9085cfa78c5>2006-10-04 11:34:45 +0000
commitbbdf3fafd55cb8fb961cef06eb296ffeceb86ca4 (patch)
tree7725182f65fd60fa40b2d854bd60f6f650b3297a
parente6a9c6f2038f821a32bcc716baf8edaa53a6a881 (diff)
clarify comments for run_at_* parameters; no change in semantics
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/AHFinderDirect/trunk@1483 f88db872-0e4f-0410-b76b-b9085cfa78c5
-rw-r--r--param.ccl7
1 files changed, 3 insertions, 4 deletions
diff --git a/param.ccl b/param.ccl
index 4d31178..5289439 100644
--- a/param.ccl
+++ b/param.ccl
@@ -57,14 +57,13 @@ int find_every "how often should we try to find apparent horizons?"
# at CCTK_ANALYSIS. However, for some purposes it's more convenient
# to run at CCTK_POSTSTEP and/or CCTK_POSTINITIAL
#
-Boolean run_at_CCTK_ANALYSIS "should we run in CCTK_ANALYSIS schedule bin?"
+Boolean run_at_CCTK_ANALYSIS "should we run at CCTK_ANALYSIS?"
{
} true
-Boolean run_at_CCTK_POSTSTEP "should we run in CCTK_POSTSTEP schedule bin?"
+Boolean run_at_CCTK_POSTSTEP "should we run at CCTK_POSTSTEP?"
{
} false
-Boolean run_at_CCTK_POSTINITIAL \
- "should we run in CCTK_POSTINITIAL schedule bin?"
+Boolean run_at_CCTK_POSTINITIAL "should we run at CCTK_POSTINITIAL?"
{
} false