New routines for calculating where 1D and 2D slices are located for output

from a 3D grid function. See the documentation (in a couple of days!) for
full details, or just check out the parameter options.

The main difference from before is that the default is to place the lines/slices
at the zero value of the coordinate system.  For a full grid this is different, from before, since the lines/slices were placed in the center of the grid.

(The big benefit of changing it is not only to make it consistent, but
to remove all knowledge of those pesky symmetry options from the IO thorns).


git-svn-id: http://svn.cactuscode.org/arrangements/CactusBase/IOUtil/trunk@78 b32723a9-ab3a-4a60-88e2-2e5d99d7c17a

1 files changed, 92 insertions, 9 deletions

diff --git a/param.ccl b/param.ccl
index 7cb0d1a..f94ccb5 100644
--- a/param.ccl
+++ b/param.ccl
@@ -1,15 +1,6 @@
 # Parameter definitions for thorn IOUtil
 
 #############################################################################
-### import grid parameters
-#############################################################################
-shares: grid
-
-USES KEYWORD domain ""
-{
-}
-
-#############################################################################
 ### declare IOUtil parameters
 ### These are declared protected so that they can be seen by other IO thorns.
 #############################################################################
@@ -141,3 +132,95 @@ STRING recover_ID_vars "List of variables to read in from the given initial data
 {
   .* :: A regex which matches everything
 } "all"
+
+
+
+CCTK_REAL out_xline_y "y-coord for 1D lines in x-direction"
+{
+ *:* :: ""
+} 0.0
+CCTK_REAL out_xline_z "z-coord for 1D lines in x-direction"
+{
+ *:* :: ""
+} 0.0
+
+CCTK_REAL out_yline_x "x-coord for 1D lines in y-direction"
+{
+ *:* :: ""
+} 0.0
+CCTK_REAL out_yline_z "z-coord for 1D lines in y-direction"
+{
+ *:* :: ""
+} 0.0 
+
+CCTK_REAL out_zline_x "x-coord for 1D lines in z-direction"
+{
+ *:* :: ""
+} 0.0
+CCTK_REAL out_zline_y "y-coord for 1D lines in z-direction"
+{
+ *:* :: ""
+} 0.0
+
+CCTK_INT out_xline_yi "y-index (from 0) for 1D lines in x-direction"
+{
+ 0:* :: ""
+} 0
+CCTK_INT out_xline_zi "z-index (from 0) for 1D lines in x-direction"
+{
+ 0:* :: ""
+} 0
+
+CCTK_INT out_yline_xi "x-index (from 0) for 1D lines in y-direction"
+{
+ 0:* :: ""
+} 0
+CCTK_INT out_yline_zi "z-index (from 0) for 1D lines in y-direction"
+{
+ 0:* :: ""
+} 0
+
+CCTK_INT out_zline_xi "x-index (from 0) for 1D lines in z-direction"
+{
+ 0:* :: ""
+} 0
+CCTK_INT out_zline_yi "y-index (from 0) for 1D lines in z-direction"
+{
+ 0:* :: ""
+} 0
+
+
+############################
+# Specific to 2D output
+# Choosing what output to do
+############################
+CCTK_REAL out_yzplane_x "x-coord for 2D planes in yz"
+{
+ *:* :: ""
+} 0.0
+
+CCTK_REAL out_xzplane_y "y-coord for 2D planes in xz"
+{
+ *:* :: ""
+} 0.0
+
+CCTK_REAL out_xyplane_z "z-coord for 2D planes in xy"
+{
+ *:* :: "" 
+} 0.0
+
+CCTK_INT out_xyplane_zi "z-index (from 0) for 2D planes in xy"
+{
+ 0:* :: ""
+} 0
+
+CCTK_INT out_xzplane_yi "y-index (from 0) for 2D planes in xz"
+{
+ 0:* :: ""
+} 0
+
+CCTK_INT out_yzplane_xi "x-index (from 0) for 2D planes in yz"
+{
+ 0:* :: ""
+} 0
+