Commit a32e23e5 authored by Nathalie Furmento's avatar Nathalie Furmento
Browse files

tutorials/2015-06-PATC/index.html: fixes

git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/starpu/website@15575 176f6dd6-97d6-42f4-bd05-d3db9ad07c7a
parent 4975f92c
......@@ -163,7 +163,7 @@ $ export STARPU_HOSTNAME=mirage
</pre></tt>
<p>
Also add this do your <tt>.bash_profile</tt> for further connections. Of course, on
Also add this to your <tt>.bash_profile</tt> for further connections. Of course, on
a heterogeneous cluster, the cluster launcher script should set various
hostnames for the different node classes, as appropriate.
</p>
......@@ -174,7 +174,7 @@ hostnames for the different node classes, as appropriate.
<p>
All files needed for the lab works are available in
the <a href="files/2015.06.patcStarPU.zip">zip file</a>. Copy that
the <a href="files/2015.06.patcStarPU.zip">zip file</a>. Copy this
file on your PlaFRIM/DiHPES account and unzip its contents.
</p>
......@@ -698,7 +698,7 @@ module load runtime/starpu/1.1.4
</pre></tt>
<p>
The trace file is output in <tt>/tmp</tt> by default. Since execution will
The trace file is stored in <tt>/tmp</tt> by default. Since execution will
happen on a cluster node, the file will not be reachable after execution,
we need to tell StarPU to store output traces in the home directory, by
setting:
......@@ -723,7 +723,7 @@ $ starpu_fxt_tool -i ~/prof_file_*
</pre></tt>
<p>
That will create
This will create
<ul>
<li>
a <tt>paje.trace</tt> file, which can be opened by using the <a
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment