[cig-commits] r7465 - in short/3D/PyLith/trunk/doc/userguide: .
boundaryconditions fileformats governingeqns install intro
materials runpylith tutorials tutorials/twotet4
tutorials/twotet4/figs
brad at geodynamics.org
brad at geodynamics.org
Mon Jun 25 00:54:55 PDT 2007
Author: brad
Date: 2007-06-25 00:54:54 -0700 (Mon, 25 Jun 2007)
New Revision: 7465
Removed:
short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4/figs/tetmesh.jpg
Modified:
short/3D/PyLith/trunk/doc/userguide/boundaryconditions/boundaryconditions.lyx
short/3D/PyLith/trunk/doc/userguide/fileformats/fileformats.lyx
short/3D/PyLith/trunk/doc/userguide/governingeqns/governingeqns.lyx
short/3D/PyLith/trunk/doc/userguide/install/install.lyx
short/3D/PyLith/trunk/doc/userguide/intro/intro.lyx
short/3D/PyLith/trunk/doc/userguide/materials/materials.lyx
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/twotet4/figs/twotet4-mesh.eps
short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4/figs/twotet4-mesh.fig
short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4/twotet4.lyx
short/3D/PyLith/trunk/doc/userguide/userguide.lyx
Log:
Some general editing to the manual. Fixed figure for the twotet4 mesh. Added section on spatial database parameters.
Modified: short/3D/PyLith/trunk/doc/userguide/boundaryconditions/boundaryconditions.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/boundaryconditions/boundaryconditions.lyx 2007-06-25 06:58:19 UTC (rev 7464)
+++ short/3D/PyLith/trunk/doc/userguide/boundaryconditions/boundaryconditions.lyx 2007-06-25 07:54:54 UTC (rev 7465)
@@ -343,8 +343,8 @@
\end_layout
\begin_layout Standard
-Dirichlet boundary conditions prescribe a fixed value of slip at vertices
- of the finite-element mesh.
+Dirichlet boundary conditions prescribe a fixed value of displacement on
+ a subset of the vertices of the finite-element mesh.
While Dirichlet boundary conditions can be applied to any vertex, usually
they are applied to vertices on the lateral and bottom boundaries of the
domain.
@@ -363,7 +363,7 @@
\begin_layout Description
id This is an integer identifier for the boundary condition.
- It is not used in the current implementation.
+ It is not used in the current implementation and may be ommitted.
\end_layout
\begin_layout Description
@@ -423,8 +423,11 @@
\end_layout
\begin_layout Standard
-where we have specified that we want to use the BCTwoSides boundary condition
- container, the group of vertices has the label
+where we have specified that we want to use the
+\family typewriter
+BCTwoSides
+\family default
+ boundary condition container, the group of vertices has the label
\begin_inset Quotes eld
\end_inset
Modified: short/3D/PyLith/trunk/doc/userguide/fileformats/fileformats.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/fileformats/fileformats.lyx 2007-06-25 06:58:19 UTC (rev 7464)
+++ short/3D/PyLith/trunk/doc/userguide/fileformats/fileformats.lyx 2007-06-25 07:54:54 UTC (rev 7465)
@@ -1,4 +1,4 @@
-#LyX 1.4.4 created this file. For more info see http://www.lyx.org/
+#LyX 1.4.3 created this file. For more info see http://www.lyx.org/
\lyxformat 245
\begin_document
\begin_header
@@ -53,7 +53,7 @@
\end_layout
\begin_layout Standard
-PyLith Mesh ASCII files allow quick specification of the mesh information
+PyLith mesh ASCII files allow quick specification of the mesh information
for very small, simple meshes that are most easily written by hand.
We do not recommend using this format for anything other than these very
small, simple meshes.
@@ -103,7 +103,7 @@
\end_layout
\begin_layout LyX-Code
-// squares of edge length 2.
+// square cells of edge length 2.
\end_layout
\begin_layout LyX-Code
@@ -241,7 +241,7 @@
\end_layout
\begin_layout LyX-Code
- // see Section XX for diagrams giving the order for each
+ // see Section 4.2 for diagrams giving the order for each
\end_layout
\begin_layout LyX-Code
@@ -422,11 +422,12 @@
\end_layout
\begin_layout Standard
-Spatialdata files provide specification of a field over some set of points.
+Spatial database files provide specification of a field over some set of
+ points.
There is no topology associated with the points.
- Spatialdata files contain a header describing the set of points and then
- the data with each line listing the coordinates of a point followed by
- the values of the fields for that point.
+ Spatial database files contain a header describing the set of points and
+ then the data with each line listing the coordinates of a point followed
+ by the values of the fields for that point.
Although multiple values can be specified at each point with more than
one value included in a search query, the interpolation of each value will
be done indepedently.
@@ -441,13 +442,12 @@
Spatial database files can specifiy spatial variations over zero, one, two,
and three dimensions.
Zero dimensional variations correspond to uniform values.
- One-dimensional spatial variations correspond to linear variations, which
- need not coincide with coordinate axes.
- Likewise, two-dimensional spatial variations correspond to values specifies
- on a planar surface (which need not coincide with the coordinate axes)
- and three-dimensional spatial variations correspond to variations over
- a volume.
- In one, two, and three dimensions, queries can use a
+ One-dimensional spatial variations correspond to piecewise linear variations,
+ which need not coincide with coordinate axes.
+ Likewise, two-dimensional spatial variations correspond to variations on
+ a planar surface (which need not coincide with the coordinate axes) and
+ three-dimensional spatial variations correspond to variations over a volume.
+ In one, two, or three dimensions, queries can use a
\begin_inset Quotes eld
\end_inset
@@ -505,11 +505,14 @@
\end_layout
\begin_layout LyX-Code
-// right-lateral with 0.25 m of reverse slip at the surface with // a linear
- taper from 2.0 m to 0.0 m from -2 km to -4 km.
+// right-lateral with 0.25 m of reverse slip at the surface with
\end_layout
\begin_layout LyX-Code
+// a linear taper from 2.0 m to 0.0 m from -2 km to -4 km.
+\end_layout
+
+\begin_layout LyX-Code
\end_layout
@@ -582,10 +585,14 @@
\begin_layout LyX-Code
// and stored but not parsed for meaning.
- Unit conversions will // likely be implemented in a future PyLith release.
+ Unit conversions will
\end_layout
\begin_layout LyX-Code
+ // likely be implemented in a future PyLith release.
+\end_layout
+
+\begin_layout LyX-Code
value-units = m m m
\end_layout
@@ -780,12 +787,11 @@
\end_layout
\begin_layout LyX-Code
- // Conversion factor to get to meters (only applies to vertical coordinate
- unless you are
+ // Conversion factor to get to meters (only applies to vertical
\end_layout
\begin_layout LyX-Code
- // using a geocentric coordinate system).
+ // coordinate unless you are using a geocentric coordinate system).
\end_layout
\begin_layout LyX-Code
@@ -1024,14 +1030,18 @@
\begin_inset Quotes erd
\end_inset
- to see a list of available geographic projections.
+ to see a list of available geographic
\end_layout
\begin_layout LyX-Code
- // projector = projection {
+ // projections.
\end_layout
\begin_layout LyX-Code
+ projector = projection {
+\end_layout
+
+\begin_layout LyX-Code
// Name of the projection.
run
\begin_inset Quotes eld
@@ -1041,14 +1051,23 @@
\begin_inset Quotes erd
\end_inset
- to see a list of supported projections.
+ to see a list of
\end_layout
\begin_layout LyX-Code
- projection = utm // Use the Universal Transverse Mercator projection.
+ // supported projections.
+ Use the Universal Transverse Mercator
\end_layout
\begin_layout LyX-Code
+ // projection.
+\end_layout
+
+\begin_layout LyX-Code
+ projection = utm
+\end_layout
+
+\begin_layout LyX-Code
units = m // Units in the projection.
\end_layout
@@ -1057,17 +1076,16 @@
\end_layout
\begin_layout LyX-Code
- // Provide a list of projection options; these are the command line
- arguments you would
+ // Provide a list of projection options; these are the command
\end_layout
\begin_layout LyX-Code
- // use with the proj program.
- Refer to the Proj.4 library documentation for complete
+ // line arguments you would use with the proj program.
+ Refer to
\end_layout
\begin_layout LyX-Code
- // details.
+ // the Proj.4 library documentation for complete details.
\end_layout
\begin_layout LyX-Code
@@ -1121,12 +1139,11 @@
\end_layout
\begin_layout LyX-Code
- // Conversion factor to get to meters (only applies to vertical coordinate
- unless you are
+ // Conversion factor to get to meters (only applies to vertical
\end_layout
\begin_layout LyX-Code
- // using a geocentric coordinate system).
+ // coordinate unless you are using a geocentric coordinate system).
\end_layout
\begin_layout LyX-Code
@@ -1223,37 +1240,57 @@
\begin_layout LyX-Code
// Origin of the local Cartesian coordinate system.
- To avoid roundoff errors it is best to pick a location near the center
- of the region of interest.
- An elevation on the surface of the Earth in the middle of the region also
- works well (and makes the vertical coordinate easy to interpret).
+ To avoid
\end_layout
\begin_layout LyX-Code
-origin-lon = -116.7094 // Longitude of the origin in decimal degrees (west
- is negative).
+ // roundoff errors it is best to pick a location near the center of
\end_layout
\begin_layout LyX-Code
-origin-lat = 36.3874 // Latitude of the origin in decimal degrees (north
- is positive).
+ // the region of interest.
+ An elevation on the surface of the Earth
\end_layout
\begin_layout LyX-Code
+ // in the middle of the region also works well (and makes the
+\end_layout
+
+\begin_layout LyX-Code
+ // vertical coordinate easy to interpret).
+\end_layout
+
+\begin_layout LyX-Code
+ origin-lon = -116.7094 // Longitude of the origin in decimal degrees
+\end_layout
+
+\begin_layout LyX-Code
+ // (west is negative).
+\end_layout
+
+\begin_layout LyX-Code
+ origin-lat = 36.3874 // Latitude of the origin in decimal degrees
+\end_layout
+
+\begin_layout LyX-Code
+ // (north is positive).
+\end_layout
+
+\begin_layout LyX-Code
\end_layout
\begin_layout LyX-Code
-// Elevation with respect to the vertical datum.
- Units are the same as the Cartesian
+ // Elevation with respect to the vertical datum.
+ Units are the
\end_layout
\begin_layout LyX-Code
-// coordinate system (in this case meters).
+ // same as the Cartesian coordinate system (in this case meters).
\end_layout
\begin_layout LyX-Code
-origin-elev = 3.5
+ origin-elev = 3.5
\end_layout
\begin_layout LyX-Code
@@ -1277,5 +1314,81 @@
\end_layout
+\begin_layout Subsection
+Spatial Database Parameters
+\end_layout
+
+\begin_layout Standard
+As in the other Pyre objects, spatial database objects contain parameters
+ that can be set from the command line or
+\family typewriter
+.cf
+\family default
+g or
+\family typewriter
+.pml
+\family default
+ files.
+ The parameters for a spatial database are:
+\end_layout
+
+\begin_layout Description
+label Label for the database, which is used in diagnostic messages.
+\end_layout
+
+\begin_layout Description
+query_type Type of search query to perform.
+ Values for this parameter are
+\begin_inset Quotes eld
+\end_inset
+
+linear
+\begin_inset Quotes erd
+\end_inset
+
+ and
+\begin_inset Quotes eld
+\end_inset
+
+nearest
+\begin_inset Quotes erd
+\end_inset
+
+ (default).
+\end_layout
+
+\begin_layout Description
+iohandler Database importer.
+ Only one importer is implemented, so you do not need to change this setting.
+\end_layout
+
+\begin_layout Description
+iohandler.filename Filename for the spatial database.
+\end_layout
+
+\begin_layout Standard
+An example of setting these parameters in a
+\family typewriter
+.cfg
+\family default
+ file is:
+\end_layout
+
+\begin_layout LyX-Code
+label = Material properties
+\end_layout
+
+\begin_layout LyX-Code
+query_type = linear
+\end_layout
+
+\begin_layout LyX-Code
+iohandler.filename = mydb.spatialdb
+\end_layout
+
+\begin_layout LyX-Code
+
+\end_layout
+
\end_body
\end_document
Modified: short/3D/PyLith/trunk/doc/userguide/governingeqns/governingeqns.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/governingeqns/governingeqns.lyx 2007-06-25 06:58:19 UTC (rev 7464)
+++ short/3D/PyLith/trunk/doc/userguide/governingeqns/governingeqns.lyx 2007-06-25 07:54:54 UTC (rev 7465)
@@ -845,18 +845,8 @@
\end_inset
-\begin_inset Marginal
-status open
-
-\begin_layout Standard
-Need to check this equation.
\end_layout
-\end_inset
-
-
-\end_layout
-
\begin_layout Subsection
Vector Notation
\end_layout
@@ -1005,16 +995,6 @@
Within an element we represent the fields as a linear combination of a set
of basis functions and the values of the fields at vertices of the element,
-\begin_inset Marginal
-status open
-
-\begin_layout Standard
-Is this written correctly?
-\end_layout
-
-\end_inset
-
-
\begin_inset Formula \begin{equation}
\overrightarrow{a}=\underline{N}\cdot\overrightarrow{a^{e}},\end{equation}
@@ -1031,16 +1011,6 @@
is the field at an element's vertices.
Rewriting the trial functions and displacement field in terms of the basis
functions gives
-\begin_inset Marginal
-status open
-
-\begin_layout Standard
-Is the trial function expression correct?
-\end_layout
-
-\end_inset
-
-
\begin_inset Formula \begin{equation}
\overrightarrow{\phi}=\overrightarrow{N},\text{ and}\end{equation}
@@ -1081,7 +1051,7 @@
\end_layout
\begin_layout Section
-Explicit Time Integration of Elasticity Equation
+Solution Method for Dynamic Problems
\end_layout
\begin_layout Standard
@@ -1177,7 +1147,7 @@
\end_layout
\begin_layout Section
-Solution Method for Infinitesimal Strain Quasi-Static Problems
+Solution Method for Quasi-Static Problems
\end_layout
\begin_layout Standard
Modified: short/3D/PyLith/trunk/doc/userguide/install/install.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/install/install.lyx 2007-06-25 06:58:19 UTC (rev 7464)
+++ short/3D/PyLith/trunk/doc/userguide/install/install.lyx 2007-06-25 07:54:54 UTC (rev 7465)
@@ -61,9 +61,7 @@
\end_layout
\begin_layout Standard
-Help is available via the CIG Short-Term Crustal Dynamics Mailing List and
- CIG's issue tracking system.
- The
+The
\begin_inset LatexCommand \url[CIG Short-Term Crustal Dynamics Mailing List]{cig-short at geodynamics.org}
\end_inset
@@ -125,7 +123,7 @@
binary packages.
On the one hand, using these packages removes the burden of configuring,
building, and installing these packages, but it can come with its own host
- of complications if a consistent compiler and configuration settings are
+ of complications if consistent compiler and configuration settings are
not used across all of the packages on which PyLith depends.
This is usually not an issue with Linux distributions, such as Fedora,
Ubuntu, and Debian that have good quality control; it can be an issue with
Modified: short/3D/PyLith/trunk/doc/userguide/intro/intro.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/intro/intro.lyx 2007-06-25 06:58:19 UTC (rev 7464)
+++ short/3D/PyLith/trunk/doc/userguide/intro/intro.lyx 2007-06-25 07:54:54 UTC (rev 7465)
@@ -87,7 +87,7 @@
Simulation parameters are generally specified through the use of simple
ASCII files or the command line.
At present, mesh information may be provided using a simple ASCII file
- (PyLith ASCII format) or imported from CUBIT or LaGriT, two widely-used
+ (PyLith mesh ASCII format) or imported from CUBIT or LaGriT, two widely-used
meshing packages.
The elements currently available include a linear bar in 1D, linear triangles
and quadrilaterals in 2D, and linear tetrahedra and hexahedra in 3D.
@@ -133,7 +133,7 @@
Since there are a wide variety of mesh formats, this information must then
be translated into something that the computational physics code can understand.
PyLith presently provides three mesh importing options: CUBIT Exodus format,
- LaGriT GMV + Pset files, and PyLith ASCII format.
+ LaGriT GMV + Pset files, and PyLith mesh ASCII format.
The modeling of the physical processes of interest is performed by a code
such as PyLith.
Once the computations have been performed, the results must be exported
Modified: short/3D/PyLith/trunk/doc/userguide/materials/materials.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/materials/materials.lyx 2007-06-25 06:58:19 UTC (rev 7464)
+++ short/3D/PyLith/trunk/doc/userguide/materials/materials.lyx 2007-06-25 07:54:54 UTC (rev 7465)
@@ -1,4 +1,4 @@
-#LyX 1.4.4 created this file. For more info see http://www.lyx.org/
+#LyX 1.4.3 created this file. For more info see http://www.lyx.org/
\lyxformat 245
\begin_document
\begin_header
@@ -71,12 +71,11 @@
\end_layout
\begin_layout Enumerate
-In the mesh generation process, a material identifier must be assigned to
- each cell.
+In the mesh generation process, assign a material identifier to each cell.
\end_layout
\begin_layout Enumerate
-A material container must be created unless a suitable one already exists.
+Create a material container unless a suitable one already exists.
\end_layout
\begin_layout Enumerate
@@ -113,8 +112,11 @@
mesh generator.
For example, in the PyLith mesh ASCII format, the identifiers are listed
in the cells group using the material-id data; in CUBIT materials are defined
- using blocks; in LaGriT materials are defined by the attribute imt and
- the mregion command.
+ using blocks; in LaGriT materials are defined by the attribute
+\family typewriter
+imt1
+\family default
+ and the mregion command.
\end_layout
\begin_layout Subsection
@@ -130,7 +132,11 @@
not yet available.
The default material container is a homogeneous material, i.e., a single
material model for the entire problem.
- A two-material container (pylith.materials.BiMaterial) is also supplied.
+ A two-material container (
+\family typewriter
+pylith.materials.BiMaterial
+\family default
+) is also supplied.
For problems with more than two materials, the user must create the material
container using an
\family typewriter
@@ -141,7 +147,15 @@
examples/templates
\family default
directory of the PyLith distribution).
- Example XX discusses creating a material container using this template.
+ The examples in
+\family typewriter
+examples/3d/hex8
+\family default
+ and
+\family typewriter
+examples/3d/tet4
+\family default
+ use a material container using this template.
This
\family typewriter
.odb
@@ -229,7 +243,7 @@
The parameters for the bulk constitutive model are specified using a spatial
database.
Refer to the discussion of each material model to find the parameters that
- must be specified inthe spatial database.
+ must be specified in the spatial database.
Appendix
\begin_inset LatexCommand \ref{sec:Spatialdata:SimpleIOAscii}
Modified: short/3D/PyLith/trunk/doc/userguide/runpylith/runpylith.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/runpylith/runpylith.lyx 2007-06-25 06:58:19 UTC (rev 7464)
+++ short/3D/PyLith/trunk/doc/userguide/runpylith/runpylith.lyx 2007-06-25 07:54:54 UTC (rev 7465)
@@ -65,7 +65,7 @@
and how the vertices are connected into cells), the material identifier
for each cell, and sets of vertices associated with boundary conditions,
faults, and output (for subsets of the mesh).
- This information can be provided using the PyLith Mesh ASCII format (See
+ This information can be provided using the PyLith mesh ASCII format (See
Chapter
\begin_inset LatexCommand \ref{cha:Tutorials}
@@ -77,7 +77,15 @@
\end_inset
for the format specification) or by importing the information from the
- LaGriT or CUBIT meshing packages (See Section XX [LaGriT/CUBIT tutorials]).
+ LaGriT or CUBIT meshing packages (See
+\family typewriter
+examples/3d/hex8
+\family default
+ and
+\family typewriter
+examples/3d/tet4
+\family default
+).
\end_layout
\begin_layout Enumerate
@@ -134,8 +142,6 @@
Facilities correspond to software modules.
Both facilities and properties have default values provided, so you only
need to set values when you want to deviate from the default behavior.
- Unless you write a module that extends PyLith's functionality, you will
- never need to change any of the facilities from the defaults.
\end_layout
\begin_layout Subsection
@@ -314,8 +320,8 @@
file format is intended for applications in which PyLith input files are
generated by another program, e.g., a GUI, web application, or a high-level
structured editor.
- This file fomat will not be discussed further here.
- But if you are interested in using
+ This file fomat will not be discussed further here, but if you are interested
+ in using
\family typewriter
.pml
\family default
@@ -364,7 +370,7 @@
\begin_layout Enumerate
\family typewriter
-PREFIX/etc/pylithapp.cfg
+$PREFIX/etc/pylithapp.cfg
\family default
, for system-wide settings;
\end_layout
@@ -666,7 +672,7 @@
Geometrical and topological information for the finite element mesh may
be provided by exporting an EXODUS format file from CUBIT, by exporting
a GMV file and an accompanying Pset file from LaGriT, or by specifying
- the information in PyLith Mesh ASCII format.
+ the information in PyLith mesh ASCII format.
See Chapter
\begin_inset LatexCommand \ref{cha:Tutorials}
@@ -692,7 +698,17 @@
\end_inset
).
- The vertex ordering must follow the convention shown in the figures.
+ The vertex ordering must follow the convention shown in Figures
+\begin_inset LatexCommand \ref{fig:1D-linear-elements}
+
+\end_inset
+
+-
+\begin_inset LatexCommand \ref{fig:3D-linear-elements}
+
+\end_inset
+
+.
Quadratic cells are also supported, but at present the only method for
using these cells in PyLith is using PyLith ASCII format.
PyLith does not yet support automatic generation of a quadratic mesh from
@@ -714,7 +730,17 @@
type for each cell in the mesh.
For a mesh with a single material type, there will only be a single label
for every cell in the mesh.
- ***Put in references for all of this***
+ See Chapters
+\begin_inset LatexCommand \ref{cha:material:models}
+
+\end_inset
+
+ and
+\begin_inset LatexCommand \ref{cha:boundary:interface:conditions}
+
+\end_inset
+
+ for more detailed discussions of setting the materials and boundary conditions.
\end_layout
\begin_layout Standard
Modified: short/3D/PyLith/trunk/doc/userguide/tutorials/tutorials.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/tutorials/tutorials.lyx 2007-06-25 06:58:19 UTC (rev 7464)
+++ short/3D/PyLith/trunk/doc/userguide/tutorials/tutorials.lyx 2007-06-25 07:54:54 UTC (rev 7465)
@@ -1,4 +1,4 @@
-#LyX 1.4.4 created this file. For more info see http://www.lyx.org/
+#LyX 1.4.3 created this file. For more info see http://www.lyx.org/
\lyxformat 245
\begin_document
\begin_header
@@ -116,11 +116,6 @@
, will require the use of a mesh generation package to create the meshes.
All of the files used in the example problems are heavily documented, which
should help users to understand the different file formats.
- This tutorial begins with the simplest problem (
-\family typewriter
-examples/twocells/twotri3
-\family default
-), and continues to more complex examples.
\end_layout
\begin_layout Standard
Deleted: short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4/figs/tetmesh.jpg
===================================================================
(Binary files differ)
Modified: short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4/figs/twotet4-mesh.eps
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4/figs/twotet4-mesh.eps 2007-06-25 06:58:19 UTC (rev 7464)
+++ short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4/figs/twotet4-mesh.eps 2007-06-25 07:54:54 UTC (rev 7465)
@@ -1,10 +1,10 @@
%!PS-Adobe-2.0 EPSF-2.0
%%Title: twotet4-mesh.fig
-%%Creator: fig2dev Version 3.2 Patchlevel 5
-%%CreationDate: Sun Jun 24 23:45:43 2007
-%%For: willic3 at Wow.local (Charles Williams)
-%%BoundingBox: 0 0 121 145
-%Magnification: 1.0000
+%%Creator: fig2dev Version 3.2 Patchlevel 4
+%%CreationDate: Sun Jun 24 23:59:35 2007
+%%For: brad at Brads-Computer.local (Brad Aagaard)
+%%BoundingBox: 0 0 204 147
+%%Magnification: 1.0000
%%EndComments
/$F2psDict 200 dict def
$F2psDict begin
@@ -43,26 +43,26 @@
/col30 {1.000 0.880 0.880 srgb} bind def
/col31 {1.000 0.840 0.000 srgb} bind def
/col32 {0.004 0.004 0.004 srgb} bind def
-/col33 {0.992 0.992 0.992 srgb} bind def
-/col34 {0.184 0.208 0.282 srgb} bind def
-/col35 {0.447 0.498 0.675 srgb} bind def
-/col36 {0.996 0.251 0.251 srgb} bind def
-/col37 {0.784 0.000 0.012 srgb} bind def
-/col38 {0.996 0.733 0.412 srgb} bind def
-/col39 {0.961 0.498 0.000 srgb} bind def
-/col40 {0.996 0.996 0.451 srgb} bind def
-/col41 {0.898 0.898 0.000 srgb} bind def
-/col42 {0.376 0.796 0.055 srgb} bind def
-/col43 {0.231 0.490 0.031 srgb} bind def
-/col44 {0.200 0.733 0.996 srgb} bind def
-/col45 {0.118 0.431 0.584 srgb} bind def
-/col46 {0.804 0.565 0.996 srgb} bind def
-/col47 {0.380 0.004 0.686 srgb} bind def
+/col33 {0.988 0.988 0.988 srgb} bind def
+/col34 {0.184 0.207 0.281 srgb} bind def
+/col35 {0.445 0.496 0.672 srgb} bind def
+/col36 {0.992 0.250 0.250 srgb} bind def
+/col37 {0.781 0.000 0.012 srgb} bind def
+/col38 {0.992 0.730 0.410 srgb} bind def
+/col39 {0.957 0.496 0.000 srgb} bind def
+/col40 {0.992 0.992 0.449 srgb} bind def
+/col41 {0.895 0.895 0.000 srgb} bind def
+/col42 {0.375 0.793 0.055 srgb} bind def
+/col43 {0.230 0.488 0.031 srgb} bind def
+/col44 {0.199 0.730 0.992 srgb} bind def
+/col45 {0.117 0.430 0.582 srgb} bind def
+/col46 {0.801 0.562 0.992 srgb} bind def
+/col47 {0.379 0.004 0.684 srgb} bind def
end
save
-newpath 0 145 moveto 0 0 lineto 121 0 lineto 121 145 lineto closepath clip newpath
--147.6 230.4 translate
+newpath 0 147 moveto 0 0 lineto 204 0 lineto 204 147 lineto closepath clip newpath
+-261.0 297.0 translate
1 -1 scale
/cp {closepath} bind def
@@ -123,48 +123,63 @@
% here starts figure with depth 50
% Polyline
2 slj
-0 slc
7.500 slw
-n 3600 1650 m 2625 3075 l 3525 3600 l
+ [60] 0 sd
+n 6003 2617 m
+ 6375 3750 l gs col45 s gr [] 0 sd
+% Polyline
+n 6000 2625 m 4575 4125 l 5550 4725 l
cp gs col45 s gr
% Polyline
+n 6000 2625 m 5550 4725 l 7575 4275 l
+ cp gs col45 s gr
+% Polyline
[60] 0 sd
-n 2625 3075 m
- 4275 2925 l gs col45 s gr [] 0 sd
+n 4575 4125 m
+ 6375 3750 l gs col45 s gr [] 0 sd
% Polyline
-n 3600 1650 m 4275 2925 l 3525 3600 l
- cp gs col45 s gr
+ [60] 0 sd
+n 6375 3750 m
+ 7575 4275 l gs col45 s gr [] 0 sd
+% Polyline
+ [60] 0 sd
+n 5550 4725 m
+ 6375 3750 l gs col45 s gr [] 0 sd
% here ends figure;
%
% here starts figure with depth 40
+/Helvetica-Bold ff 180.00 scf sf
+6450 3675 m
+gs 1 -1 sc (3) col0 sh gr
+/Helvetica-Bold ff 180.00 scf sf
+7650 4275 m
+gs 1 -1 sc (4) col0 sh gr
+/Helvetica-Bold ff 180.00 scf sf
+4350 4200 m
+gs 1 -1 sc (0) col0 sh gr
% Ellipse
7.500 slw
-n 4275 2925 37 37 0 360 DrawEllipse gs col39 1.00 shd ef gr gs col39 s gr
+n 6000 2625 37 37 0 360 DrawEllipse gs col39 1.00 shd ef gr gs col39 s gr
-/Helvetica-Bold ff 200.00 scf sf
-2475 3225 m
-gs 1 -1 sc (0) col0 sh gr
-/Helvetica-Bold ff 200.00 scf sf
-3450 3825 m
+/Helvetica-Bold ff 180.00 scf sf
+5550 4950 m
gs 1 -1 sc (1) col0 sh gr
-/Helvetica-Bold ff 200.00 scf sf
-4350 3075 m
-gs 1 -1 sc (2) col0 sh gr
% Ellipse
-n 3525 3600 37 37 0 360 DrawEllipse gs col39 1.00 shd ef gr gs col39 s gr
+n 4575 4125 37 37 0 360 DrawEllipse gs col39 1.00 shd ef gr gs col39 s gr
-/Helvetica-Bold ff 200.00 scf sf
-3600 1575 m
-gs 1 -1 sc (3) col0 sh gr
% Ellipse
-n 2625 3075 37 37 0 360 DrawEllipse gs col39 1.00 shd ef gr gs col39 s gr
+n 5550 4725 37 37 0 360 DrawEllipse gs col39 1.00 shd ef gr gs col39 s gr
% Ellipse
-n 3600 1650 37 37 0 360 DrawEllipse gs col39 1.00 shd ef gr gs col39 s gr
+n 6375 3750 37 37 0 360 DrawEllipse gs col39 1.00 shd ef gr gs col39 s gr
+% Ellipse
+n 7575 4275 37 37 0 360 DrawEllipse gs col39 1.00 shd ef gr gs col39 s gr
+
+/Helvetica-Bold ff 180.00 scf sf
+5850 2625 m
+gs 1 -1 sc (2) col0 sh gr
% here ends figure;
$F2psEnd
rs
showpage
-%%Trailer
-%EOF
Modified: short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4/figs/twotet4-mesh.fig
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4/figs/twotet4-mesh.fig 2007-06-25 06:58:19 UTC (rev 7464)
+++ short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4/figs/twotet4-mesh.fig 2007-06-25 07:54:54 UTC (rev 7465)
@@ -1,4 +1,4 @@
-#FIG 3.2 Produced by xfig version 3.2.5
+#FIG 3.2
Landscape
Center
Inches
@@ -23,17 +23,25 @@
0 45 #1e6e95
0 46 #cd90fe
0 47 #6101af
-1 3 0 1 39 39 40 -1 20 0.000 1 0.0000 3525 3600 37 37 3525 3600 3562 3600
-1 3 0 1 39 39 40 -1 20 0.000 1 0.0000 2625 3075 37 37 2625 3075 2662 3075
-1 3 0 1 39 39 40 -1 20 0.000 1 0.0000 3600 1650 37 37 3600 1650 3637 1650
-1 3 0 1 39 39 40 -1 20 0.000 1 0.0000 4275 2925 37 37 4275 2925 4312 2925
+1 3 0 1 39 39 40 -1 20 0.000 1 0.0000 6000 2625 37 37 6000 2625 6037 2625
+1 3 0 1 39 39 40 -1 20 0.000 1 0.0000 4575 4125 37 37 4575 4125 4612 4125
+1 3 0 1 39 39 40 -1 20 0.000 1 0.0000 5550 4725 37 37 5550 4725 5587 4725
+1 3 0 1 39 39 40 -1 20 0.000 1 0.0000 6375 3750 37 37 6375 3750 6412 3750
+1 3 0 1 39 39 40 -1 20 0.000 1 0.0000 7575 4275 37 37 7575 4275 7612 4275
2 3 0 1 45 7 50 -1 -1 0.000 2 0 -1 0 0 4
- 3600 1650 4275 2925 3525 3600 3600 1650
+ 6000 2625 4575 4125 5550 4725 6000 2625
2 3 0 1 45 7 50 -1 -1 0.000 2 0 -1 0 0 4
- 3600 1650 2625 3075 3525 3600 3600 1650
+ 6000 2625 5550 4725 7575 4275 6000 2625
2 1 1 1 45 7 50 -1 -1 4.000 2 0 -1 0 0 2
- 2625 3075 4275 2925
-4 0 0 40 -1 18 12 0.0000 4 135 105 2475 3225 0\001
-4 0 0 40 -1 18 12 0.0000 4 135 105 3450 3825 1\001
-4 0 0 40 -1 18 12 0.0000 4 135 105 4350 3075 2\001
-4 0 0 40 -1 18 12 0.0000 4 135 105 3600 1575 3\001
+ 4575 4125 6375 3750
+2 1 1 1 45 7 50 -1 -1 4.000 2 0 -1 0 0 2
+ 6375 3750 7575 4275
+2 1 1 1 45 7 50 -1 -1 4.000 2 0 -1 0 0 2
+ 5550 4725 6375 3750
+2 1 1 1 45 7 50 -1 -1 4.000 2 0 -1 0 0 2
+ 6003 2617 6375 3750
+4 0 0 40 -1 18 12 0.0000 4 120 105 5850 2625 2\001
+4 0 0 40 -1 18 12 0.0000 4 120 105 6450 3675 3\001
+4 0 0 40 -1 18 12 0.0000 4 120 90 7650 4275 4\001
+4 0 0 40 -1 18 12 0.0000 4 120 105 4350 4200 0\001
+4 0 0 40 -1 18 12 0.0000 4 120 105 5550 4950 1\001
Modified: short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4/twotet4.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4/twotet4.lyx 2007-06-25 06:58:19 UTC (rev 7464)
+++ short/3D/PyLith/trunk/doc/userguide/tutorials/twotet4/twotet4.lyx 2007-06-25 07:54:54 UTC (rev 7465)
@@ -1,4 +1,4 @@
-#LyX 1.4.4 created this file. For more info see http://www.lyx.org/
+#LyX 1.4.3 created this file. For more info see http://www.lyx.org/
\lyxformat 245
\begin_document
\begin_header
@@ -99,7 +99,7 @@
\begin_layout Standard
\align center
\begin_inset Graphics
- filename figs/twotet4-mesh.fig
+ filename figs/twotet4-mesh.eps
\end_inset
Modified: short/3D/PyLith/trunk/doc/userguide/userguide.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/userguide.lyx 2007-06-25 06:58:19 UTC (rev 7464)
+++ short/3D/PyLith/trunk/doc/userguide/userguide.lyx 2007-06-25 07:54:54 UTC (rev 7465)
@@ -1,4 +1,4 @@
-#LyX 1.4.4 created this file. For more info see http://www.lyx.org/
+#LyX 1.4.3 created this file. For more info see http://www.lyx.org/
\lyxformat 245
\begin_document
\begin_header
@@ -361,7 +361,7 @@
\begin_layout Bibliography
-\bibitem [4]{Zienkiewicz:Taylor:2000}
+\bibitem [7]{Zienkiewicz:Taylor:2000}
Zienkiewicz, O.C.
and R.L.
Taylor (2000),
@@ -373,7 +373,7 @@
\begin_layout Bibliography
-\bibitem [5]{Taylor:2003}
+\bibitem [8]{Taylor:2003}
Taylor, R.L.
(2003), `FEAP--A Finite Element Analysis Program',
\shape italic
More information about the cig-commits
mailing list