[cig-commits] r11403 - in short/3D/PyLith/trunk/examples/twocells: twohex8 twoquad4 twotet4 twotet4-geoproj twotri3
willic3 at geodynamics.org
willic3 at geodynamics.org
Tue Mar 11 11:22:18 PDT 2008
Author: willic3
Date: 2008-03-11 11:22:18 -0700 (Tue, 11 Mar 2008)
New Revision: 11403
Added:
short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation.jpg
Removed:
short/3D/PyLith/trunk/examples/twocells/twohex8/dislocation_disp.spatialdb
short/3D/PyLith/trunk/examples/twocells/twoquad4/dislocation_disp.spatialdb
short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/axialdisp.spatialdb
short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation_disp.spatialdb
short/3D/PyLith/trunk/examples/twocells/twotet4/dislocation_disp.spatialdb
short/3D/PyLith/trunk/examples/twocells/twotri3/dislocation_disp.spatialdb
Modified:
short/3D/PyLith/trunk/examples/twocells/twohex8/README
short/3D/PyLith/trunk/examples/twocells/twoquad4/README
short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation.cfg
short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation_slip.spatialdb
short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation_sliprate.spatialdb
short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation_sliptime.spatialdb
short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/pylithapp.cfg
short/3D/PyLith/trunk/examples/twocells/twotet4/README
short/3D/PyLith/trunk/examples/twocells/twotri3/README
Log:
Updated examples to be consistent with the tutorials.
Modified: short/3D/PyLith/trunk/examples/twocells/twohex8/README
===================================================================
--- short/3D/PyLith/trunk/examples/twocells/twohex8/README 2008-03-11 17:55:52 UTC (rev 11402)
+++ short/3D/PyLith/trunk/examples/twocells/twohex8/README 2008-03-11 18:22:18 UTC (rev 11403)
@@ -32,13 +32,11 @@
3. dislocation: Fault displacements are applied between the two
elements, while the left and right corners are fixed in x, y, and z.
a. dislocation.cfg: Parameter settings for this problem.
- b. dislocation.spatialdb: Boundary condition database for this
+ b. dislocation_slip.spatialdb: Fault slip database for this problem.
+ c. dislocation_sliprate.spatialdb: Fault slip rate database for this
problem.
- c. dislocation_disp.spatialdb: Fault slip database for this problem.
- d. dislocation_sliprate.spatialdb: Fault slip rate database for this
+ d. dislocation_sliptime.spatialdb: Fault slip time database for this
problem.
- e. dislocation_sliptime.spatialdb: Fault slip time database for this
- problem.
All of the files are documented. The 'pylithapp.cfg' file is read
automatically when running PyLith. To add to or override these
@@ -48,6 +46,7 @@
pylith sheardisp.cfg
pylith dislocation.cfg
-Each of these commands will produce a set of VTK files (one for each
-time step), which may be viewed with visualization packages such as
-ParaView or Mayavi.
+Each of these commands will produce a set of VTK files (including some that
+will be produced for each time step), which may be viewed with visualization
+packages such as ParaView or Mayavi. The JPEG files in this directory show
+sample visualizations for each problem using ParaView.
Deleted: short/3D/PyLith/trunk/examples/twocells/twohex8/dislocation_disp.spatialdb
===================================================================
--- short/3D/PyLith/trunk/examples/twocells/twohex8/dislocation_disp.spatialdb 2008-03-11 17:55:52 UTC (rev 11402)
+++ short/3D/PyLith/trunk/examples/twocells/twohex8/dislocation_disp.spatialdb 2008-03-11 18:22:18 UTC (rev 11403)
@@ -1,44 +0,0 @@
-#SPATIAL.ascii 1
-
-// This database is used to specify the boundary conditions for the
-// dislocation (kinematic fault) example.
-
-// This follows the format for a Simple DB (the only type presently available).
-SimpleDB {
-
- // There are 3 values specified in the database, corresponding to the
- // constraint values for the x, y, and z degrees of freedom.
- num-values = 3
- value-names = dof-0 dof-1 dof-2
-
- // The constraint values (displacements) have units of meters.
- value-units = m m m
-
- // The values are specified at two spatial locations.
- num-locs = 2
-
- // The dimension of the spatial distribution is 1, since the data
- // is being specified at points.
- data-dim = 1
-
- // The spatial dimension of the database is 3.
- space-dim = 3
-
- // We are specifying the data in a Cartesian coordinate system.
- cs-data = cartesian {
-
- // Our units are already in meters, so we can just multiply by one.
- to-meters = 1.0
-
- // We are using a 3D Cartesian coordinate system.
- space-dim = 3
- }
-}
-
-// This is where the data is specified.
-// As described in dislocation.cfg, this database will be used to specify
-// data along faces (pylith.bc.BCSixSides).
-// The entries are:
-// X-coord, Y-coord, Z-coord, dof-0, dof-1, dof-2.
--1.0 0.0 0.0 0.0 0.0 0.0
- 1.0 0.0 0.0 0.0 0.0 0.0
Modified: short/3D/PyLith/trunk/examples/twocells/twoquad4/README
===================================================================
--- short/3D/PyLith/trunk/examples/twocells/twoquad4/README 2008-03-11 17:55:52 UTC (rev 11402)
+++ short/3D/PyLith/trunk/examples/twocells/twoquad4/README 2008-03-11 18:22:18 UTC (rev 11403)
@@ -45,8 +45,7 @@
the left and right edges are fixed in x and y.
- dislocation.cfg: Parameter settings.
- - dislocation.spatialdb: Database of Dirichlet BC values.
- - dislocation_disp.spatialdb: Database of fault slip values.
+ - dislocation_slip.spatialdb: Database of fault slip values.
- dislocation_sliprate.spatialdb: Database of peak slip rate values.
- dislocation_sliptime.spatialdb: Database of slip initiation time values.
Deleted: short/3D/PyLith/trunk/examples/twocells/twoquad4/dislocation_disp.spatialdb
===================================================================
--- short/3D/PyLith/trunk/examples/twocells/twoquad4/dislocation_disp.spatialdb 2008-03-11 17:55:52 UTC (rev 11402)
+++ short/3D/PyLith/trunk/examples/twocells/twoquad4/dislocation_disp.spatialdb 2008-03-11 18:22:18 UTC (rev 11403)
@@ -1,44 +0,0 @@
-#SPATIAL.ascii 1
-
-// This database is used to specify the boundary conditions for the
-// dislocation (kinematic fault) example.
-
-// This follows the format for a Simple DB (the only type presently available).
-SimpleDB {
-
- // There are two values specified in the database, corresponding to the
- // constraint values for the x (dof-0) and y (dof-1) degrees of freedom.
- num-values = 2
- value-names = dof-0 dof-1
-
- // The constraint values (displacements) have units of meters.
- value-units = m m
-
- // The values are specified at two spatial locations.
- num-locs = 2
-
- // The dimension of the spatial distribution is 1, since the data
- // is being specified at points.
- data-dim = 1
-
- // The spatial dimension of the database is 2.
- space-dim = 2
-
- // We are specifying the data in a Cartesian coordinate system.
- cs-data = cartesian {
-
- // Our units are already in meters, so we can just multiply by one.
- to-meters = 1.0
-
- // We are using a 2D Cartesian coordinate system.
- space-dim = 2
- }
-}
-
-// This is where the data is specified.
-// As described in dislocation.cfg, this database will be used to specify
-// data along an edge (pylith.bc.BCFourSides).
-// The entries are:
-// X-coord, Y-coord, dof-0 (x constraint), dof-1 (y constraint).
--2.0 0.0 0.0 0.0
- 2.0 0.0 0.0 0.0
Modified: short/3D/PyLith/trunk/examples/twocells/twotet4/README
===================================================================
--- short/3D/PyLith/trunk/examples/twocells/twotet4/README 2008-03-11 17:55:52 UTC (rev 11402)
+++ short/3D/PyLith/trunk/examples/twocells/twotet4/README 2008-03-11 18:22:18 UTC (rev 11403)
@@ -25,13 +25,11 @@
2. dislocation: Fault displacements are applied between the two
elements, while the left and right corners are fixed in x, y, and z.
a. dislocation.cfg: Parameter settings for this problem.
- b. dislocation.spatialdb: Boundary condition database for this
+ b. dislocation_slip.spatialdb: Fault slip database for this problem.
+ c. dislocation_sliprate.spatialdb: Fault slip rate database for this
problem.
- c. dislocation_disp.spatialdb: Fault slip database for this problem.
- d. dislocation_sliprate.spatialdb: Fault slip rate database for this
+ d. dislocation_sliptime.spatialdb: Fault slip time database for this
problem.
- e. dislocation_sliptime.spatialdb: Fault slip time database for this
- problem.
All of the files are documented. The 'pylithapp.cfg' file is read
automatically when running PyLith. To add to or override these
@@ -40,5 +38,7 @@
pylith axialdisp.cfg
pylith dislocation.cfg
-Each of these commands will produce a corresponding VTK file, which may
+Each of these commands will produce a set of VTK files, which may
be viewed with visualization packages such as ParaView or Mayavi.
+The JPEG files in this directory show sample visualizations for these
+problems using ParaView.
Deleted: short/3D/PyLith/trunk/examples/twocells/twotet4/dislocation_disp.spatialdb
===================================================================
--- short/3D/PyLith/trunk/examples/twocells/twotet4/dislocation_disp.spatialdb 2008-03-11 17:55:52 UTC (rev 11402)
+++ short/3D/PyLith/trunk/examples/twocells/twotet4/dislocation_disp.spatialdb 2008-03-11 18:22:18 UTC (rev 11403)
@@ -1,44 +0,0 @@
-#SPATIAL.ascii 1
-
-// This database is used to specify the boundary conditions for the
-// dislocation (kinematic fault) example.
-
-// This follows the format for a Simple DB (the only type presently available).
-SimpleDB {
-
- // There are 3 values specified in the database, corresponding to the
- // constraint values for the x (dof-0), y (dof-1), and z (dof-2) degrees of
- // freedom.
- num-values = 3
- value-names = dof-0 dof-1 dof-2
-
- // The constraint values (displacements) have units of meters.
- value-units = m m m
-
- // The values are specified at one spatial location.
- num-locs = 1
-
- // The dimension of the spatial distribution is 0, since the data
- // is uniform over the mesh.
- data-dim = 0
-
- // The spatial dimension of the database is 3.
- space-dim = 3
-
- // We are specifying the data in a Cartesian coordinate system.
- cs-data = cartesian {
-
- // Our units are already in meters, so we can just multiply by one.
- to-meters = 1.0
-
- // We are using a 3D Cartesian coordinate system.
- space-dim = 3
- }
-}
-
-// This is where the data is specified.
-// As described in dislocation.cfg, this database will be used to specify
-// data along an edge (pylith.bc.BCFourSides).
-// The entries are:
-// X-coord, Y-coord, Z-coord, dof-0, dof-1, dof-2.
- 0.0 0.0 0.0 0.0 0.0 0.0
Deleted: short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/axialdisp.spatialdb
===================================================================
--- short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/axialdisp.spatialdb 2008-03-11 17:55:52 UTC (rev 11402)
+++ short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/axialdisp.spatialdb 2008-03-11 18:22:18 UTC (rev 11403)
@@ -1,48 +0,0 @@
-#SPATIAL.ascii 1
-
-// This database is used to specify the boundary conditions for the axial
-// displacement example.
-
-// This follows the format for a Simple DB (the only type presently available).
-SimpleDB {
-
- // There are 3 values specified in the database, corresponding to the
- // constraint values for the x (dof-0), y (dof-1) and z (dof-2) degrees of
- // freedom.
- num-values = 3
- value-names = dof-0 dof-1 dof-2
-
- // The constraint values (displacements) have units of meters.
- value-units = m m m
-
- // The values are specified at two spatial locations.
- num-locs = 2
-
- // The dimension of the spatial distribution is 1, since data is being
- // specified at points.
- data-dim = 1
-
- // The spatial dimension of the database is 3.
- space-dim = 3
-
- // We are specifying the data in a projected geographic coordinate system.
- cs-data = geo-projected {
- to-meters = 1.0
- ellipsoid = clrk66
- datum-horiz = NAD27
- datum-vert = mean sea level
- projector = projection {
- projection = utm
- units = m
- proj-options = +zone=11
- }
- }
-}
-
-// This is where the data is specified.
-// As described in axialdisp.cfg, this database will be used to specify
-// data at a point (pylith.bc.BCSingle).
-// The entries are:
-// X-coord, Y-coord, Z-coord, dof-0, dof-1, dof-2.
-499999.0 3.7e6 0.0 -0.01 0.0 0.0
-500001.0 3.7e6 0.0 0.01 0.0 0.0
Modified: short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation.cfg
===================================================================
--- short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation.cfg 2008-03-11 17:55:52 UTC (rev 11402)
+++ short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation.cfg 2008-03-11 18:22:18 UTC (rev 11403)
@@ -42,6 +42,9 @@
# Provide information on the boundary conditions.
[pylithapp.timedependent.bc.bc]
+# We use the default spatial database for the Dirichlet BC which sets
+# the displacements to zero for all time.
+
# We are fixing the 0 (x), 1 (y), and 2 (z) degrees of freedom.
fixed_dof = [0, 1, 2]
@@ -49,6 +52,9 @@
# 'end points' in the mesh file.
label = end points
+# We are assigning the label 'Dirichlet BC' to the database.
+db.label = Dirichlet BC
+
# ----------------------------------------------------------------------
# faults
# ----------------------------------------------------------------------
@@ -73,9 +79,17 @@
# material ID's are equal to 100.
# We need the material database for the fault to properly condition the
-# system of equations.
-mat_db.iohandler.filename = matprops.spatialdb
+# system of equations. This is using the same spatial database as used in
+# the computations.
+mat_db = spatialdata.spatialdb.SCECCVMH
+mat_db.data_dir = /home/brad/data/sceccvm-h/vx53/bin
+# Using this spatial database should give approximately the same results,
+# since the properties aren't that different from SCEC CVM-H.
+# matprops.spatialdb: lambda = mu = 30 GPa
+# SCEC CVM-H: lambda = 19.5 GPa, mu = 25.6 GPa
+# mat_db.iohandler.filename = matprops.spatialdb
+
# The quadrature for a 3D fault is 2D.
quadrature = pylith.feassemble.quadrature.Quadrature2Din3D
quadrature.cell.shape = triangle
Added: short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation.jpg
===================================================================
(Binary files differ)
Property changes on: short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation.jpg
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation_disp.spatialdb
===================================================================
--- short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation_disp.spatialdb 2008-03-11 17:55:52 UTC (rev 11402)
+++ short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation_disp.spatialdb 2008-03-11 18:22:18 UTC (rev 11403)
@@ -1,47 +0,0 @@
-#SPATIAL.ascii 1
-
-// This database is used to specify the boundary conditions for the
-// dislocation (kinematic fault) example.
-
-// This follows the format for a Simple DB (the only type presently available).
-SimpleDB {
-
- // There are 3 values specified in the database, corresponding to the
- // constraint values for the x (dof-0), y (dof-1), and z (dof-2) degrees of
- // freedom.
- num-values = 3
- value-names = dof-0 dof-1 dof-2
-
- // The constraint values (displacements) have units of meters.
- value-units = m m m
-
- // The values are specified at one spatial location.
- num-locs = 1
-
- // The dimension of the spatial distribution is 0, since the data
- // is uniform over the mesh.
- data-dim = 0
-
- // The spatial dimension of the database is 3.
- space-dim = 3
-
- // We are specifying the data in a projected geographic coordinate system.
- cs-data = geo-projected {
- to-meters = 1.0
- ellipsoid = clrk66
- datum-horiz = NAD27
- datum-vert = mean sea level
- projector = projection {
- projection = utm
- units = m
- proj-options = +zone=11
- }
- }
-}
-
-// This is where the data is specified.
-// As described in dislocation.cfg, this database will be used to specify
-// data along an edge (pylith.bc.BCFourSides).
-// The entries are:
-// X-coord, Y-coord, Z-coord, dof-0, dof-1, dof-2.
- 500000.0 3.7e6 0.0 0.0 0.0 0.0
Modified: short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation_slip.spatialdb
===================================================================
--- short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation_slip.spatialdb 2008-03-11 17:55:52 UTC (rev 11402)
+++ short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation_slip.spatialdb 2008-03-11 18:22:18 UTC (rev 11403)
@@ -16,8 +16,8 @@
// The values are specified at one spatial location.
num-locs = 3
- // The dimension of the spatial distribution is 2, since the same data
- // is specified on a plane.
+ // The dimension of the spatial distribution is 1, since the data is
+ // specified at points.
data-dim = 1
// The spatial dimension of the database is 3.
@@ -39,7 +39,7 @@
// This is where the data is specified.
// As described in dislocation.cfg, this database will be used to specify
-// varying data for a fault (pylith.faults.SingleFault).
+// varying data for a fault.
// The entries are:
// X-Coord, Y-Coord, Z-Coord, left-lateral slip, reverse-slip, fault-opening slip
500000.0 3699900.0 -100.0 0.01 0.0 0.0
Modified: short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation_sliprate.spatialdb
===================================================================
--- short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation_sliprate.spatialdb 2008-03-11 17:55:52 UTC (rev 11402)
+++ short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation_sliprate.spatialdb 2008-03-11 18:22:18 UTC (rev 11403)
@@ -38,7 +38,7 @@
// This is where the data is specified.
// As described in dislocation.cfg, this database will be used to specify
-// uniform data for a fault (pylith.faults.SingleFault).
+// uniform data for a fault.
// The entries are:
// X-Coord, Y-Coord, Z-Coord, slip rate
500000.0 3.7e6 0.0 1.0e+6
Modified: short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation_sliptime.spatialdb
===================================================================
--- short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation_sliptime.spatialdb 2008-03-11 17:55:52 UTC (rev 11402)
+++ short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/dislocation_sliptime.spatialdb 2008-03-11 18:22:18 UTC (rev 11403)
@@ -38,7 +38,7 @@
// This is where the data is specified.
// As described in dislocation.cfg, this database will be used to specify
-// uniform data for a fault (pylith.faults.SingleFault).
+// uniform data for a fault.
// The entries are:
// X-Coord, Y-Coord, Z-Coord, slip time
500000.0 3.7e6 0.0 -1.0
Modified: short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/pylithapp.cfg
===================================================================
--- short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/pylithapp.cfg 2008-03-11 17:55:52 UTC (rev 11402)
+++ short/3D/PyLith/trunk/examples/twocells/twotet4-geoproj/pylithapp.cfg 2008-03-11 18:22:18 UTC (rev 11403)
@@ -95,7 +95,7 @@
# ----------------------------------------------------------------------
[pylithapp.petsc]
pc_type = jacobi
-ksp_rtol = 1.0e-8
+ksp_rtol = 1.0e-10
ksp_monitor = true
ksp_view = true
log_summary = true
Modified: short/3D/PyLith/trunk/examples/twocells/twotri3/README
===================================================================
--- short/3D/PyLith/trunk/examples/twocells/twotri3/README 2008-03-11 17:55:52 UTC (rev 11402)
+++ short/3D/PyLith/trunk/examples/twocells/twotri3/README 2008-03-11 18:22:18 UTC (rev 11403)
@@ -39,8 +39,7 @@
the lower left and upper right corners are fixed in x and y.
- dislocation.cfg: Parameter settings.
- - dislocation.spatialdb: Database with Dirichlet BC values.
- - dislocation_disp.spatialdb: Database with fault slip values.
+ - dislocation_slip.spatialdb: Database with fault slip values.
- dislocation_sliprate.spatialdb: Database with peak slip rate values.
- dislocation_sliptime.spatialdb: Database with slip initiation time
values.
Deleted: short/3D/PyLith/trunk/examples/twocells/twotri3/dislocation_disp.spatialdb
===================================================================
--- short/3D/PyLith/trunk/examples/twocells/twotri3/dislocation_disp.spatialdb 2008-03-11 17:55:52 UTC (rev 11402)
+++ short/3D/PyLith/trunk/examples/twocells/twotri3/dislocation_disp.spatialdb 2008-03-11 18:22:18 UTC (rev 11403)
@@ -1,43 +0,0 @@
-#SPATIAL.ascii 1
-
-// This database is used to specify the boundary conditions for the
-// dislocation (kinematic fault) example.
-
-// This follows the format for a Simple DB (the only type presently available).
-SimpleDB {
-
- // There are two values specified in the database, corresponding to the
- // constraint values for the x (dof-0) and y (dof-1) degrees of freedom.
- num-values = 2
- value-names = dof-0 dof-1
-
- // The constraint values (displacements) have units of meters.
- value-units = m m
-
- // The values are specified at one spatial location.
- num-locs = 1
-
- // The dimension of the spatial distribution is 0, since the same data
- // is specified for all points in the set.
- data-dim = 0
-
- // The spatial dimension of the database is 2.
- space-dim = 2
-
- // We are specifying the data in a Cartesian coordinate system.
- cs-data = cartesian {
-
- // Our units are already in meters, so we can just multiply by one.
- to-meters = 1.0
-
- // We are using a 2D Cartesian coordinate system.
- space-dim = 2
- }
-}
-
-// This is where the data is specified.
-// As described in dislocation.cfg, this database will be used to specify
-// data at a point (pylith.bc.BCSingle).
-// The entries are:
-// X-coord, Y-coord, dof-0 (x constraint), dof-1 (y constraint).
-0.0 0.0 0.0 0.0
More information about the cig-commits
mailing list