[Commits] [svn:einsteintoolkit] Paper_EinsteinToolkit_2010/ (Rev. 9)

[knarf at cct.lsu.edu]

User: knarf
Date: 2011/01/19 04:15 PM

Modified:
 /
  ET.tex

Log:
 something on base modules - probably too much

File Changes:

Directory: /
============

File [modified]: ET.tex
Delta lines: +30 -11
===================================================================
--- ET.tex	2011-01-19 21:39:18 UTC (rev 8)
+++ ET.tex	2011-01-19 22:15:54 UTC (rev 9)
@@ -247,7 +247,7 @@
 \section{Core Technologies}
 
 \subsection{Cactus Framework}
-\todo{Gab}
+\todo{1/2 page Gab}
 
 The \textbf{Cactus
   Framework}~\cite{CS_cactus_web,CS_Goodale02a,CS_cactususersguide} is
@@ -279,7 +279,7 @@
 combined with contributions from the community.
 
 \subsection{Carpet Mesh Refinement}
-\todo{Erik}
+\todo{1/2 page Erik}
 
 While Cactus is distributed with a structured-mesh unigrid MPI
 parallel driver (\codename{PUGH}\footnote{Recent results with a
@@ -303,24 +303,43 @@
 
 
 \subsection{Simulation Factory}
-\todo{Erik}
+\todo{1/3 page Erik}
 
 \subsection{Kranc}
-\todo{Ian}
+\todo{1/3 page Ian}
 
 
 \section{Components}
 
 \subsection{Base Modules}
-\todo{Frank}
+\todo{1/3 page Frank}
+A modular design has many advantages for distributed development of a
+complex software system, but it also requires standards to be defined
+and followed. Low-level interoperability can be and is provided by
+the Cactus infrastructure. One example of this is using one module
+from within another, e.g. by calling a function within another thorn
+without the knowledge about the programming language this function
+is actually implemented in.
 
+However, certain other standards are very hard or impossible to
+enforce on a technical level. Examples for this are the exact
+definitions of physical variables, their units, but also on the more
+technical level the variable names used for the physical quantities.
+The Einstein Toolkit provides modules with the sole purpose to
+declare variables which are commonly used in many modules, and to
+define their meaning and unit. The latter however, is not strictly
+enforced, and instead provided by the module documentation. Two
+of the those base modules are described in the following in more
+detail, because general relativistic codes use different conventions
+in especially those areas.
+
 \paragraph{Vacuum Spacetimes}
 
 \paragraph{Relativistic Matter Spacetimes}
 
 
 \subsection{Initial Data}
-\todo{Josh}
+\todo{1/2 page Josh}
 
 \paragraph{Gravitational Waves}
 
@@ -330,7 +349,7 @@
 
 
 \subsection{Evolution Methods}
-\todo{Christian}
+\todo{1/2 page Christian}
 
 \paragraph{Spacetime}
 
@@ -338,7 +357,7 @@
 
 
 \subsection{Analysis}
-\todo{Tanja}
+\todo{1/2 page Tanja}
 
 \paragraph{Masses}
 
@@ -348,7 +367,7 @@
 
 
 \subsection{Relativity Tools}
-\todo{Peter}
+\todo{1/2 page Peter}
 
 \paragraph{Black Hole Excision}
 
@@ -358,7 +377,7 @@
 
 
 \subsection{Infrastructure and Numerical Methods}
-\todo{Erik}
+\todo{1/2 page Erik}
 
 \paragraph{Domains and Coordinates}
 
@@ -368,7 +387,7 @@
 
 
 \section{Examples}
-\todo{Frank}
+\todo{2 pages Frank}
 
 \paragraph{Kerr-Schild}