add beginnings of support for using new CCTK_InterpGridArrays()

global interpolator & multiprocessor operation

... at present the CCTK_InterpGridArrays() support works fine,
    but only on 1 processor, I seem to get an infinite loop on
    multiple processors


git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/AHFinderDirect/trunk@917 f88db872-0e4f-0410-b76b-b9085cfa78c5

1 files changed, 18 insertions, 9 deletions

diff --git a/param.ccl b/param.ccl
index 9b8ebe5..8466572 100644
--- a/param.ccl
+++ b/param.ccl
@@ -545,13 +545,20 @@ keyword integral_method "how do we compute integrals over the horizon?"
 
 keyword geometry_method "how do we compute the slice's geometry?"
 {
-# for normal use
-"interpolate from Cactus grid" :: "interpolate gij and Kij from Cactus grid"
+# this would be for normal use, but it doesn't work yet :( :( :(
+"globally interpolate from Cactus grid" :: \
+   "interpolate gij and Kij from global Cactus grid \
+    using CCTK_InterpGridArrays() global interpolator API"
+
+# use this for now
+"locally interpolate from Cactus grid" :: \
+   "interpolate gij and Kij from local Cactus grid on this processor \
+    using CCTK_InterpLocalUniform() localinterpolator API"
 
 # for testing/debugging
 "Schwarzschild/EF"             :: \
   "hard-wire to Schwarzschild spacetime / Eddington-Finkelstein slice"
-} "interpolate from Cactus grid"
+} "locally interpolate from Cactus grid"
 
 ########################################
 
@@ -562,10 +569,6 @@ keyword geometry_method "how do we compute the slice's geometry?"
 # Cactus grid to the position of each trial horizon surface, giving
 # gij, Kij, and partial_x gij as outputs.  This interpolator must have
 # the following properties:
-# - It must be able to accept the Cactus grid as an input domain.  The
-#   current implementation uses the  CCTK_InterpLocalUniform()  API; this
-#   is processor-local and so restricts the whole apparent horizon finder
-#   to single-processor operation.
 # - It must support taking at least 1st derivatives as part of the
 #   interpolation.
 # - It should give at least $C^1$ interpolants for smooth data, otherwise
@@ -578,10 +581,16 @@ keyword geometry_method "how do we compute the slice's geometry?"
 # thorn).
 #
 
+string coordinate_system_name \
+  "name under which the coordinate system is registered in Cactus"
+{
+.+ :: "any string (in practice it should be nonempty)"
+} "cart3d"
+
 string geometry_interpolator_name \
   "name under which the geometry interpolation operator is registered in Cactus"
 {
-.* :: "any string"
+.+ :: "any string"
 } "Hermite polynomial interpolation"
 
 string geometry_interpolator_pars \
@@ -679,7 +688,7 @@ boolean check_that_geometry_is_finite \
 string interpatch_interpolator_name \
   "name under which the interpatch interpolation operator is registered in Cactus"
 {
-.* :: "any string"
+.+ :: "any string (in practice it should be nonempty)"
 } "Lagrange polynomial interpolation"
 
 string interpatch_interpolator_pars \