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, 3 insertions, 2 deletions

diff --git a/Carpet/Carpet/src/Comm.cc b/Carpet/Carpet/src/Comm.cc
index 80cea30c5..b09869ef9 100644
--- a/Carpet/Carpet/src/Comm.cc
+++ b/Carpet/Carpet/src/Comm.cc
@@ -166,7 +166,8 @@ namespace Carpet {
       if (sync_during_time_integration or local_do_prolongate) {
         SyncGroups (cctkGH, goodgroups);
       }
-    }
+
+    } // for g
 
     return retval;
   }
@@ -178,7 +179,7 @@ namespace Carpet {
   {
     DECLARE_CCTK_PARAMETERS;
     const int tl = 0;
-
+    
     // use the current time here (which may be modified by the user)
     const CCTK_REAL time
       = (cctkGH->cctk_time - initial_time) / delta_time;