[Swift-commit] r7018 - SwiftTutorials/swift-cray-tutorial/doc

[ketan at ci.uchicago.edu]

Author: ketan
Date: 2013-08-27 21:08:45 -0500 (Tue, 27 Aug 2013)
New Revision: 7018

Modified:
   SwiftTutorials/swift-cray-tutorial/doc/README
Log:
small changes

Modified: SwiftTutorials/swift-cray-tutorial/doc/README
===================================================================
--- SwiftTutorials/swift-cray-tutorial/doc/README	2013-08-28 01:49:44 UTC (rev 7017)
+++ SwiftTutorials/swift-cray-tutorial/doc/README	2013-08-28 02:08:45 UTC (rev 7018)
@@ -100,7 +100,7 @@
 that serve as easy-to-understand proxies for real science
 applications. These "programs" behave as follows.
 
-simulation.sh
+simulate.sh
 ~~~~~~~~~~~
 
 The simulation.sh script serves as a trivial proxy for any more
@@ -297,7 +297,7 @@
 which is located in the tutorial PATH:
 
 -----
-$ cleanup.sh
+$ cleanup
 ------
 
 NOTE: You'll also find two Swift configuration files in each `partNN`
@@ -675,7 +675,7 @@
 "pilot jobs" using qsub. These pilot jobs hold on to compute nodes and
 allow Swift to run many app invocations within a single job. This
 mechanism is described in
-http://www.swift-lang.org/papers/UCC-coasters.pdf[this paper from UCC-2011]
+http://www.swift-lang.org/papers/UCC-coasters.pdf[this paper from UCC-2011].
 
 `profile` tags specify additional attributes for the execution
 provider. (A "provider" is like a driver which knows how to handle
@@ -722,7 +722,7 @@
 (specifically 1 over) `jobThrottle` * 100 to be used.
 
 The last two attributes specify where and how Swift should perform
-data management.  `workdirectory lus/scratch/{env.USER}/swiftwork`
+data management.  `workdirectory /lus/scratch/{env.USER}/swiftwork`
 specifies where the Swift "application execution sanbox directory"
 used for each app will be located. In some situations this can be a
 directory local to the compute node (eg, for Cray systems, `/dev/shm`
@@ -847,7 +847,6 @@
 We use the following `apps` file:
 -----
 $ cat multipools
-$ cat multipools
 raven     simulate simulate.sh
 ravenGPU  simulate simulate.sh
 localhost stats    stats.sh