[cig-commits] r13408 - short/3D/PyLith/trunk/doc/releasenotes

[brad at geodynamics.org]

Author: brad
Date: 2008-11-25 17:26:45 -0800 (Tue, 25 Nov 2008)
New Revision: 13408

Modified:
   short/3D/PyLith/trunk/doc/releasenotes/announce_v1.3.1.txt
Log:
Final version of release notes.

Modified: short/3D/PyLith/trunk/doc/releasenotes/announce_v1.3.1.txt
===================================================================
--- short/3D/PyLith/trunk/doc/releasenotes/announce_v1.3.1.txt	2008-11-26 00:55:18 UTC (rev 13407)
+++ short/3D/PyLith/trunk/doc/releasenotes/announce_v1.3.1.txt	2008-11-26 01:26:45 UTC (rev 13408)
@@ -5,12 +5,12 @@
 viscoelastic problems in tectonic deformation.
 
 This release fixes several bugs associated with running PyLith in
-parallel. These include selection of the partitioner and calculating
-the change in tractions on the fault surface. The PETSc logging has
-been enhanced by separating the events using stages. This release also
-includes some minor performance improvements to the Sieve
-implementation. We encourage all users of previous PyLith releases to
-switch to this latest release.
+parallel. These include selection of the partitioner, calculating the
+change in tractions on the fault surface, and quasi-static time
+stepping. The PETSc logging has been enhanced by separating the events
+using stages. This release also includes some minor performance
+improvements to the Sieve implementation. We encourage all users of
+previous PyLith releases to switch to this latest release.
 
 You can download the source code and binaries from
 
@@ -41,3 +41,15 @@
 
     - Fixed bug where fault material property databases were not
       closed, resulting in memory not being deallocated.
+
+IMPORTANT NOTE ON UNIT TESTS
+
+  Several unit tests in this release will fail, but this release has
+  been thoroughly checked to verify that it produces correct
+  results. The failing unit tests are associated with new vertices
+  being added to the opposite side of the fault during creation of the
+  cohesive cells in some cases compared with previous
+  implementations. Instead of changing the test data in many locations
+  and potentially encountering this issue in the future, we are going
+  to make the unit tests smarter. We will make another release when
+  these unit tests are updated.