[cig-commits] r15285 - in short/3D/PyLith/trunk/doc/userguide: boundaryconditions materials runpylith
sue at geodynamics.org
sue at geodynamics.org
Mon Jun 15 16:40:01 PDT 2009
Author: sue
Date: 2009-06-15 16:40:01 -0700 (Mon, 15 Jun 2009)
New Revision: 15285
Modified:
short/3D/PyLith/trunk/doc/userguide/boundaryconditions/boundaryconditions.lyx
short/3D/PyLith/trunk/doc/userguide/materials/materials.lyx
short/3D/PyLith/trunk/doc/userguide/runpylith/runpylith.lyx
Log:
typos fixed, pt. 1
Modified: short/3D/PyLith/trunk/doc/userguide/boundaryconditions/boundaryconditions.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/boundaryconditions/boundaryconditions.lyx 2009-06-15 23:33:56 UTC (rev 15284)
+++ short/3D/PyLith/trunk/doc/userguide/boundaryconditions/boundaryconditions.lyx 2009-06-15 23:40:01 UTC (rev 15285)
@@ -231,7 +231,7 @@
of a value in time.
One can specify just the initial value, just the rate of change of the
value (along with the corresponding onset time), or just the modulation
- in amplitude (along withthe corresponding temporal variation and onset
+ in amplitude (along with the corresponding temporal variation and onset
time), or any combination of the three.
The facilities associated with this formulation are:
\end_layout
@@ -303,23 +303,8 @@
\begin_layout Standard
By default the output manager does not output any information.
- The specified displacements and velocities can be output by including
-\begin_inset Quotes eld
-\end_inset
-
-displacements
-\begin_inset Quotes erd
-\end_inset
-
- and
-\begin_inset Quotes eld
-\end_inset
-
-velocities
-\begin_inset Quotes erd
-\end_inset
-
- in the output manager's
+ The specified displacements and velocities can be output by including ``displac
+ements'' and ``velocities'' in the output manager's
\family typewriter
vertex_info_fields
\family default
@@ -857,15 +842,7 @@
\begin_layout Standard
By default the output manager does not output any information.
The specified tractions can be output in global coordinates by including
-
-\begin_inset Quotes eld
-\end_inset
-
-tractions
-\begin_inset Quotes erd
-\end_inset
-
- in the output manager's
+ ``tractions'' in the output manager's
\family typewriter
cell_info_fields
\family default
Modified: short/3D/PyLith/trunk/doc/userguide/materials/materials.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/materials/materials.lyx 2009-06-15 23:33:56 UTC (rev 15284)
+++ short/3D/PyLith/trunk/doc/userguide/materials/materials.lyx 2009-06-15 23:40:01 UTC (rev 15285)
@@ -3419,8 +3419,8 @@
\begin_inset Caption
\begin_layout Plain Layout
-Values in spatial database for initial state variables for 3-D problems.
- 2-D problems use only the relevant values.
+Values in spatial database for initial state variables for 3D problems.
+ 2D problems use only the relevant values.
\end_layout
\end_inset
Modified: short/3D/PyLith/trunk/doc/userguide/runpylith/runpylith.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/runpylith/runpylith.lyx 2009-06-15 23:33:56 UTC (rev 15284)
+++ short/3D/PyLith/trunk/doc/userguide/runpylith/runpylith.lyx 2009-06-15 23:40:01 UTC (rev 15285)
@@ -131,13 +131,13 @@
\end_layout
\begin_layout Standard
-The parameters for PyLith are specified as a hiearchy or tree of modules.
- The application assembles the hiearchy of modules from user input and then
- calls the main function in the top-level module in the same manner as a
- C or C++ program.
+The parameters for PyLith are specified as a hierarchy or tree of modules.
+ The application assembles the hierarchy of modules from user input and
+ then calls the main function in the top-level module in the same manner
+ as a C or C++ program.
The behavior of the application is determined by the modules included in
- the hiearchy as specified by the user.
- The Pyre framework provides the interface for defining this hiearchy.
+ the hierarchy as specified by the user.
+ The Pyre framework provides the interface for defining this hierarchy.
Pyre properties correspond to simple settings in the form of strings, integers,
and real numbers.
Pyre facilities correspond to software modules.
@@ -172,8 +172,7 @@
\family typewriter
problem
\family default
- specifies the physical properties, boundary conditions, etc.
- and
+ specifies the physical properties, boundary conditions, etc., and
\family typewriter
petsc
\family default
@@ -217,9 +216,9 @@
All dimensional parameters require units.
The units are specified using Python and Fortran syntax, so square meters
is m**2.
- Whitespace is not allowed in the string for units and dimensioned quantities
- are multiplied by the units string, for example two meters per second is
- 2.0*m/s.
+ Whitespace is not allowed in the string, for units and dimensioned quantities
+ are multiplied by the units string; for example, two meters per second
+ is 2.0*m/s.
\end_layout
\begin_layout Subsubsection
@@ -699,7 +698,7 @@
\noindent
\align center
\begin_inset Graphics
- filename /Users/brad/src/cig/pylith/doc/userguide/runpylith/figs/bar2.eps
+ filename figs/bar2.eps
\end_inset
@@ -746,7 +745,7 @@
\noindent
\align center
\begin_inset Graphics
- filename /Users/brad/src/cig/pylith/doc/userguide/runpylith/figs/tri3.eps
+ filename figs/tri3.eps
\end_inset
@@ -828,7 +827,7 @@
\begin_inset Graphics
- filename /Users/brad/src/cig/pylith/doc/userguide/runpylith/figs/quad4.eps
+ filename figs/quad4.eps
\end_inset
@@ -876,7 +875,7 @@
\noindent
\align center
\begin_inset Graphics
- filename /Users/brad/src/cig/pylith/doc/userguide/runpylith/figs/tet4.eps
+ filename figs/tet4.eps
\end_inset
@@ -958,7 +957,7 @@
\begin_inset Graphics
- filename /Users/brad/src/cig/pylith/doc/userguide/runpylith/figs/hex8.eps
+ filename figs/hex8.eps
\end_inset
@@ -1000,8 +999,8 @@
\begin_layout Standard
The problem component specifies the basic parameters of the simulation,
- including the physical properties, the boundary conditions, interface condition
-s (faults).
+ including the physical properties, the boundary conditions, and interface
+ conditions (faults).
The current release of PyLith contains one type of problem,
\family typewriter
TimeDependent
@@ -1799,7 +1798,7 @@
\end_layout
\begin_layout Standard
-The explicit and implicit ime stepping formulations use a common set of
+The explicit and implicit time stepping formulations use a common set of
facilities and properties.
The facilities include
\end_layout
@@ -1809,7 +1808,7 @@
\end_layout
\begin_layout Description
-solver Type of solver to use (default is linear)
+solver Type of solver to use (default is linear).
\end_layout
\begin_layout Description
@@ -1838,7 +1837,7 @@
\begin_layout Description
split_fields Split solution field into a displacement portion (field 0)
and a Lagrange multiplier portion (field 1) to permit application of sophistica
-ted PETSc preconditions (default is false, for expert users only).
+ted PETSc preconditions (default is false; for expert users only).
\end_layout
\begin_layout Standard
@@ -1902,7 +1901,7 @@
\color inherit
Changing the time step requires recomputing the Jacobian of the system,
- which can greatly increase the runtime if the time step size changes frequently.
+ which can greatly increase the runtime if the time-step size changes frequently.
\end_layout
\begin_layout Subsubsection
@@ -1913,7 +1912,7 @@
With a uniform, user-specified time step, the user selects the time step
that is used over the entire duration of the simulation.
This value is used whether or not it yields a stable solution, so users
- should be careful when selecting the time step value.
+ should be careful when selecting the time-step value.
The properties for the uniform, user-specified time step are:
\end_layout
@@ -1962,7 +1961,7 @@
\end_layout
\begin_layout Standard
-The nonuniform, user-specified time step implementation allows the user
+The nonuniform, user-specified, time-step implementation allows the user
to specify the time steps in an ASCII file (see Section
\begin_inset CommandInset ref
LatexCommand ref
@@ -1970,7 +1969,7 @@
\end_inset
- for the format specification of the time step file).
+ for the format specification of the time-step file).
If the total duration exceeds the time associated with the time steps,
then a flag determines whether to cycle through the time steps or to use
the last specified time step for the time remaining.
@@ -1982,12 +1981,12 @@
\end_layout
\begin_layout Description
-filename Name of file with time step sizes.
+filename Name of file with time-step sizes.
\end_layout
\begin_layout Description
loop_steps If true, cycle through time steps, otherwise keep using last
- time step size for any time remaining
+ time-step size for any time remaining.
\end_layout
\begin_layout Standard
@@ -2032,16 +2031,16 @@
\end_layout
\begin_layout Standard
-This time step implementation automatically calculates a stable time step
+This time-step implementation automatically calculates a stable time step
based on the constitutive model and rate of deformation.
As a result, this choice for choosing the time step relies on accurate
calculation of a stable time step within each finite-element cell by the
constitutive models.
- In order to provide some control over the time step selection, the user
+ In order to provide some control over the time-step selection, the user
can control the frequency that a new time step is calculated, the time
step to use relative to the value determined by the constitutive models,
and a maximum value for the time step.
- The properties for controlling the automatic time step selection are:
+ The properties for controlling the automatic time-step selection are:
\end_layout
\begin_layout Description
@@ -2775,7 +2774,7 @@
LaGriT (itetclr) and CUBIT (block id).
The id also tags the cells in the mesh for associating cells with a specific
material model and quadrature rule.
- For boundary conditions the ``label'' is a string used to associate groups
+ For boundary conditions, the ``label'' is a string used to associate groups
of vertices (psets in LaGriT and nodesets in CUBIT) with a boundary condition.
Note that some mesh generators use strings (LaGriT) to identify groups
of nodes while others use integers (CUBIT Exodus files).
@@ -2783,15 +2782,8 @@
in the Exodus files, so we must rely on the nodeset ID.
PyLith 1.0 had an ``id'' for boundary conditions, but we removed it from
subsequent releases because it was not used.
- For faults the ``label'' is used in the same manner as the
-\begin_inset Quotes eld
-\end_inset
-
-label
-\begin_inset Quotes erd
-\end_inset
-
- for boundary conditions.
+ For faults the ``label'' is used in the same manner as the ``label'' for
+ boundary conditions.
That is, it associates a string with a group of vertices (pset in LaGriT
and nodeset in CUBIT).
The fault ``id'' is a integer used to tag the cohesive cells in the mesh
More information about the CIG-COMMITS
mailing list