- add a parameter to choose when to schedule the ID

- add a parameter for multiplying an already computed lapse to the
  one computed here

This does not change the default behaviour.
However, the testsuite fails - but it also failed before this change in
the same way. Does anybody know anything about this?
-> It fails at exactly one point in the 1D-slices, but only in y and z
   directions


git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinInitialData/TwoPunctures/trunk@59 b2a53a04-0f4f-0410-87ed-f9f25ced00cf

1 files changed, 17 insertions, 5 deletions

diff --git a/schedule.ccl b/schedule.ccl
index bc410ca..4d6e4ee 100644
--- a/schedule.ccl
+++ b/schedule.ccl
@@ -12,10 +12,22 @@ if (CCTK_Equals(initial_data, "twopunctures"))
     LANG: C
   } "Check parameters and thorn needs"
 
-  SCHEDULE TwoPunctures IN ADMBase_InitialData
+  if (schedule_in_ADMBase_InitialData)
   {
-    LANG: C
-    STORAGE: puncture_u
-    SYNC: ADMBase::metric ADMBase::curv ADMBase::lapse
-  } "Create puncture black hole initial data"
+    SCHEDULE TwoPunctures IN ADMBase_InitialData
+    {
+      LANG: C
+      STORAGE: puncture_u
+      SYNC: ADMBase::metric ADMBase::curv ADMBase::lapse
+    } "Create puncture black hole initial data"
+  }
+  else
+  {
+    SCHEDULE TwoPunctures AT Initial AFTER ADMBase_InitialData BEFORE ADMBase_PostInitial AFTER TOV_Initial_Data
+    {
+      LANG: C
+      STORAGE: puncture_u
+      SYNC: ADMBase::metric ADMBase::curv ADMBase::lapse
+    } "Create puncture black hole initial data"
+  }
 }