Parameter names changes as announced in today's mail to users@cactuscode.org.

You must also update thorn IOUtil now.

This thorn will be moved from BetaThorns to CactusPUGHIO now.


git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGHIO/IOPanda/trunk@32 38c3d835-c875-442e-b0fe-21c19ce1d001

1 files changed, 9 insertions, 9 deletions

diff --git a/doc/documentation.tex b/doc/documentation.tex
index 53b1102..eeeae89 100644
--- a/doc/documentation.tex
+++ b/doc/documentation.tex
@@ -4,10 +4,10 @@
 
 \title{IOPanda}
 \author{Jonghyun Lee}
-\date{1999}
+\date{1999\\$ $Revision$ $Date$ $}
 \maketitle
 
-\abstract{Thorn IOPanda provides parallel I/O methods for 3D output of grid functions and multidimensional arrays in using the Panda parallel I/O library.\\
+\abstract{Thorn {\bf IOPanda} provides parallel I/O methods for 3D output of grid functions and multidimensional arrays in using the Panda parallel I/O library.\\
 %
 \section{What is Panda?}
 %
@@ -19,13 +19,13 @@ First, Panda provides high-performance collective array I/O. High-performance I/
 entire I/O process rather than just passively respond to file read and write
 requests from the compute processors.
   
-Second, Panda supports flexible in-memory and on-disk layouts. In Panda, applications can use different in-memory and on-disk layouts. If the user specifies different layouts in memory and on disk, Panda automatically and efficiently reorganize the data at I/O time. It supports both regular and irregular distribution of arrays. For regular distribution, Panda follows High-Performance Fortran (HPF) style distribution. The IOPanda thorn use (BLOCK, *, *) distribution as a default when writing out grid functions in Cactus, which makes the process to create a single array file much easier when multiple I/O processors creates multiple data files.
+Second, Panda supports flexible in-memory and on-disk layouts. In Panda, applications can use different in-memory and on-disk layouts. If the user specifies different layouts in memory and on disk, Panda automatically and efficiently reorganize the data at I/O time. It supports both regular and irregular distribution of arrays. For regular distribution, Panda follows High-Performance Fortran (HPF) style distribution. The {\bf IOPanda} thorn use (BLOCK, *, *) distribution as a default when writing out grid functions in Cactus, which makes the process to create a single array file much easier when multiple I/O processors creates multiple data files.
      
-Finally, Panda supports many other useful features such as adaptive mesh refinement (AMR) and automatic data migration. For the IOPanda thorn, these features will be included soon.   
+Finally, Panda supports many other useful features such as adaptive mesh refinement (AMR) and automatic data migration. For the {\bf IOPanda} thorn, these features will be included soon.   
 
-\section{Thorn IOPanda}
+\section{Thorn {\bf IOPanda}}
 %
-Thorn IOPanda registers an IO method called {\tt IOPanda\_3D} with the IO interface in the flesh. This method creates three-dimensional output of 3D grid functions. (and possibly multidimensional arrays, which are not implemented fully in Cactus yet). Panda library integrated into IOPanda thorn has been modified and currently it supports to write array data in IEEEIO binary format. It will be modified again so that it can support output in HDF5. 
+Thorn {\bf IOPanda} registers an I/O method called {\tt IOPanda} with the I/O interface in the flesh. This method creates three-dimensional output of 3D grid functions. (and possibly multidimensional arrays, which are not implemented fully in Cactus yet). Panda library integrated into {\bf IOPanda} thorn has been modified and currently it supports to write array data in IEEEIO binary format. It will be modified again so that it can support output in HDF5. 
 
 Data written by panda goes into files named {\tt "<varname>.<rank\_of\_io\_processor>"} and will be placed in the directory which is specified in the input paramemter file. Futher processing of these data can be done with visualization tools like Amira, AVS, and IDL. 
 
@@ -34,11 +34,11 @@ Checkpoint/recovery operations are not implemented yet and will be included in t
 %
 \section{Comments}
 %
-Since IOPanda uses parameters from IOUtil it also needs this I/O skeleton thorn compiled into Cactus and activated.
+Since {\bf IOPanda} uses parameters from {\bf IOUtil} it also needs this I/O skeleton thorn compiled into Cactus and activated.
 
-When using IOPanda thorn, sometimes an error regarding MPI\_TYPE\_MAX can occur. If this happens, simply increase the value using {\tt setenv MPI\_TYPE\_MAX <larger number than current value>}.
+When using {\bf IOPanda} thorn, sometimes an error regarding MPI\_TYPE\_MAX can occur. If this happens, simply increase the value using {\tt setenv MPI\_TYPE\_MAX <larger number than current value>}.
 
-If arrays cannot be divided evenly by the mesh determined by Cactus (i.e. dividing 10x10 array into nine chunks using 3x3 mesh), IOPanda can't handle this case because it divides array in a way different from Cactus. Please avoid this case for now.  
+If arrays cannot be divided evenly by the mesh determined by Cactus (i.e. dividing 10x10 array into nine chunks using 3x3 mesh), {\bf IOPanda} can't handle this case because it divides array in a way different from Cactus. Please avoid this case for now.  
 % Automatically created from the ccl files 
 % Do not worry for now.
 \include{interface}