[cig-commits] r13282 - doc/snac

[sue at geodynamics.org]

Author: sue
Date: 2008-11-10 14:06:10 -0800 (Mon, 10 Nov 2008)
New Revision: 13282

Modified:
   doc/snac/snac.lyx
Log:
refixed typos and some other fixes

Modified: doc/snac/snac.lyx
===================================================================
--- doc/snac/snac.lyx	2008-11-10 21:47:48 UTC (rev 13281)
+++ doc/snac/snac.lyx	2008-11-10 22:06:10 UTC (rev 13282)
@@ -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
@@ -1445,18 +1445,11 @@
 
 \end_inset
 
-(b) shows that remeshing can not only generate a more regular mesh but also
+(b) shows that remeshing cannot only generate a more regular mesh but also
  change the bottom boundary of the domain.
- Although useful in some cases, this 
-\begin_inset Quotes sld
-\end_inset
-
-boundary restoring
-\begin_inset Quotes srd
-\end_inset
-
- technique should be used with caution because it also creates unmappable
- regions and thus requires to assume the state and properties of material.
+ Although useful in some cases, this ``boundary restoring'' technique should
+ be used with caution because it also creates unmappable regions and thus
+ requires us to assume the state and properties of material.
  SNAC keeps the deformed boundary by default.
 \end_layout
 
@@ -1522,11 +1515,8 @@
  Having StGermain as a framework, SNAC code must follow certain conventions.
  It means that many abilities are available in generic forms: XML input,
  extensible data structures, classified output streams, etc.
- SNAC is readily customizable through writing a``plugin
-\begin_inset Quotes srd
-\end_inset
-
-, a shared object that can be loaded dynamically at run-time.
+ SNAC is readily customizable through writing a ``plugin,'' a shared object
+ that can be loaded dynamically at run-time.
  The two key design ideas relevant to SNAC are the ``SNAC Context'' and
  ``Entry Points.'' 
 \end_layout
@@ -1548,7 +1538,7 @@
 \begin_layout Enumerate
 Packaging together all the high-level data structures that a SNAC run requires,
  such as the Mesh, boundary conditions, simulation parameters, etc.
- Most of these objects are extensible/and or configurable using the XML
+ Most of these objects are extensible and/or configurable using the XML
  input file.
 \end_layout
 
@@ -1573,30 +1563,15 @@
 
 \begin_layout Standard
 The reason entry points are dynamic lists of function pointers (or ``hooks'')
- is that a user, say a research scientist, often wants to extend the default
+ is that a user, e.g., a research scientist, often wants to extend the default
  functionality of an application at only a few specific points in the code.
  In SNAC, this is simply a matter of adding pointers to their custom functions
  to the relevant entry points.
  For instance, to add a contribution from the Winkler foundation to the
- residual force at each node, one can simply include a plugin called 
-\begin_inset Quotes sld
-\end_inset
-
-SnacWinklerForce
-\begin_inset Quotes srd
-\end_inset
-
-.
- What this plugins does is to add (or 
-\begin_inset Quotes sld
-\end_inset
-
-hook up
-\begin_inset Quotes srd
-\end_inset
-
-) its own force computing routine to the entry point that already has a
- pointer to the function computing internal residual forces.
+ residual force at each node, one can simply include a plugin called ``SnacWinkl
+erForce.'' What this plugins does is to add (or ``hook up'') its own force
+ computing routine to the entry point that already has a pointer to the
+ function computing internal residual forces.
  It is possible to determined which function should be called first.
  This way, the core structure of the code does not need to be modified every
  time new operations on nodes or elements are added.