User: bmundim Date: 2011/08/22 12:29 AM
Modified: / ET.tex
Log: A few typos fixed.
File Changes:
Directory: / ============
File [modified]: ET.tex Delta lines: +6 -5 =================================================================== --- ET.tex 2011-08-22 04:21:20 UTC (rev 113) +++ ET.tex 2011-08-22 05:29:40 UTC (rev 114) @@ -349,7 +349,7 @@
In addition, the Einstein Toolkit provides computer scientists an ideal platform to perform state-of-the-art research, which directly -benefits research in other areas of science and providines an +benefits research in other areas of science and provides an immediate application of their research. One of the most prominent examples within the Einstein Toolkit is the Cactus Computational Toolkit, a framework developed by computer scientists and now used by researchers @@ -360,7 +360,7 @@ The mechanisms for the development and support of the Einstein Toolkit are designed to be open, transparent and community-driven. The complete source code, documentation and tools included in the Einstein Toolkit are distributed -under open-source licenses. The Einstein Toolkit maintains an version +under open-source licenses. The Einstein Toolkit maintains a version control system ({\tt svn.einsteintoolkit.org}) with open access that contains software supported by the Einstein Toolkit, the toolkit web pages, and documentation. An open wiki for documentation @@ -414,7 +414,7 @@ develop new application level tools for performance and correctness.
The structure of the Cactus framework is completely modular, with -only a very small core proving the interfaces between modules, +only a very small core providing the interfaces between modules, both at compile- and run-time. The Cactus modules, called ``thorns'', may, and typically do, specify inter-module dependencies, e.g., to share or extend configuration information, common variables or runtime parameters. @@ -663,11 +663,12 @@ The Einstein Toolkit provides modules with the sole purpose to declare commonly used variables, and to define their meaning and units. The latter is not strictly enforced, and instead documented as part of the -module documentation. Two of the these base modules are described in the +module documentation. Two of these base modules are described in the following in more detail, because especially these quantities might be defined differently in various simulation codes.
\subsubsection{ADMBase} +%BCM: the following sentence seems to be an inadvertently truncated one: Relativistic spacetime evolution methods used within the Cactus framework use different formulations, but essentially all are based on the $3+1$ ADM construction~\cite{Arnowitt:1962hi}, in which @@ -704,7 +705,7 @@ \end{itemize}
The type of initial data chosen for a simulation is specified by the -parameters{\tt initial_data} (3-metric and extrinsic curvature), +parameters {\tt initial_data} (3-metric and extrinsic curvature), {\tt initial_lapse}, {\tt initial_shift}, and by parameters for their first time derivatives, {\tt initial_dtlapse} and {\tt initial_dtshift}, respectively.