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

[knarf at cct.lsu.edu]

User: knarf
Date: 2011/11/14 12:41 AM

Modified:
 /
  ET.tex

Log:
 cosmetics in Cactus section

File Changes:

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

File [modified]: ET.tex
Delta lines: +14 -14
===================================================================
--- ET.tex	2011-11-14 06:38:16 UTC (rev 200)
+++ ET.tex	2011-11-14 06:41:20 UTC (rev 201)
@@ -365,37 +365,37 @@
 The {\tt Cactus}
   Framework~\cite{Cactuscode:web,Goodale:2002a,CactusUsersGuide:web} is
 an open source, modular, portable programming environment for
-collaborative HPC computing, primarily developed at Louisiana State University,
+collaborative HPC computing primarily developed at Louisiana State University,
 and historically at the Albert Einstein Institute and the
-National Center for Supercomputing Applications~\todo{RH: for the senior
+National Center for Supercomputing Applications\todo{~RH: for the senior
 people: is there a citable paper or somthing similar that docuemnts NCSA's
 involvement in Cactus?}.
-The {\tt Cactus} computational toolkit consists of general modules providing
+The {\tt Cactus} computational toolkit consists of general modules which provide
 parallel drivers, coordinates, boundary conditions, interpolators,
 reduction operators, and efficient I/O in different data
-formats. Generic interfaces are used, making it possible to use
-external packages and improved modules which are immediately available
-to its users.
+formats. Generic interfaces make it possible to use
+external packages and improved modules which are made immediately available
+to users.
 
 The structure of the {\tt Cactus} framework is completely modular, with
-only a very small core (the ``flesh'') providing the interfaces between
+only a very small core (the ``flesh'') which provides the interfaces between
 modules,
-both at compile- and run-time. The {\tt Cactus} modules, called ``thorns'',
-may, and typically do, specify inter-module dependencies, e.g., to share or
+both at compile- and run-time. The {\tt 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.
 Modules compiled into an executable can remain dormant at run-time.
 This usage of modules and a common interface between them, enables researchers
 to 1) easily use modules written by others without the need to understand
-all details of their implementation, and 2) to write their own modules
+all details of their implementation, and 2) write their own modules
 without the need to change the source code of other parts of a simulation,
 in the (supported) programming language of their choice.
 The number of active modules within a typical {\tt Cactus} simulation ranges
-from tens to hundreds, often with an extensive set of inter-module
+from tens to hundreds and often has an extensive set of inter-module
 dependencies.
 
-The {\tt Cactus} Framework was developed by the
-numerical relativity community, and although it is a general component
-framework that supports different application domains its core user
+The {\tt Cactus} Framework was developed originally by the
+numerical relativity community, and although it is now a general component
+framework that supports different application domains, its core user
 group continues to be comprised of numerical relativists. 
 It is not surprising therefore, that one of the science modules provided in
 the Einstein Toolkit is a set of state of the art modules to simulate binary