[Swift-commit] r4214 - text/parco10submission

[noreply at svn.ci.uchicago.edu]

Author: dsk
Date: 2011-03-23 03:34:53 -0500 (Wed, 23 Mar 2011)
New Revision: 4214

Modified:
   text/parco10submission/paper.tex
Log:
minor changes


Modified: text/parco10submission/paper.tex
===================================================================
--- text/parco10submission/paper.tex	2011-03-22 21:57:56 UTC (rev 4213)
+++ text/parco10submission/paper.tex	2011-03-23 08:34:53 UTC (rev 4214)
@@ -661,7 +661,7 @@
 uses the built-in \verb|filesys_mapper| to map
 all files matching the name pattern \verb|*.jpeg| to an array--and then applies a function to each element of that array.
 
-Swift mappers can operate on files stored on the local machine in the directory where the {\tt swift} command is executing, or they can map any files accessible to the local machine, using absolute pathnames. Custom mappers (and some of the built-in mappers) can also map variables to files specified by URIs for access from remote servers via protocols such as GridFTP or HTTP, as described in section \ref{Execution}. Mappers can interact with structure fields and array elements in a simple and useful manner.
+Swift mappers can operate on files stored on the local machine in the directory where the {\tt swift} command is executing, or they can map any files accessible to the local machine, using absolute pathnames. Custom mappers (and some of the built-in mappers) can also map variables to files specified by URIs for access from remote servers via protocols such as GridFTP or HTTP, as described in Section~\ref{Execution}. Mappers can interact with structure fields and array elements in a simple and useful manner.
 
 New mappers can be added to Swift either as Java classes or as simple, external executable scripts or programs coded in any language.
 Mappers can operate both as input mappers (which map files to be processed as application inputs) and as output mappers (which specify the names of files to be produced by applications). It is important to understand that mapping a variable is a different operation from setting the value of a variable. Variables of mapped-file type are mapped (conceptually) when the variable becomes ``in scope,'' but they are set when a statement assigns them a value. Mapper invocations (and invocations of external mapper executables) are completely synchronized with the Swift parallel execution model.
@@ -1545,13 +1545,13 @@
 
 \section*{Acknowledgments}
 
-This research is supported in part by NSF grants OCI-721939 and
+This research was supported in part by NSF grants OCI-721939 and
 OCI-0944332 and by the U.S. Department of Energy under contract
 DE-AC02-06CH11357. Computing resources were provided by the Argonne
-Leadership Computing Facility, TeraGrid, the Open Science Grid, the UChicago / Argonne Computation Institute
-Petascale Active Data Store, and the Amazon Web Services Education allocation program.
+Leadership Computing Facility, TeraGrid, the Open Science Grid, the UChicago/Argonne Computation Institute
+Petascale Active Data Store (PADS), and the Amazon Web Services Education allocation program.
 
-The glass cavity simulation example in this article is the work of Glen Hocky of the Reichman Lab of the Columbia University Department of Chemistry. We thank Glen for his contributions to the text and code of section 4 and valuable feedback to the Swift project. We gratefully acknowledge the contributions of current and former Swift team members, collaborators, and users: Sarah Kenny, Allan Espinosa, Zhao Zhang, Luiz Gadelha, David Kelly, Milena Nokolic, Jon Monette, Aashish Adhikari, Marc Parisien, Michael Andric, Steven Small, John Dennis, Mats Rynge,  Michael Kubal, Tibi Stef-Praun, Xu Du, Zhengxiong Hou, and Xi Li. The initial implementation of Swift was the work of Yong Zhao and Mihael Hategan; Karajan was designed and implemented by Hategan. We thank Tim Armstrong for helpful comments on the text.
+The glass cavity simulation example in this article is the work of Glen Hocky of the Reichman Lab of the Columbia University Department of Chemistry. We thank Glen for his contributions to the text and code of Section 4 and valuable feedback to the Swift project. We gratefully acknowledge the contributions of current and former Swift team members, collaborators, and users: Sarah Kenny, Allan Espinosa, Zhao Zhang, Luiz Gadelha, David Kelly, Milena Nokolic, Jon Monette, Aashish Adhikari, Marc Parisien, Michael Andric, Steven Small, John Dennis, Mats Rynge,  Michael Kubal, Tibi Stef-Praun, Xu Du, Zhengxiong Hou, and Xi Li. The initial implementation of Swift was the work of Yong Zhao and Mihael Hategan; Karajan was designed and implemented by Hategan. We thank Tim Armstrong for helpful comments on the text.
 
 \bibliographystyle{elsarticle-num}
 \bibliography{paper,Wozniak} % for ACM SIGS style