Introduce a parameter to choose whether MoL applies

boundary conditions (and synchronization, and prolongation)
to the initial data.


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

2 files changed, 14 insertions, 4 deletions

diff --git a/param.ccl b/param.ccl
index e82dd07..43a1fd4 100644
--- a/param.ccl
+++ b/param.ccl
@@ -220,3 +220,7 @@ KEYWORD verbose "How verbose should MoL be?"
   "register" :: "List the variables registered as well"
   "extreme"  :: "Everything you never wanted to know"
 } "normal"
+
+BOOLEAN set_ID_boundaries "Should boundaries be overwritten (via synchronization, prolongation, boundary conditions) by MoL?"
+{
+} "yes"
diff --git a/schedule.ccl b/schedule.ccl
index 8dc65f9..48283fd 100644
--- a/schedule.ccl
+++ b/schedule.ccl
@@ -646,9 +646,12 @@ 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
+if (set_ID_boundaries)
 {
-} "Ensure that everything is correct after the initial data have been set up"
+  schedule GROUP MoL_PostStep AT PostInitial
+  {
+  } "Ensure that everything is correct after the initial data have been set up"
+}
 
 ##################################################################
 ###  Schedule the PostStep parts in the Carpet 'PostRegrid'    ###
@@ -668,9 +671,12 @@ schedule GROUP MoL_PostStep AT PostRegrid
 ###  expensive, but it's simplest for the moment.              ###
 ##################################################################
 
-schedule GROUP MoL_PostStep AT PostRestrictInitial
+if (set_ID_boundaries)
 {
-} "Ensure that everything is correct after restriction"
+  schedule GROUP MoL_PostStep AT PostRestrictInitial
+  {
+  } "Ensure that everything is correct after restriction"
+}
 
 schedule GROUP MoL_PostStep AT PostRestrict
 {