[cig-commits] r14265 - short/2.5D/benchmarks/savageprescott

[willic3 at geodynamics.org]

Author: willic3
Date: 2009-03-08 19:55:25 -0700 (Sun, 08 Mar 2009)
New Revision: 14265

Modified:
   short/2.5D/benchmarks/savageprescott/README
Log:
Modified top-level README to include discussion about using velocity
results.



Modified: short/2.5D/benchmarks/savageprescott/README
===================================================================
--- short/2.5D/benchmarks/savageprescott/README	2009-03-09 02:44:28 UTC (rev 14264)
+++ short/2.5D/benchmarks/savageprescott/README	2009-03-09 02:55:25 UTC (rev 14265)
@@ -4,8 +4,9 @@
 occurs at regular recurrence intervals on the upper locked part of the
 fault, while constant-velocity creep occurs on the lower part of the fault.
 This directory contains the files necessary to run the problem using
-PyLith, as well as a utils directory that contains a Python script and
-.cfg file to compute the analytical solution.
+PyLith, as well as a utils directory that contains a Python scripts and
+.cfg files to compute the analytical solution, and to generate velocity
+results for the PyLith solutions.
 
 To run the PyLith simulation, go to the parameters directory and run one
 of the shell scripts, or just run PyLith directly using the appropriate
@@ -16,21 +17,26 @@
 package such as ParaView.
 
 The simplest way to compare the numerical and analytical solutions is to
-look at profile results using a plotting package. The savpres_ss.py
-script will produce a comma-separated-values file (savageprescott.csv) that
-is easy to use with a plotting package. For results from PyLith, it is
-probably easiest to generate profile results using ParaView (e.g., the
-"Plot Over Line" filter). By loading the entire time series for the
-ground surface results, it is possible to generate profile results for
-all time steps. For comparison with the analytical results, it is easiest
-to use a profile coincident with the x-axis that extends from x=0 to the
-right-hand side of the mesh. The profiles can also be saved as CSV files
-from ParaView.
+look at profile velocity results using a plotting package. The savpres_ss.py
+script will produce comma-separated-values files for displacements and
+velocities (savpres_displ.csv, savpres_vel.csv) that are easy to use with a
+plotting package.
 
 Note that it is not possible to directly compare the PyLith results with the
 analytical solution. This is because the analytical solution assumes steady
 asthenospheric flow at the beginning of computations, while the numerical
 solution requires several earthquake cycles to reach this state. For direct
-comparison, it is therefore more reasonable to reference all results to
-the displacement field immediately following an earthquake. This is what was
-done for the figures contained in the "figures" directory.
+comparison, you can either reference all results to the displacement field
+immediately following an earthquake, or you can look at velocity results.
+
+There is an additional script in the utils directory (vtkdiff.py) that
+computes velocities from PyLith displacement results. See the README in the
+utils directory to find out how to do this. This will create a set of VTK
+files that you can use with ParaView.  You can generate profile results
+using ParaView (e.g., the "Plot Over Line" filter). By loading the entire
+time series for the ground surface velocity results, it is possible to
+generate profile results for all time steps. For comparison with the
+analytical results, it is easiest to use a profile coincident with the
+x-axis that extends from x=0 to the right-hand side of the mesh. The
+profiles can also be saved as CSV files from ParaView.
+