[cig-commits] r14198 - short/2.5D/benchmarks/savageprescott/parameters

[willic3 at geodynamics.org]

Author: willic3
Date: 2009-03-02 18:33:54 -0800 (Mon, 02 Mar 2009)
New Revision: 14198

Added:
   short/2.5D/benchmarks/savageprescott/parameters/README
Log:
Added brief README to parameters directory.



Added: short/2.5D/benchmarks/savageprescott/parameters/README
===================================================================
--- short/2.5D/benchmarks/savageprescott/parameters/README	                        (rev 0)
+++ short/2.5D/benchmarks/savageprescott/parameters/README	2009-03-03 02:33:54 UTC (rev 14198)
@@ -0,0 +1,28 @@
+This directory contains the .cfg files and spatial databases needed to run
+the benchmark. The simulations may either be run using the shell scripts
+(spbm_xxx.sh) or by running the commands contained in the scripts. This
+will take the form:
+pylith spbm_xxx.cfg timedep.cfg
+
+The default parameters, which are independent of the mesh used, are
+contained in pylithapp.cfg. Additional mesh-dependent parameters are given
+in the spbm_xxx.cfg files. The timedep.cfg file contains parameters specific
+to time-dependent fault slip. There are four different cases so far:
+
+spbm_hex8_unif1_20km.cfg:	This is a simple uniform mesh with a fault
+completely contained in the elastic layer. The mesh resolution is 20 km
+throughout.
+
+spbm_hex8_unif2_20km.cfg:	This is identical to the previous case,
+except that the fault extends all the way through the mesh (even though no
+slip is applied below the elastic layer. This case is used for testing our
+fault implementation and should not generally be used by end users.
+
+spbm_hex8_graded1_20km.cfg:	This uses a mesh with an initial resolution
+of 20 km that includes one level of refinement surrounding the center of the
+mesh. The fault is completely contained in the elastic layer.
+
+spbm_hex8_graded2_20km.cfg:	This is identical to the graded1 case,
+except that the fault extends all the way through the mesh (even though no
+slip is applied below the elastic layer. This case is used for testing our
+fault implementation and should not generally be used by end users.