Check to see that no grid variable has more than 15 dimensions. The

restriction comes from specifying a set of faces using a single signed
32 bit integer.  It may be possible to use two more bits, which would
provide an extra dimension, but this seems unnecessary at the moment.
Note that (as pointed out by Erik Schnetter, on the flesh mailing list)
we are assuming that the integer is at least 32 bits, which is not
guaranteed by C.  Might this pose a problem?  Should we restrict
ourselves to (16-1)/2 = 7 dimensions?


git-svn-id: http://svn.cactuscode.org/arrangements/CactusBase/Boundary/trunk@235 6a38eb6e-646e-4a02-a296-d141613ad6c4

1 files changed, 5 insertions, 0 deletions

diff --git a/schedule.ccl b/schedule.ccl
index 9e5d248..9afb8e6 100644
--- a/schedule.ccl
+++ b/schedule.ccl
@@ -1,6 +1,11 @@
 # Schedule definitions for thorn Boundary
 # $Header$
 
+schedule Boundary_Check at CCTK_PARAMCHECK
+{
+  lang: C
+} "Check dimension of grid variables"
+
 schedule Boundary_RegisterBCs at CCTK_BASEGRID
 {
   lang: C