[cig-commits] r11455 - in short/3D/PyLith/trunk/doc/userguide: runpylith tutorials tutorials/twoquad4 tutorials/twotet4-geoproj
willic3 at geodynamics.org
willic3 at geodynamics.org
Mon Mar 17 06:55:20 PDT 2008
Author: willic3
Date: 2008-03-17 06:55:19 -0700 (Mon, 17 Mar 2008)
New Revision: 11455
Modified:
short/3D/PyLith/trunk/doc/userguide/runpylith/runpylith.lyx
short/3D/PyLith/trunk/doc/userguide/tutorials/tutorials.lyx
short/3D/PyLith/trunk/doc/userguide/tutorials/twoquad4/twoquad4.lyx
short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4-geoproj/twotet4-geoproj.lyx
Log:
Minor edits, fixed some cross-referencing, and edited lists of concepts for
some tutorials.
Modified: short/3D/PyLith/trunk/doc/userguide/runpylith/runpylith.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/runpylith/runpylith.lyx 2008-03-17 03:33:15 UTC (rev 11454)
+++ short/3D/PyLith/trunk/doc/userguide/runpylith/runpylith.lyx 2008-03-17 13:55:19 UTC (rev 11455)
@@ -1,4 +1,4 @@
-#LyX 1.5.2 created this file. For more info see http://www.lyx.org/
+#LyX 1.5.3 created this file. For more info see http://www.lyx.org/
\lyxformat 276
\begin_document
\begin_header
@@ -1065,8 +1065,8 @@
\end_layout
\begin_layout Standard
-The mesh information defines the vertex coordinates as well as specifies
- the vertices composing each cell in the mesh.
+The mesh information defines the vertex coordinates and specifies the vertices
+ composing each cell in the mesh.
The mesh information must also define at least one set of vertices for
which displacement (Dirichlet) boundary conditions will be provided.
In most realistic problems, there will be several vertex groups, each with
@@ -1563,7 +1563,7 @@
\end_layout
\begin_layout Standard
-Specify the physical properties of a linearly elastic, isotropicmaterial
+Specify the physical properties of a linearly elastic, isotropic material
in a
\family typewriter
pylithapp.cfg
@@ -1603,8 +1603,14 @@
One such database is the SCEC CVM-H database, which provides seismic velocities
and density information for much of southern California.
Spatialdata provides a direct interface to this database.
- See Tutorial TODO:?? for an example of using the SCEC CVM-H database for
- physical properties of an elastic material.
+ See
+\begin_inset LatexCommand ref
+reference "sec:Tutorial-Two-tet4-geoproj"
+
+\end_inset
+
+ for an example of using the SCEC CVM-H database for physical properties
+ of an elastic material.
The interface is known to work with versions 5.2 and 5.3 of the SCEC CVM-H.
The Pyre properties for the SCEC CVM-H are:
\end_layout
@@ -1628,7 +1634,7 @@
\end_layout
\begin_layout Standard
-Specify the physical properties of a linearly elastic, isotropicmaterial
+Specify the physical properties of a linearly elastic, isotropic material
using the SCEC CVM-H in a
\family typewriter
pylithapp.cfg
Modified: short/3D/PyLith/trunk/doc/userguide/tutorials/tutorials.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/tutorials/tutorials.lyx 2008-03-17 03:33:15 UTC (rev 11454)
+++ short/3D/PyLith/trunk/doc/userguide/tutorials/tutorials.lyx 2008-03-17 13:55:19 UTC (rev 11455)
@@ -1,4 +1,4 @@
-#LyX 1.5.2 created this file. For more info see http://www.lyx.org/
+#LyX 1.5.3 created this file. For more info see http://www.lyx.org/
\lyxformat 276
\begin_document
\begin_header
Modified: short/3D/PyLith/trunk/doc/userguide/tutorials/twoquad4/twoquad4.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/tutorials/twoquad4/twoquad4.lyx 2008-03-17 03:33:15 UTC (rev 11454)
+++ short/3D/PyLith/trunk/doc/userguide/tutorials/twoquad4/twoquad4.lyx 2008-03-17 13:55:19 UTC (rev 11455)
@@ -1,4 +1,4 @@
-#LyX 1.5.2 created this file. For more info see http://www.lyx.org/
+#LyX 1.5.3 created this file. For more info see http://www.lyx.org/
\lyxformat 276
\begin_document
\begin_header
@@ -72,6 +72,10 @@
\end_layout
\begin_layout Itemize
+Neumann boundary conditions
+\end_layout
+
+\begin_layout Itemize
Kinematic fault interface conditions
\end_layout
@@ -229,8 +233,8 @@
\begin_layout Description
pylithapp.timedependent.materials Settings that control the material type,
specify which material IDs are to be associated with a particular material
- type, and give the name of the spatial database containing physical properties
- for the material.
+ type, and give the name of the spatial database containing physical properties
+ for the material.
The quadrature information is also given.
\end_layout
Modified: short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4-geoproj/twotet4-geoproj.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4-geoproj/twotet4-geoproj.lyx 2008-03-17 03:33:15 UTC (rev 11454)
+++ short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4-geoproj/twotet4-geoproj.lyx 2008-03-17 13:55:19 UTC (rev 11455)
@@ -1,4 +1,4 @@
-#LyX 1.5.1 created this file. For more info see http://www.lyx.org/
+#LyX 1.5.3 created this file. For more info see http://www.lyx.org/
\lyxformat 276
\begin_document
\begin_header
@@ -52,8 +52,7 @@
\end_inset
-Tutorial Using Two Tetrahedra with Georeferenced Coordinate Systems
-ted Mesh
+Tutorial Using Two Tetrahedra with Georeferenced Coordinate System Mesh
\end_layout
\begin_layout Standard
@@ -93,6 +92,10 @@
\end_layout
\begin_layout Itemize
+SCEC CVM-H spatial database
+\end_layout
+
+\begin_layout Itemize
FixedDOFDB spatial database
\end_layout
@@ -110,34 +113,34 @@
).
The primary difference is in how the material properties are assigned.
- For this tutorial, the physical properties come from the SCEC CVM-H database (described in
+ For this tutorial, the physical properties come from the SCEC CVM-H database
+ (described in
\begin_inset LatexCommand ref
reference "sub:SCECCVMH-Impl"
\end_inset
+
).
- Using the SCEC SVM-H database is straightforward, requiring
- only a few modifications to
+ Using the SCEC SVM-H database is straightforward, requiring only a few
+ modifications to
\family typewriter
pylithapp.cfg
\family default
.
+ Because the SCEC CVM-H database uses geographic coordinates, we must also
+ use geographic coordinates in the PyLith mesh ASCII file and other spatial
+ databases.
+ Note that all of these geographic coordinate systems do not need to be
+ the same.
+ PyLith will automatically transform from one geographic coordinate system
+ to another using the spatialdata package.
+ The spatial databases should all use a Cartesian coordinate system, such
+ as a geographic projection to insure interpolation is performed properly.
+ Since all aspects of this problem other than the material database and
+ the coordinate system are identical to the examples in
+\begin_inset LatexCommand ref
+reference "sec:Tutorial-Two-tet4"
- Because the SCEC CVM-H database uses geographic coordinates, we must
- also use geographic coordinates in the PyLith mesh ASCII file and
- other spatial databases.
- Note that all of these geographic coordinate
- systems do not need to be the same. PyLith will automatically
- transform from one geographic coordinate system to another using the
- spatialdata package.
- The spatial databases should all use a Cartesian
- coordinate system, such as a geographic projection to insure
- interpolation is performed properly.
- Since all aspects of this
- problem other than the material database and the coordinate system
- are identical to the examples in \begin_inset LatexCommand ref
- reference "sec:Tutorial-Two-tet4"
-
\end_inset
, we only describe the kinematic fault problem in this tutorial.
@@ -178,15 +181,16 @@
\end_inset
-, you will notice that, although the mesh topology is the same, the
- vertex coordinates are significantly different.
- We use zone 11 UTM
- coordinates with the NAD27 datum for the mesh.
- Although we used the
- same coordinate system as the SCEC CVM-H, we could have also used any
- another geographic projection supported by spatialdata and Proj.4.
- See appendix SPATIALDATA FILE FORMAT for other examples of using geographic coordinates.
- \end_layout
+, you will notice that, although the mesh topology is the same, the vertex
+ coordinates are significantly different.
+ We use zone 11 UTM coordinates with the NAD27 datum for the mesh.
+ Although we used the same coordinate system as the SCEC CVM-H, we could
+ have also used any another geographic projection supported by spatialdata
+ and Proj.4.
+ See appendix SPATIALDATA FILE FORMAT for other examples of using geographic
+ coordinates.
+
+\end_layout
\begin_layout Standard
\noindent
@@ -551,12 +555,15 @@
\end_layout
\begin_layout Standard
- Recall that we condition problems with the kinematic fault interface using the material properties. Since the material properties are being defined using the SCEC CVM-H database,
- this same database should be used as the material database for the faults. This also applies to the AbsorbingDampers boundary condition.
+ Recall that we condition problems with the kinematic fault interface using
+ the material properties.
+ Since the material properties are being defined using the SCEC CVM-H database,
+ this same database should be used as the material database for the faults.
+ This also applies to the AbsorbingDampers boundary condition.
+\end_layout
\begin_layout Standard
-The fault example requires three additional database files that were not
- needed for the simple displacement examples.
+The fault example requires three additional database files.
The first file (
\family typewriter
dislocation_slip.spatialdb
@@ -564,13 +571,14 @@
) specifies 0.01 m of left-lateral fault slip for the entire fault.
Since we specify a different amount of slip for every vertex on the fault,
the data dimension is one.
- It is also necessary to specify the peak slip rate, which is done in the file
-
+ It is also necessary to specify the peak slip rate, which is done in the
+ file
\family typewriter
dislocation_sliprate.spatialdb
\family default
.
- The peak slip rate of 1.0e6 m/s generates a step-function for the slip time history.
+ The peak slip rate of 1.0e6 m/s generates a step-function for the slip time
+ history.
Finally, we must provide the time at which slip begins.
The elastic solution begins at
\begin_inset Formula $t=-dt$
@@ -611,9 +619,7 @@
\family default
,
\family typewriter
-dislocation_
-\newline
-sliptime.spatialdb
+dislocation_sliptime.spatialdb
\family default
\size default
) provide a complete description of the problem, and we can then run this
More information about the cig-commits
mailing list