Carpet: Use thorn InitBase to manage initial data setup

Thorn InitBase specifies how initial data should be calculated.  There
can be three possibilities:

init_some_levels: Set up at least one time level; other time levels
are scratch space

init_single_level: Set up exactly one time level; other time levels
are not acessed

init_all_levels: Set up all active time levels

Carpet checks this parameter and ensures that this setting is
consistent with Carpet's parameters

init_each_timelevel
init_fill_timelevels
init_3_timelevels

The new parameter init_fill_timelevels copies the current time level
into all past time levels, very similar to what
MoL::initial_data_is_crap does.

darcs-hash:20070706122545-dae7b-57ccca2954b1bd7ad98771e689c6c5b569c238cc.gz

1 files changed, 9 insertions, 0 deletions

diff --git a/Carpet/Carpet/param.ccl b/Carpet/Carpet/param.ccl
index c773686c4..a16b9bfe8 100644
--- a/Carpet/Carpet/param.ccl
+++ b/Carpet/Carpet/param.ccl
@@ -10,6 +10,11 @@ USES CCTK_REAL cctk_final_time
 USES CCTK_REAL max_runtime 
 
 
+shares: InitBase
+
+USES KEYWORD initial_data_setup_method
+
+
 shares: IO
 
 USES STRING out_dir
@@ -438,6 +443,10 @@ BOOLEAN init_each_timelevel "Call initial data routines once for each timelevel"
 {
 } "no"
 
+BOOLEAN init_fill_timelevels "Fill past time levels from current time level after calling initial data routines" STEERABLE=always
+{
+} "no"
+
 BOOLEAN prolongate_initial_data "Prolongate the refined regions during initial data generation" STEERABLE=always
 {
 } "no"