Split hamnormalized into its own variable group, so that it will work

properly with Cartoon.

Cartoon is now properly called by selecting variables for 'None'
boundary condition, and defining their proper tensortypealias in
interface.ccl.  Note that this illustrates how to trigger an entire
schedule group in the ANALYSIS time bin.


git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@84 b7a48df3-cbbf-4440-997f-b4b717c9f7fc

1 files changed, 17 insertions, 9 deletions

diff --git a/schedule.ccl b/schedule.ccl
index 7a33dd3..5e34880 100644
--- a/schedule.ccl
+++ b/schedule.ccl
@@ -1,4 +1,3 @@
-
 # Make sure there is storage for the conformal state flag
 # so we can use it irrespective of metric_type
 storage: conformal_state
@@ -20,21 +19,30 @@ schedule ADMConstraint_InitSymBound at CCTK_BASEGRID
 
 if (constraints_persist)
 {
-  STORAGE: hamiltonian,momentum
+  STORAGE: hamiltonian, normalized_hamiltonian, momentum
   schedule ADMConstraints at CCTK_POSTSTEP
   {
     LANG: Fortran
   } "Evaluate ADM constraints for use in other routines"
+
+  schedule GROUP ApplyBCs at CCTK_POSTSTEP after ADMConstraints
+  {
+  } "Apply (symmetry) boundary conditions"
 }
 else
 {
-  schedule ADMConstraints at CCTK_ANALYSIS
+  schedule GROUP ADMConstraintsGroup at CCTK_ANALYSIS
+  {
+    STORAGE: hamiltonian, normalized_hamiltonian, momentum
+    TRIGGERS: hamiltonian, normalized_hamiltonian, momentum
+  } "Evaluate ADM constraints, and perform symmetry boundary conditions"
+
+  schedule ADMConstraints in ADMConstraintsGroup
   {		
     LANG: Fortran
-    STORAGE: hamiltonian,momentum
-    TRIGGERS: hamiltonian,momentum
-  } "Evaluate ADM constraints" 
-}
-
-
+  } "Evaluate ADM constraints"
 
+  schedule GROUP ApplyBCs in ADMConstraintsGroup after ADMConstraints
+  {
+  } "Apply (symmetry) boundary conditions"
+}