[Swift-commit] r3754 - text/parco10submission

[noreply at svn.ci.uchicago.edu]

Author: dsk
Date: 2010-12-08 19:39:04 -0600 (Wed, 08 Dec 2010)
New Revision: 3754

Modified:
   text/parco10submission/ResponseToReviews.txt
   text/parco10submission/Wozniak.bib
   text/parco10submission/paper.tex
Log:
more small changes in Parco paper


Modified: text/parco10submission/ResponseToReviews.txt
===================================================================
--- text/parco10submission/ResponseToReviews.txt	2010-12-09 01:29:08 UTC (rev 3753)
+++ text/parco10submission/ResponseToReviews.txt	2010-12-09 01:39:04 UTC (rev 3754)
@@ -181,8 +181,13 @@
 probably should be defined.  Other acronyms: GRAM, fMRI (and FMRI,
 cf. Fig. 2, which should probably be fMRI).
 
->>> <<<
+>>> 
 
+RDBMS removed.
+FMRI fixed.
+
+<<<
+
 6. All these appear: "stage in", "stage-in", "stagein".  Please be
 consistent (similarly for stage out).
 
@@ -230,8 +235,12 @@
 should have page numbers, some references are missing a year.
 Reference 8 severely mangles "Bresnahan".
 
->>> <<<
+>>> 
 
+Ref 8 fixed.
+
+<<<
+
 14. It is somewhat disingenuous to refer to thousands and millions of
 cores (section 6.2).  All systems I know of are managed as nodes,
 where each node might have 8 or 12 or 16 cores.  This is no essential

Modified: text/parco10submission/Wozniak.bib
===================================================================
--- text/parco10submission/Wozniak.bib	2010-12-09 01:29:08 UTC (rev 3753)
+++ text/parco10submission/Wozniak.bib	2010-12-09 01:39:04 UTC (rev 3754)
@@ -288,7 +288,7 @@
 }
 
 @INPROCEEDINGS{GridFTP_2005,
-  author = {William Allcock and John Bresnahan an Rajkumar Kettimuthu and Michael
+  author = {William Allcock and John Bresnahan and Rajkumar Kettimuthu and Michael
 	Link and Catalin Dumitrescu and Ioan Raicu and Ian Foster},
   title = {The {G}lobus Striped {GridFTP} Framework and Server},
   booktitle = {Proc. Supercomputing},

Modified: text/parco10submission/paper.tex
===================================================================
--- text/parco10submission/paper.tex	2010-12-09 01:29:08 UTC (rev 3753)
+++ text/parco10submission/paper.tex	2010-12-09 01:39:04 UTC (rev 3754)
@@ -526,8 +526,8 @@
 \end{verbatim}
 
 Sometimes data may be stored in a form that does not fit with Swift's
-file-and-site model; \katznote{Swift's ``file-and-site model'' hasn't been introduced before.  I'm not even sure what it is.}  for example, data might be stored in an RDBMS on some
-database server. In that case, a variable can be declared to have
+file-and-site model; \katznote{Swift's ``file-and-site model'' hasn't been introduced before.  I'm not even sure what it is.}  for example, data might be stored in an database on a
+server. In that case, a variable can be declared to have
 \verb|extern| type. This indicates that Swift should use the variable to
 determine execution dependency, but should not attempt other data management;
 for example, it will not perform any form of data stage-in or stage-out;
@@ -967,7 +967,7 @@
 \begin{figure}[htbp]
   \begin{center}
     \includegraphics[scale=1]{img/IMG_fmridataset}
-    \caption{FMRI application data structure\label{FMRI_app_image}}
+    \caption{fMRI application data structure\label{FMRI_app_image}}
   \end{center}
 \end{figure}
 
@@ -1012,7 +1012,7 @@
 }
 
 \end{verbatim}
-    \caption{FMRI application in SwiftScript\label{FMRI_app_script}}
+    \caption{fMRI application in SwiftScript\label{FMRI_app_script}}
 \end{figure}
 
 In this example, the logical structure of the fMRI dataset shown in