[Swift-commit] r3372 - text/parco10submission

[noreply at svn.ci.uchicago.edu]

Author: wozniak
Date: 2010-06-15 20:27:29 -0500 (Tue, 15 Jun 2010)
New Revision: 3372

Modified:
   text/parco10submission/Wozniak.bib
   text/parco10submission/paper.tex
Log:
More fixes


Modified: text/parco10submission/Wozniak.bib
===================================================================
--- text/parco10submission/Wozniak.bib	2010-06-16 01:27:20 UTC (rev 3371)
+++ text/parco10submission/Wozniak.bib	2010-06-16 01:27:29 UTC (rev 3372)
@@ -6222,3 +6222,14 @@
   booktitle = {Proc. International Symposium of Grid Computing},
   year = 2007
 }
+
+ at ARTICLE{CNARI_2007,
+  title = {Accelerating Medical Research using the {S}wift
+                  Workflow System},
+  author = {Stef-Praun, T. and Clifford, B. and Foster, I. and
+           Hasson, U. and Hategan, M. and Small, S. L. and
+           Wilde, M. and Zhao, Y.},
+  journal = {Studies in Health Technology and Informatics},
+  volume = 126,
+  year = 2007
+}
\ No newline at end of file

Modified: text/parco10submission/paper.tex
===================================================================
--- text/parco10submission/paper.tex	2010-06-16 01:27:20 UTC (rev 3371)
+++ text/parco10submission/paper.tex	2010-06-16 01:27:29 UTC (rev 3372)
@@ -428,7 +428,9 @@
 invoke other SwiftScript procedures rather than a component
 program. The basic structure of a composite procedure may be thought
 of as a graph of calls to other procedures.
-
+The following script will invoke two procedures, with an intermediate
+data file named anonymously connecting the \verb|first| and
+\verb|second| procedures:
 \begin{verbatim}
    (file output) process (file input) {
       file intermediate;
@@ -441,12 +443,8 @@
    y = process(x);
 \end{verbatim}
 
-This will invoke two procedures, with an intermediate data file named
-anonymously connecting the \verb|first| and \verb|second| procedures.
-
 Ordering of execution is generally determined by execution of \verb|app|
 procedures, not by any containing procedures. In this code block:
-
 \begin{verbatim}
    (file a, file b) A() {
       a = A1();
@@ -457,11 +455,10 @@
    s = S(x);
    t = S(y);
 \end{verbatim}
+a valid execution order is: \verb|A1 S(x) A2 S(y)|. The compound
+procedure \verb|A| does not have to have fully completed for its
+return values to be used by subsequent statements.
 
-then a valid execution order is: \verb|A1 S(x) A2 S(y)|. The
-compound procedure \verb|A| does not have to have fully completed
-for its return values to be used by subsequent statements.
-
 \subsection{More about types}
 \label{LanguageTypes}
 
@@ -1134,14 +1131,14 @@
 
 \subsection{Provisioning for more granular applications}
 
-In some applications (such as CNARI\cite{CNARI}) the execution time
-for a program is very short. In such circumstances, execution time can
-become dominated by GRAM and LRM overhead. A resource provisioning
-system such as Falkon\cite{FALKON} or the CoG~\cite{CoG_2001} coaster
-mechanism developed for Swift can be used to ameliorate this overhead,
-by incurring the allocation overhead once per worker node. Both of
-these mechanisms can be plugged into Swift straightforwardly through
-the CoG provider API.
+In some applications the execution time for a program is very
+short. In such circumstances, execution time can become dominated by
+GRAM and LRM overhead. A resource provisioning system such as
+Falkon~\cite{Falkon_2008} or the CoG~\cite{CoG_2001} coaster mechanism
+developed for Swift can be used to ameliorate this overhead, by
+incurring the allocation overhead once per worker node. Both of these
+mechanisms can be plugged into Swift straightforwardly through the CoG
+provider API.
 
 \subsection{Swift on thousands of cores}