[cig-commits] [commit] master: Update main.lyx and transfer checklist from old cigma.lyx into a text file. (1d1cd30)

[cig_noreply at geodynamics.org]

Repository : https://github.com/geodynamics/cigma

On branch  : master
Link       : https://github.com/geodynamics/cigma/compare/65c02138d3ae8b87c088cc14fe4f98e21e3f0805...a26f592c25c89a40622404999ba1effcdf6df9e3

>---------------------------------------------------------------

commit 1d1cd30d4904a73ac17c8a0a3ad7792bba520db0
Author: Luis Armendariz <luis>
Date:   Wed Jan 21 19:38:07 2009 +0000

    Update main.lyx and transfer checklist from old cigma.lyx into a text file.


>---------------------------------------------------------------

1d1cd30d4904a73ac17c8a0a3ad7792bba520db0
 checklist.txt | 42 ++++++++++++++++++++++++++++++++++++++++
 main.lyx      | 62 +++++++++++++++++++++++++++++++++++++++++++++++------------
 2 files changed, 92 insertions(+), 12 deletions(-)

diff --git a/checklist.txt b/checklist.txt
new file mode 100644
index 0000000..024576e
--- /dev/null
+++ b/checklist.txt
@@ -0,0 +1,42 @@
+
+Verify that the following points are discussed in the manual:
+
+  - Cigma does not include a mesh generation package, so in order
+    to have greater accuracy in the comparisons one needs to increase
+    order of the integration rule being used.
+
+  - Meshes are internally stored as unstructured meshes.
+
+  - That we can only compare Fields on a single ElementBlock at a time.
+
+Things to check for the release:
+
+  - Files
+    * Make sure the tarball has all the required files
+    * Check for the proper /doc/ files
+    * Check for the proper /examples/ files
+    * Check that all required data files are included (see /tests/data/ directory)
+    * Check that 'make check' works
+
+  - Installation procedures
+    * Create tarball with 'make dist' and test it
+    * Use custom boost installation on ~/opt/boost
+    * Use custom hdf5 installation on ~/opt/hdf5
+    * Use custom vtk installation on ~/opt/vtk
+
+  - Consistency checks
+    * comparing one and zero on brick{1,2} meshes (should give volume)
+    * comparing test.brick and zero on brick{1,2} meshes (should give known answer)
+    * comparing test.square and zero on brick{1,2} meshes (should give known answer)
+
+  - Integration rules
+    * Increase order of integration rule instead of mesh refinement (check convergence)
+
+  - Examples
+    * comparing laplace solutions
+    * comparing citcomcu solutions
+    * comparing conman solutions (see blankenbach)
+    * comparing gale solutions
+    * comparing pylith solutions
+    * comparing geofest solutions
+
diff --git a/main.lyx b/main.lyx
index da3bb16..1393ac7 100644
--- a/main.lyx
+++ b/main.lyx
@@ -835,11 +835,10 @@ How to Select Your Input and Output Datasets
 \end_layout
 
 \begin_layout Standard
-The basic object used to store data in Cigma is a simple two dimensional
- array of values, or dataset.
- Since scientific file formats are capable of storing multiple datasets,
- you will typically need a way to select a specific array on a given data
- file.
+The basic objects used to store data in Cigma are simple two dimensional
+ array of values, or datasets.
+ As scientific file formats are capable of storing multiple datasets, you
+ will typically need a way to select a specific array on a given data file.
  Therefore, regardless of the context, the option arguments to Cigma are
  parsed consistently by following the 
 \family typewriter
@@ -852,11 +851,11 @@ Filename:Location
 \emph on
 filename
 \emph default
- unambiguously determines the target array, then the 
+ part unambiguously determines the target array, then the 
 \emph on
 location
 \emph default
- part of the option argument is taken to be empty.
+ part of the option argument may be omitted.
  Now, depending on how Cigma was configured during the build procedure,
  there are a number of different file formats available for specifying and
  storing your data.
@@ -1224,7 +1223,7 @@ Option (MC) is required if options (M1) and (M2) are given.
 \end_layout
 
 \begin_layout Subsection
-Mesh from an HDF5 File
+Mesh HDF5 File
 \end_layout
 
 \begin_layout Standard
@@ -1280,20 +1279,32 @@ Group location
 \end_layout
 
 \begin_layout LyX-Code
- |-- Attribute 
+ |-- 
+\emph on
+Attribute
+\emph default
+ 
 \series bold
 \emph on
 CellType
 \end_layout
 
 \begin_layout LyX-Code
- |-- Array 
+ |-- 
+\emph on
+Array
+\emph default
+ 
 \series bold
 coordinates
 \end_layout
 
 \begin_layout LyX-Code
- `-- Array 
+ `-- 
+\emph on
+Array
+\emph default
+ 
 \series bold
 connectivity
 \end_layout
@@ -1926,7 +1937,34 @@ Quadrature Rules
 \end_layout
 
 \begin_layout Standard
-Here we discuss the quadrature rules
+Here we discuss the quadrature rules available in Cigma.
+\end_layout
+
+\begin_layout Chapter
+Utilities
+\end_layout
+
+\begin_layout Standard
+Cigma comes with a couple of utilities that make the life easier to the
+ user.
+ One is called 
+\family typewriter
+h5attr
+\family default
+ and lets you see the attributes attached to a dataset inside an HDF5 file.
+ The other one is called 
+\family typewriter
+vtk-residuals
+\family default
+ and allows the user to create visualization files given a mesh and a scalar
+ array representing the residuals over the elements of the mesh.
+\end_layout
+
+\begin_layout Standard
+Normally, these utilities will be installed somewhere in your PATH during
+ the process of installation of the Cigma package, so that you can invoke
+ them from any place in your filesystem after the installation has successfully
+ finished.
 \end_layout
 
 \end_body