As per my proposal in

   http://www.cactuscode.org/pipermail/developers/2005-March/000815.html
add a new parameter  copy_ID_after_MoL_PostStep  to control precisely
*when* in CCTK_POSTINITIAL  MoL_FillAllLevels  is scheduled
if  initial_data_is_crap  is set.

The default (MoL_FillAllLevels is scheduled *before* MoL_PostStep)
matches the previous behavior, so there's no change required to par
files unless you want the new behavior (MoL_FillAllLevels is scheduled
*after* MoL_PostStep).


git-svn-id: http://svn.cactuscode.org/arrangements/CactusNumerical/MoL/trunk@87 578cdeb0-5ea1-4b81-8215-5a3b8777ee0b

1 files changed, 14 insertions, 4 deletions

diff --git a/schedule.ccl b/schedule.ccl
index ca5085e..55af153 100644
--- a/schedule.ccl
+++ b/schedule.ccl
@@ -130,10 +130,20 @@ schedule MoL_ReportNumberVariables AT Wragh AFTER MoL_Register
 
 if (initial_data_is_crap)
 {
-  schedule MoL_FillAllLevels AT PostInitial
+  if (copy_ID_after_MoL_PostStep)
   {
-    LANG:C
-  } "A bad routine. Fills all previous timelevels with data copied from the current."
+    schedule MoL_FillAllLevels AT PostInitial AFTER MoL_PostStep
+    {
+      LANG:C
+    } "A bad routine. Fills all previous timelevels with data copied from the current."
+  }
+  else
+  {
+    schedule MoL_FillAllLevels AT PostInitial BEFORE MoL_PostStep
+    {
+      LANG:C
+    } "A bad routine. Fills all previous timelevels with data copied from the current."
+  }
 }
 
 ##########################################
@@ -569,7 +579,7 @@ schedule GROUP MoL_PostStep IN MoL_Step AFTER MoL_Add
 {
 } "The group for physics thorns to schedule boundary calls etc."
 
-schedule GROUP MoL_PostStep AT PostInitial AFTER MoL_FillAllLevels
+schedule GROUP MoL_PostStep AT PostInitial
 {
 } "Ensure that everything is correct after the initial data have been set up"