[cig-commits] r16838 - short/3D/PyLith/trunk/doc/userguide/extending

[brad at geodynamics.org]

Author: brad
Date: 2010-05-30 13:58:43 -0700 (Sun, 30 May 2010)
New Revision: 16838

Modified:
   short/3D/PyLith/trunk/doc/userguide/extending/extending.lyx
Log:
Added note on limitations of being able to extend PyLith.

Modified: short/3D/PyLith/trunk/doc/userguide/extending/extending.lyx
===================================================================
--- short/3D/PyLith/trunk/doc/userguide/extending/extending.lyx	2010-05-30 20:58:09 UTC (rev 16837)
+++ short/3D/PyLith/trunk/doc/userguide/extending/extending.lyx	2010-05-30 20:58:43 UTC (rev 16838)
@@ -68,7 +68,13 @@
  you set the spatial database to UniformDB, SimpleDB, or SCECCVMH you are
  switching between different compatible components for a spatial database
  facility.
- In this section we provide examples of how to extend PyLith for components
+ Modifying the governing equations to include other physical processes requires
+ changing the data structures associated with the solution and altering
+ the PyLith code.
+\end_layout
+
+\begin_layout Standard
+In this section we provide examples of how to extend PyLith for components
  that users will most likely want to replace with their own custom versions.
  You will need a familiarity with Python, Makefiles, and C++ to write your
  own components.