aboutsummaryrefslogtreecommitdiff
path: root/param.ccl
diff options
context:
space:
mode:
authordiener <diener@2a26948c-0e4f-0410-aee8-f1d3e353619c>2004-03-03 16:43:25 +0000
committerdiener <diener@2a26948c-0e4f-0410-aee8-f1d3e353619c>2004-03-03 16:43:25 +0000
commit564c15048d03894c2dd2315c54cebeb07ebf70be (patch)
tree73844ef28b7d9836867bdbedc2e4e72daec65232 /param.ccl
parentcc166f4d2e715bdfdef04e217602a18acdbef1ae (diff)
Added a cheat parameter to enable the reuse of the final data set for a
number of iterations before starting the real backwards evolution of the level set function. If everything is stationary this should be okay. If it is only approximately stationary, the evolution of the level set function is dubious but the trial surfaces might get closer to the real event horizon. Testing is definitely necessary. Don't use it unless you really know what you are doing. The implementation is also slightly dubious, since I modify cctk_iteration to start out with negative iteration numbers. There might be a more elegant way of doing this. git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/EHFinder/trunk@167 2a26948c-0e4f-0410-aee8-f1d3e353619c
Diffstat (limited to 'param.ccl')
-rw-r--r--param.ccl9
1 files changed, 9 insertions, 0 deletions
diff --git a/param.ccl b/param.ccl
index 0007865..7c2a3b2 100644
--- a/param.ccl
+++ b/param.ccl
@@ -30,6 +30,15 @@ BOOLEAN read_conformal_factor_once "Should the conformal factor only be read onc
{
} "yes"
+BOOLEAN cheat "Should we cheat and evolve using the last data set for a while?"
+{
+} "no"
+
+CCTK_INT cheat_iterations "For how many iterations should we cheat"
+{
+0:* :: "Positive please"
+} 0
+
KEYWORD initial_f[10] "Initial surface choice"
{
"sphere" :: "spherical surface"