[cig-commits] r16987 - in short/3D/PyLith/trunk/examples/meshing/surfaces/nurbs: contours dem

[brad at geodynamics.org]

Author: brad
Date: 2010-06-11 09:09:00 -0700 (Fri, 11 Jun 2010)
New Revision: 16987

Modified:
   short/3D/PyLith/trunk/examples/meshing/surfaces/nurbs/contours/README
   short/3D/PyLith/trunk/examples/meshing/surfaces/nurbs/dem/README
Log:
Cleanup of README text.

Modified: short/3D/PyLith/trunk/examples/meshing/surfaces/nurbs/contours/README
===================================================================
--- short/3D/PyLith/trunk/examples/meshing/surfaces/nurbs/contours/README	2010-06-11 15:59:17 UTC (rev 16986)
+++ short/3D/PyLith/trunk/examples/meshing/surfaces/nurbs/contours/README	2010-06-11 16:09:00 UTC (rev 16987)
@@ -1,41 +1,37 @@
-This is a very simple example showing how to create a NURBS surface
-from a set of contours using Cubit. The simplest way to create a
-surface from a set of contours is to use them to create a skin surface
-(see Cubit documentation). Note that this example is pertinent to a
-set of semi-parallel truncated contours. The example is a set of
-contours defining the subduction interface for the Hikurangi
-subduction zone, New Zealand, rotated so the subduction zone is
-oriented approximately N-S.  There are essentially three steps to
-creating the NURBS surface:
+This is a simple example showing how to create a NURBS surface from a
+set of contours using Cubit. The simplest way to create a surface from
+a set of contours is to use them to create a skin surface (see Cubit
+documentation). Note that this example is pertinent to a set of
+semi-parallel truncated contours. The example defines the subduction
+interface for the Hikurangi subduction zone, New Zealand, rotated so
+the subduction zone is oriented approximately N-S.  There are three
+steps to creating the NURBS surface. The first step is probably not
+needed in many cases.
 
-1. The first step is probably not needed in many cases. In the
-original data file (hikurangi_shiftrot.txt) many of the internal
-contours are truncated, segmented, or incomplete. A Python script
-(fill_contours.py) has been provided to fill in the missing contour
-sections, assuming that the first and last contours are complete. The
-parameters to control this script are in the file
-'fill_contours.cfg'. Once the parameters have been set, the script can
-be run by simply typing:
+1. In the original data file (hikurangi_shiftrot.txt) many of the
+internal contours are truncated, segmented, or incomplete. A Python
+script (fill_contours.py) fills in the missing contour sections,
+assuming that the first and last contours are complete. The parameters
+to control this script are in the file 'fill_contours.cfg'. Once the
+parameters have been set, the script can be run by simply typing:
 
 ./fill_contours.py
 
-This will create a new file named 'hikurangi_shiftrot_fill.txt'. Note
-that this script is very unsophisticated and relies on the contours
-having an approximate N-S orientation.
+This creates a new file named 'hikurangi_shiftrot_fill.txt'. Note that
+this script is very unsophisticated and relies on the contours having
+an approximate N-S orientation.
 
-2.  Once we have a complete set of contours, we can convert them to
-spline curve definitions that may be used by Cubit. A Python script
-(cont2lines.py) has been provided to do this, and the parameters are
-set in the file 'cont2lines.cfg'. Once the Python script is run, it
-will create a separate spline curve Cubit command for each contour in
-the journal directory. It will also create a main Cubit journal file
-(hikurangi_mksurf.jou) that will playback all the journal files in the
-journal directory and then create a skin surface using Cubit (see
-Cubit documentation).
+2.  Once we have a complete set of contours, we convert them to spline
+curve definitions that may be used by Cubit using the Python script,
+cont2lines.py; the parameters are set in the file
+'cont2lines.cfg'. The Python script will create a separate spline
+curve Cubit command for each contour in the journal directory. It will
+also create a main Cubit journal file (hikurangi_mksurf.jou) that will
+playback all the journal files in the journal directory and then
+create a skin surface using Cubit (see Cubit documentation).
 
-3.  We then just need to start Cubit and playback the
-hikurangi_mksurf.jou file to create an ACIS NURBS surface
-(hikurangi_sub_geom.sab).
+3.  We then just run Cubit and playback the hikurangi_mksurf.jou file
+to create an ACIS NURBS surface (hikurangi_sub_geom.sab).
 
 Once the NURBS surface has been created, it may be used in future
 Cubit sessions by importing it:

Modified: short/3D/PyLith/trunk/examples/meshing/surfaces/nurbs/dem/README
===================================================================
--- short/3D/PyLith/trunk/examples/meshing/surfaces/nurbs/dem/README	2010-06-11 15:59:17 UTC (rev 16986)
+++ short/3D/PyLith/trunk/examples/meshing/surfaces/nurbs/dem/README	2010-06-11 16:09:00 UTC (rev 16987)
@@ -1,25 +1,23 @@
-This is a very simple example showing how to create a NURBS surface
-using Cubit, given a set of regularly-spaced data, such as might be
-obtained from a DEM. With this sort of input, the best way to create
-the surface is probably as a net surface (see Cubit
-documentation). This requires either a mapped mesh or a set of
+This is a simple example showing how to create a NURBS surface using
+Cubit, given a set of regularly-spaced data, such as might be obtained
+from a DEM. We create the surface as a net surface (see Cubit
+documentation); this requires either a mapped mesh or a set of
 intersecting lines (u-lines and v-lines). In either case, the
 intersecting lines must for a logically structured quadrilateral
-mesh. A Python script (dem2lines.py) is provided to create the
-mesh. The script also performs the additional task of resampling the
-original data outside a specified region for which full resolution is
-desired. This is useful because using a full-resolution surface for
+mesh. The Python script, dem2lines.py, creates the lines and resamples
+the original data outside a specified region for which full resolution
+is desired. This is useful because using a full-resolution surface for
 the entire region can be quite memory intensive.
 
 The steps for creating the NURBS surface are as follows:
 
-1.  The starting point is a very coarse DEM in ASCII format of
-Mt. Ruapehu volcano in New Zealand. Note that the DEM must be in ASCII
-format and it must be ordered in either rows or columns. The DEM used
-in this example was produced using the GMT grd2xyz utility.
+1.  We start with a very coarse DEM of Mt. Ruapehu volcano in New
+Zealand in ASCII format. Note that the DEM must be in ASCII format and
+it must be ordered in either rows or columns. The DEM used in this
+example was produced using the GMT grd2xyz utility.
 
 2.  The parameters for the Python script are contained in the file
-dem2lines.cfg. In this file you must specify the name of the input
+dem2lines.cfg. In this file we specify the name of the input
 file, the name of an output VTK file (for viewing the resampled DEM
 using a package such as ParaView), and prefixes for the output u-lines
 and v-lines.  The x_min, x_max, etc. values indicate the region over
@@ -27,7 +25,7 @@
 occurs at skip_interval, 2*skip_interval, etc. until the edge of the
 DEM is reached.
 
-3.  Once the parameters have been set, you can run the script like:
+3.  Once the parameters have been set, run the script:
 
 ./dem2lines.py