[cig-commits] r8154 - short/3D/PyLith/trunk

[brad at geodynamics.org]

Author: brad
Date: 2007-10-19 09:03:16 -0700 (Fri, 19 Oct 2007)
New Revision: 8154

Modified:
   short/3D/PyLith/trunk/TODO
Log:
Added output use cases to TODO.

Modified: short/3D/PyLith/trunk/TODO
===================================================================
--- short/3D/PyLith/trunk/TODO	2007-10-19 04:22:32 UTC (rev 8153)
+++ short/3D/PyLith/trunk/TODO	2007-10-19 16:03:16 UTC (rev 8154)
@@ -4,20 +4,13 @@
 
 Release 1.0.2
 
-  1. Cleanup ElasticityImplicit::integrateResidual()
+  1. Fix partitioning with cohesive cells.
 
-    Replace update() and restrict with more efficient methods?
-
-    Apply faster update() and restrict() to integrateJacobian and
-    integrateResidual()?
-
   2. Add check to make sure every material in mesh has a material model.
 
     Add check for overlapping of material ids for bulk and cohesive
     cells.
 
-  3. Move PETSc logging out of feassemble module.
-
 Release 1.1
 
   1. Finish AbsorbingDampers BC.
@@ -28,27 +21,82 @@
 
   4. Generalized Maxwell viscoelastic model
 
-  5. Reimplement SolutionIO.
+  5. Move PETSc logging out of feassemble module.
 
-     Need to be able to append fields.
+  6. Reimplement SolutionIO.
+     a. Reimplement SolutionIOVTK
+     b. Implement SolutionIOHDF5
 
-     Want open(), writeTopology(), appendVertexField(),
-     appendCellField(), close() paradigm.
+     General Ideas
 
-     It should be possible to use PETSc viewers, but we will want to
-     setup the viewers in implementation classes and then call the
-     view in the parent class?
+       Need to be able to append fields.
 
-     Follow implementation of MeshIO. SolutionIO implements extracting
-     data from Sieve and calls virtual functions to write data.
+       It should be possible to use PETSc viewers, but we will want to
+       setup the viewers in implementation classes and then call the
+       view in the parent class?
 
-     a. Reimplement SolutionIOVTK
-     b. Implement SolutionIOHDF5
+       Want open(), writeTopology(), appendVertexField(),
+       appendCellField(), close() paradigm.
 
+     Use Cases
+
+       Want to write topology + vertex and/or cell fields
+
+       VTK files
+
+         One per time step, multiple vertex and/or cell fields
+
+       HDF5 files
+
+         One per topology (volume, surface, etc)
+
+         Would prefer to include multiple materials
+
+         Datasets contain entire time histories (makes it possible to
+         slice along time or space)
+
+       Volume information
+
+         Solution field (time histories)
+
+         Distribution information (proc of each cell)
+
+         State variable information for each cell (different info for
+         each material)
+
+           Material parameters (diagnostic)
+
+           State variable values (time histories)
+
+       Lower dimension information (surface/line mesh specified by set
+       of vertices)
+
+         Solution field (time histories)
+
+       Kinematic fault rupture
+
+         Slip and change in tractions (time histories)
+
+         Orientation, final slip, slip time (disgnostic)
+
+       Spontaneous (dynamic) fault rupture
+
+         Slip and change in tractions (time histories)
+
+         Fault constitutive values (time histories)
+
+         Orientation , Fault constitutive parameters (diagnostic)
+
+       Point locations (arbitrary location such as instrument site)
+
+         Interpolate solution to desired location
+
+         Solution field (time history)
+
 General
 
   1. Need to add explanation of output and output parameters to
-  manual.
+  manual (especially fault information).
 
   2. Add dependency diagram to manual.