[Swift-commit] r3869 - text/parco10submission

[noreply at svn.ci.uchicago.edu]

Author: dsk
Date: 2011-01-06 08:38:21 -0600 (Thu, 06 Jan 2011)
New Revision: 3869

Modified:
   text/parco10submission/paper.tex
Log:
minor changes in 2 and 3


Modified: text/parco10submission/paper.tex
===================================================================
--- text/parco10submission/paper.tex	2011-01-06 05:31:34 UTC (rev 3868)
+++ text/parco10submission/paper.tex	2011-01-06 14:38:21 UTC (rev 3869)
@@ -415,7 +415,7 @@
 
 The notation \verb|{}| indicates
 that the type represents a reference to a single \emph{opaque}
-file --- i.e., a reference to an external object whose structure is opaque to the Swift script. For convenience such type declarations typically use the equivalent shorthand \verb|type image;| (which new users find confusing but which has become a Swift idiom).
+file, i.e., a reference to an external object whose structure is opaque to the Swift script. For convenience such type declarations typically use the equivalent shorthand \verb|type image;| (which new users find confusing but which has become a Swift idiom).
 
 Mapped type variable declarations can be specified with a
 \emph{mapping} descriptor enclosed in \verb|<>| that indicates the file to be mapped to the variable.
@@ -450,7 +450,7 @@
 
 Swift has three types of functions:
 
-\emph{Built-in functions} are defined in the Java code of the Swift runtime system, and perform various utility functions (numeric conversion, string manipulation, etc.) Operators (+ *, etc.) defined by the language behave similarly.
+\emph{Built-in functions} are defined in the Java code of the Swift runtime system, and perform various utility functions (numeric conversion, string manipulation, etc.) Operators (+, *, etc.) defined by the language behave similarly.
 
 \emph{Application interface functions} (declared using the app keyword) 
 specify the interface (input files and parameters, and output files) of application programs in
@@ -476,7 +476,7 @@
 declaration} that describes the command line syntax for that
 program and its input and output files.
 For example, the following example lists a function that makes use
-of the common utility {\tt convert}\cite{ImageMagick_WWW} to rotate an
+of the common utility {\tt convert}~\cite{ImageMagick_WWW} to rotate an
 image by a specified angle:
 
 \begin{verbatim}
@@ -486,7 +486,7 @@
 \end{verbatim}
 
 %\katznote{do you need to say anything about where/how convert is defined/located?}
-(The {\tt convert} executable is located at run time through a catalog of applications or through a PATH environment variable).
+(The {\tt convert} executable is located at run time through a catalog of applications or through a PATH environment variable.)
 
 The rotate function is then invoked as follows:
 
@@ -542,7 +542,7 @@
    file frames[] <filesys_mapper; pattern="*.jpeg">;
 \end{verbatim}
 
-Here we used a built-in mapper called \verb|filesys_mapper| to
+This uses a built-in mapper called \verb|filesys_mapper| to
 all files matching the name pattern \verb|*.jpeg| to an array.
 
 The \verb|foreach| construct can be used to apply a function to each element of an array:
@@ -917,7 +917,7 @@
 executed when the function is invoked. The first token (in this case
 \verb|convert|) defines a \emph{transformation name} which is used to
 determine the executable name. Subsequent expressions define the command-line arguments for that executable:
-\verb|"-rotate"| is a string literal; angle specifies the value of the
+``\verb|-rotate|'' is a string literal; angle specifies the value of the
 angle parameter; the syntax \verb|@variable| evaluates to the filename
 of the supplied variable, thus \verb|@input| and \verb|@output|
 evaluate to the filenames of the corresponding parameters. It should
@@ -929,14 +929,14 @@
 \section{Execution engine}
 \label{Execution}
 
-Swift is implemented by compiling to a Karajan program\cite{Karajan}, which provides
+Swift is implemented by compiling to a Karajan program~\cite{Karajan}, which provides
 several benefits: a lightweight threading model,
 futures,
 remote job execution,
 and
 remote file transfer and data management.
 Both remote execution and data transfer and management functions are provided through generalized
-abstracted interfaces called "providers".
+abstracted interfaces called ``providers''.
 Data providers enable data transfer and management to be performed through a wide variety of protocols including direct local copying, GridFTP, HTTP, WebDAV, SCP, and FTP.
 Execution providers enable job execution to take place using direct POSIX process fork, Globus GRAM, Condor (and Condor-G), PBS, SGE, SSH.
 The Swift execution model can thus be extended by
@@ -1046,6 +1046,9 @@
 In such a case, Swift provides a \emph{restart log} that encapsulates
 which function invocations have been successfully completed. 
 \mikenote{What manual interv. and why???}
+\katznote{Maybe ignore this, and just say: A subsequent Swift run may be started
+with this restart log; this will avoid re-execution of already
+executed invocations.}
 After
 appropriate manual intervention, 
 a subsequent Swift run may be started