[cig-commits] r11456 - in short/3D/PyLith/trunk/doc/userguide: boundaryconditions runpylith tutorials/twohex8 tutorials/twotet4-geoproj
sue at geodynamics.org
sue at geodynamics.org
Mon Mar 17 11:24:16 PDT 2008
Author: sue
Date: 2008-03-17 11:24:16 -0700 (Mon, 17 Mar 2008)
New Revision: 11456
Modified:
short/3D/PyLith/trunk/doc/userguide/boundaryconditions/boundaryconditions.lyx
short/3D/PyLith/trunk/doc/userguide/runpylith/runpylith.lyx
short/3D/PyLith/trunk/doc/userguide/tutorials/twohex8/twohex8.lyx
short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4-geoproj/twotet4-geoproj.lyx
Log:
minor edits
Modified: short/3D/PyLith/trunk/doc/userguide/boundaryconditions/boundaryconditions.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/boundaryconditions/boundaryconditions.lyx 2008-03-17 13:55:19 UTC (rev 11455)
+++ short/3D/PyLith/trunk/doc/userguide/boundaryconditions/boundaryconditions.lyx 2008-03-17 18:24:16 UTC (rev 11456)
@@ -1,4 +1,4 @@
-#LyX 1.5.2 created this file. For more info see http://www.lyx.org/
+#LyX 1.5.1 created this file. For more info see http://www.lyx.org/
\lyxformat 276
\begin_document
\begin_header
@@ -128,8 +128,8 @@
are no longer available (or necessary).
The default boundary condition for each component in the array is the Dirichlet
Points object.
- Other boundary conditions can be bound to the names itesm in the array
- via a .cfg file, .pml file, or the command line.
+ Other boundary conditions can be bound to the names item in the array via
+ a .cfg file, .pml file, or the command line.
The parameters for the boundary condition are set using the name of the
boundary condition.
An example of setting the array of boundary condition components and changing
@@ -180,7 +180,7 @@
\begin_inset Formula $u_{o}$
\end_inset
-is the prescribed displacement at time
+ is the prescribed displacement at time
\begin_inset Formula $t_{ref}$
\end_inset
@@ -344,7 +344,7 @@
For the rate of change of values, we use the FixedDOFDB (which is a special
case of the UniformDB) and specify the velocity in the z-direction to be
1.0e-06 m/s.
- See section
+ See Section
\begin_inset LatexCommand ref
reference "sec:spatial:databases"
@@ -527,7 +527,7 @@
the surface, using values from a spatial database.
The tractions are integrated over each cell and assembled to obtain the
forces applied at the vertices.
- See section
+ See Section
\begin_inset LatexCommand ref
reference "sub:Tutorial-twoquad4-traction"
@@ -658,7 +658,7 @@
\end_layout
\begin_layout Standard
-These settings correspond to the example problem described in section
+These settings correspond to the example problem described in Section
\begin_inset LatexCommand ref
reference "sub:Tutorial-twoquad4-traction"
@@ -765,11 +765,11 @@
waves.
If the waves arriving at the absorbing boundary are relatively small in
amplitude compared to the amplitudes of primary interest, this boundary
- condition gives reasonable results.Neumann Boundary Condition Parameters
+ condition gives reasonable results.
\end_layout
\begin_layout Standard
-The Neumann boundary condition properties and components are:
+The Absorbing boundary condition properties and components are:
\end_layout
\begin_layout Description
@@ -1031,7 +1031,7 @@
\end_layout
\begin_layout Standard
-Fault interfaces are used to create dislocations (jumps in displacement
+Fault interfaces are used to create dislocations (jumps in the displacement
field) in the model.
The dislocations arise from slip across a fault surface.
Both shear and tensile dislocations are supported.
@@ -1203,7 +1203,7 @@
\begin_layout Standard
\align center
\begin_inset Graphics
- filename /Users/brad/src/cig/pylith/doc/userguide/boundaryconditions/figs/quad4cohesive.eps
+ filename figs/quad4cohesive.eps
\end_inset
@@ -1248,7 +1248,7 @@
\begin_layout Standard
\align center
\begin_inset Graphics
- filename /Users/brad/src/cig/pylith/doc/userguide/boundaryconditions/figs/quad4cohesivekin.eps
+ filename figs/quad4cohesivekin.eps
\end_inset
Modified: short/3D/PyLith/trunk/doc/userguide/runpylith/runpylith.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/runpylith/runpylith.lyx 2008-03-17 13:55:19 UTC (rev 11455)
+++ short/3D/PyLith/trunk/doc/userguide/runpylith/runpylith.lyx 2008-03-17 18:24:16 UTC (rev 11456)
@@ -1,4 +1,4 @@
-#LyX 1.5.3 created this file. For more info see http://www.lyx.org/
+#LyX 1.5.1 created this file. For more info see http://www.lyx.org/
\lyxformat 276
\begin_document
\begin_header
@@ -1603,7 +1603,7 @@
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
+ See Section
\begin_inset LatexCommand ref
reference "sec:Tutorial-Two-tet4-geoproj"
Modified: short/3D/PyLith/trunk/doc/userguide/tutorials/twohex8/twohex8.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/tutorials/twohex8/twohex8.lyx 2008-03-17 13:55:19 UTC (rev 11455)
+++ short/3D/PyLith/trunk/doc/userguide/tutorials/twohex8/twohex8.lyx 2008-03-17 18:24:16 UTC (rev 11456)
@@ -84,7 +84,7 @@
\end_layout
\begin_layout Itemize
-Trilinear hexaahedral cells
+Trilinear hexahedral cells
\end_layout
\begin_layout Itemize
@@ -431,9 +431,10 @@
\begin_layout Description
pylithapp.timedependent.materials.material.output Defines the filter to be used
- when writing cell state variables (average over the quadrature points of the
- cell), gives the base filename for state variable output files, and defines
- the format to use when defining the output filenames for each time step.
+ when writing cell state variables (average over the quadrature points of
+ the cell), gives the base filename for state variable output files, and
+ defines the format to use when defining the output filenames for each time
+ step.
\end_layout
\begin_layout Standard
@@ -446,7 +447,7 @@
axialdisp.cfg
\family default
.
- Since data is being specified using two control points (rather than being
+ Since data are being specified using two control points (rather than being
uniform over the mesh, for example), the data dimension is one.
\end_layout
@@ -661,9 +662,10 @@
\begin_layout Description
pylithapp.timedependent.materials.material.output Defines the filter to be used
- when writing cell state variables (average over the quadrature points of the
- cell), gives the base filename for state variable output files, and defines
- the format to use when defining the output filenames for each time step.
+ when writing cell state variables (average over the quadrature points of
+ the cell), gives the base filename for state variable output files, and
+ defines the format to use when defining the output filenames for each time
+ step.
\end_layout
\begin_layout Standard
@@ -676,8 +678,8 @@
sheardisp.cfg
\family default
.
- Data is being specified at two control points (rather than being uniform over
- the mesh, for example), so the data dimension is one.
+ Data are being specified at two control points (rather than being uniform
+ over the mesh, for example), so the data dimension is one.
\end_layout
\begin_layout Standard
@@ -923,15 +925,16 @@
dislocation_slip.spatialdb
\family default
) specifies 0.01 m of left-lateral fault slip for the entire fault.
- The data dimension is zero since the same data is applied to all points
+ The data dimension is zero since the same data are applied to all points
in the set.
- 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 creates a step function for the slip time history.
+ The peak slip rate of 1.0e6 m/s creates 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$
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 13:55:19 UTC (rev 11455)
+++ short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4-geoproj/twotet4-geoproj.lyx 2008-03-17 18:24:16 UTC (rev 11456)
@@ -1,4 +1,4 @@
-#LyX 1.5.3 created this file. For more info see http://www.lyx.org/
+#LyX 1.5.1 created this file. For more info see http://www.lyx.org/
\lyxformat 276
\begin_document
\begin_header
@@ -114,7 +114,7 @@
).
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
+ (described in Section
\begin_inset LatexCommand ref
reference "sub:SCECCVMH-Impl"
@@ -137,7 +137,7 @@
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
+ the coordinate system are identical to the examples in Section
\begin_inset LatexCommand ref
reference "sec:Tutorial-Two-tet4"
@@ -187,8 +187,13 @@
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.
+ See Appendix
+\begin_inset LatexCommand ref
+reference "sec:Spatialdata:SimpleIOAscii"
+
+\end_inset
+
+ for other examples of using geographic coordinates.
\end_layout
@@ -555,7 +560,7 @@
\end_layout
\begin_layout Standard
- Recall that we condition problems with the kinematic fault interface using
+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.
More information about the cig-commits
mailing list