[cig-commits] r19755 - short/3D/PyLith/trunk/examples/3d/hex8

[brad at geodynamics.org]

Author: brad
Date: 2012-03-08 17:27:46 -0800 (Thu, 08 Mar 2012)
New Revision: 19755

Modified:
   short/3D/PyLith/trunk/examples/3d/hex8/output_points.txt
   short/3D/PyLith/trunk/examples/3d/hex8/step19.cfg
Log:
Added comments.

Modified: short/3D/PyLith/trunk/examples/3d/hex8/output_points.txt
===================================================================
--- short/3D/PyLith/trunk/examples/3d/hex8/output_points.txt	2012-03-09 01:22:28 UTC (rev 19754)
+++ short/3D/PyLith/trunk/examples/3d/hex8/output_points.txt	2012-03-09 01:27:46 UTC (rev 19755)
@@ -1,6 +1,12 @@
 # This file contains a list of points where we want the solution. The
 # solution will be interpolated to these points, so they need not
 # coincide with vertices of the mesh.
+#
+# We specify the coordinates in the default coordinate system (3-D
+# Cartesian). To specify points in another coordinate system, use the
+# coordsys component of the OutputSolnPoints object. The points will
+# be transformed into the coordinate system of the mesh before
+# interpolation.
 10.0 10.0  -500.0
 10.0 10.0 -1500.0
 10.0 10.0 -2500.0

Modified: short/3D/PyLith/trunk/examples/3d/hex8/step19.cfg
===================================================================
--- short/3D/PyLith/trunk/examples/3d/hex8/step19.cfg	2012-03-09 01:22:28 UTC (rev 19754)
+++ short/3D/PyLith/trunk/examples/3d/hex8/step19.cfg	2012-03-09 01:27:46 UTC (rev 19755)
@@ -147,6 +147,10 @@
 
 # Give basename for VTK domain output of solution at points.
 [pylithapp.problem.formulation.output.points]
+# We use the default coordinate system for the points. Changing the
+# coordinate system allows the filename with the list of points to use
+# any compatible coordinate system recognized by the spatialdata
+# package.
 reader.filename = output_points.txt
 writer.filename = output/step19-points.vtk
 writer.time_constant = 1.0*year