[Swift-commit] r3870 - in text/parco10submission: . plots

[noreply at svn.ci.uchicago.edu]

Author: wozniak
Date: 2011-01-06 09:54:40 -0600 (Thu, 06 Jan 2011)
New Revision: 3870

Modified:
   text/parco10submission/paper.tex
   text/parco10submission/plots/sleep.pdf
Log:
Minor plot improvements


Modified: text/parco10submission/paper.tex
===================================================================
--- text/parco10submission/paper.tex	2011-01-06 14:38:21 UTC (rev 3869)
+++ text/parco10submission/paper.tex	2011-01-06 15:54:40 UTC (rev 3870)
@@ -346,7 +346,7 @@
 Swift scripts are written as a set of functions, composed upwards,
 starting with \emph{atomic functions} that specify the execution of
 external programs, and then higher level functions are composed as
-pipelines (or more generally, graphs) of sub-functions. 
+pipelines (or more generally, graphs) of sub-functions.
 
 Unlike most other scripting languages, Swift expresses
 invocations of ``ordinary programs''---technically, POSIX {\tt exec()}
@@ -387,7 +387,7 @@
 Structure fields can be of any type, while arrays contain only uniform values of a single type. One
 array type is provided for every atomic type (integer, string, boolean, and file reference).
 Arrays use numeric
-indices, but are sparse.  
+indices, but are sparse.
 Both types of collections can contain members of atomic or collection types. Structures contain a finite number of elements. Arrays contain a varying number of elements. Structures and arrays can both recursively reference other structures and arrays in addition to atomic values. Arrays can be nested to provide multi-dimensional indexing.
 
 Due to the dynamic, highly parallel nature of Swift, its arrays have no notion of size. Array elements can be set as a script's execution progresses. The number of elements set increases monotonically. An array is considered ``closed'' when no further statements that set an element of the array can be executed. This state is recognized at run time by information obtained from compile-time analysis of the script's call graph. Also, since all data elements have single-assignment semantics, no garbage collection issues arise.
@@ -452,11 +452,11 @@
 
 \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) 
+\emph{Application interface functions} (declared using the app keyword)
 specify the interface (input files and parameters, and output files) of application programs in
 terms of files and other parameters. They serve as an adapter between the Swift programming model and the mechanisms used to invoke application programs at run time.
 
-\emph{Compound functions} are functions 
+\emph{Compound functions} are functions
 that call atomic and other compound
 functions.
 
@@ -616,7 +616,7 @@
 parameters have been assigned values. As a result of such execution,
 more variables may become assigned, possibly allowing further parts of
 the script to execute. In this way, scripts are implicitly
-concurrent. 
+concurrent.
 
 In this script fragment, execution of functions \verb|p| and \verb|q| can
 occur in parallel:
@@ -737,7 +737,7 @@
 component program atomicity on data output.
 
 \katznote{this previous sentence
-has a lot of stuff that hasn't been defined, and the next one is equally confusing at this point in the paper.} 
+has a lot of stuff that hasn't been defined, and the next one is equally confusing at this point in the paper.}
 
 This can add substantial
 responsibility to component programs, in exchange for allowing arbitrary
@@ -1044,13 +1044,13 @@
 will fail, ultimately resulting in the entire script failing.
 
 In such a case, Swift provides a \emph{restart log} that encapsulates
-which function invocations have been successfully completed. 
+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, 
+appropriate manual intervention,
 a subsequent Swift run may be started
 with this restart log; this will avoid re-execution of already
 executed invocations.
@@ -1122,7 +1122,7 @@
 Using Swift to submit to a large number of sites poses a number of
 practical challenges that are not encountered when running on a small
 number of sites. These challenges are seen when comparing execution on
-the relatively static TeraGrid~\cite{TeraGrid_2005} with execution on the 
+the relatively static TeraGrid~\cite{TeraGrid_2005} with execution on the
 more dynamic Open Science
 Grid (OSG)~\cite{OSG_2007}, where the set of sites that may be used is
 large and changing. It is impractical to maintain a site catalog by
@@ -1599,7 +1599,7 @@
 
 \begin{figure*}[htbp]
   \begin{center}
-    \includegraphics[scale=0.50]{plots/sleep}
+    \includegraphics[scale=0.70]{plots/sleep}
     \caption{Node utilization for {\tt sleep} tasks}
     \label{PlotSleep}
   \end{center}

Modified: text/parco10submission/plots/sleep.pdf
===================================================================
(Binary files differ)