[Swift-commit] r4191 - text/parco10submission

[noreply at svn.ci.uchicago.edu]

Author: wozniak
Date: 2011-03-17 14:04:07 -0500 (Thu, 17 Mar 2011)
New Revision: 4191

Added:
   text/parco10submission/ResponseToReviews3.txt
Modified:
   text/parco10submission/paper.tex
Log:
A few more corrections and new response file


Added: text/parco10submission/ResponseToReviews3.txt
===================================================================
--- text/parco10submission/ResponseToReviews3.txt	                        (rev 0)
+++ text/parco10submission/ResponseToReviews3.txt	2011-03-17 19:04:07 UTC (rev 4191)
@@ -0,0 +1,109 @@
+
+Here are the things I found (page numbers refer to numbers on the
+printed pages, not to page numbers inside acrobat reader):
+
+Last paragraph in section 1 skips mention of section 5, which is very strange
+
+RESPONSE: Corrected
+
+p. 12: "It is important to understood"
+
+RESPONSE: Corrected
+
+p. 12: becomes"in scope"  [space missing]
+
+RESPONSE: Corrected
+
+p. 12: "The invocation of mappers... are"   ['are' should be 'is']
+
+RESPONSE: Corrected
+
+p. 13: My dictionary says 'de facto' not de-facto
+
+RESPONSE: Corrected
+
+p. 13: "underly" should be "underlie" [underly is not a word]
+
+RESPONSE: Corrected
+
+p. 14: "automatically selection"
+
+RESPONSE: Corrected
+
+p. 14: semntics
+
+RESPONSE: Corrected
+
+p. 17: applicatoin
+
+RESPONSE: Corrected
+
+p. 19: "discoveries...continues to drive"   wrong [should be 'continue']
+
+RESPONSE: Corrected
+
+p. 19: My dictionary says self-contained, not "self contained"
+
+RESPONSE: Corrected
+
+p. 20: line -9: maybe "find N files"? [doesn't make sense to me as is]
+
+RESPONSE: Corrected
+
+p. 22: line 11: geos[] . should be geos[]. (extraneous space)
+
+RESPONSE: Corrected
+
+p. 22: "for statement" should be "for the statement"
+
+RESPONSE: Corrected
+
+p. 22: line -8 "of every input tiles" should be "of every input tile"
+
+RESPONSE: Corrected
+
+p. 25: 7*27*10=1890 not 1690 (also see p. 26 where 1670 is mentioned)
+
+RESPONSE: Corrected
+
+p. 25: "These structure" [should be structures]
+
+RESPONSE: Corrected
+
+p. 25: "selectable energy function to used by" [should be 'to be used by']
+
+RESPONSE: Corrected
+
+Fig. 3: acronym SEM is undefined (also 2nd paragraph of section 5.2)
+
+RESPONSE: Corrected
+
+Fig. 4: lower half: color of "Processors" differs left vs. right; why?
+
+RESPONSE: Corrected
+
+p. 32: "rational" should be "rationale"
+
+RESPONSE: Corrected
+
+p. 32: "goals to providing" should be "goals of providing"
+
+RESPONSE: Corrected
+
+p. 33: line -12 "environment" should be "environments"
+
+RESPONSE: Corrected
+
+p. 34: "on single parallel system" - another typo
+
+RESPONSE: Corrected
+
+p. 35: "thousands of small accesses to the filesystem" might not
+       only be a bottleneck, it may significantly degrade
+       responsiveness for every process on the system
+
+RESPONSE: Corrected
+
+p. 38: "J. H G" -> J. H. G." ?
+
+RESPONSE: Corrected

Modified: text/parco10submission/paper.tex
===================================================================
--- text/parco10submission/paper.tex	2011-03-17 19:01:08 UTC (rev 4190)
+++ text/parco10submission/paper.tex	2011-03-17 19:04:07 UTC (rev 4191)
@@ -134,12 +134,12 @@
 parallelized.
 Swift exploits the maximal concurrency permitted by data dependencies within a script and by external resource availability.
 
-Swift enables users to specify process composition by representing processes as functions, where input data files and process parameters become function parameters and output data files become function return values. 
+Swift enables users to specify process composition by representing processes as functions, where input data files and process parameters become function parameters and output data files become function return values.
 Swift also
 provides a high-level representation of collections of data (used as
 function inputs and outputs) and a
 specification (``mapper'') that allows those collections to be processed by external
-programs. 
+programs.
 We chose to make the Swift language purely functional (i.e., all operations
 have a well-defined set of inputs and outputs, all variables are write-once,
 and no script-level side effects are permitted by the language) in order to prevent the difficulties that
@@ -163,7 +163,7 @@
 from a given application, such that an execution environment can
 automatically make remote execution transparent.
 Without this,
-achieving location transparency 
+achieving location transparency
 is not feasible.  Swift adds to scripting what the remote procedure call (RPC)
 paradigm~\cite{RPC} adds to programming: by formalizing the inputs and outputs of
 applications that have been declared as Swift functions, it makes the distributed remote
@@ -207,7 +207,7 @@
 itself, it is also not readily obvious that such a feature would
 contradict the main goals of Swift, and therefore is not ruled out as a
 possible future development.
-} 
+}
 
 \section{The Swift language}
 \label{Language}
@@ -601,7 +601,7 @@
 floating point numbers and true/false values, respectively.
 }
 
-\hide{ 
+\hide{
 Sometimes data may be stored in a form that does not fit with Swift's
 file-and-site model;  for example, data might be stored in an database on a
 server. In that case, a variable can be declared to have
@@ -1136,7 +1136,7 @@
 For additional visualization, the script assembles a full map of all
 the input tiles, placed in their proper grid location on the MODIS
 world map projection, and with the selected tiles marked. Since this
-operation needs true-color images of every input tiles, these are
+operation needs true-color images of every input tile, these are
 computed---again in parallel---with 317 jobs generated by the foreach
 statement at lines 76--78. The power of Swift's implicit
 parallelization is shown vividly here: since the {\tt colorMODIS} call
@@ -1500,13 +1500,13 @@
 \subsection{Filesystem access optimizations}
 
 Similarly, some applications deal with files that are uncomfortably
-small for GridFTP (on the order of tens of bytes). In this situation, a
-lightweight file access mechanism provided by Coasters can be
+small for GridFTP (on the order of tens of bytes). In this situation,
+a lightweight file access mechanism provided by Coasters can be
 substituted for GridFTP. When running on HPC resources, the thousands
-of small accesses to the filesystem may create a bottleneck.  To
-mitigate this problem, we have investigated application needs and
-are developing a set of collective data management
-primitives ~\cite{CDM_2009}.
+of small accesses to the filesystem may create a bottleneck for all
+system users.  To mitigate this problem, we have investigated
+application needs and are developing a set of collective data
+management primitives ~\cite{CDM_2009}.
 
 \subsection{Provenance}
 \label{Provenance}