From 1e6ebd4341e178e2f4591d28b79b239cfbfd0ad4 Mon Sep 17 00:00:00 2001
From: heister <heister@0785d39b-7218-0410-832d-ea1e28bc413d>
Date: Sun, 26 Jan 2014 23:41:36 +0000
Subject: [PATCH] leave a note on how to start step-32

git-svn-id: https://svn.dealii.org/trunk@32320 0785d39b-7218-0410-832d-ea1e28bc413d
---
 deal.II/examples/step-32/doc/results.dox | 15 ++++++++++++---
 1 file changed, 12 insertions(+), 3 deletions(-)

diff --git a/deal.II/examples/step-32/doc/results.dox b/deal.II/examples/step-32/doc/results.dox
index ca0d584e14..d26392b17d 100644
--- a/deal.II/examples/step-32/doc/results.dox
+++ b/deal.II/examples/step-32/doc/results.dox
@@ -38,10 +38,19 @@ cluster at Texas A&amp;M University.
 
 <h3>Results for a 2d circular shell testcase</h3>
 
+Next, we will run step-32 with the parameter file in the directory. Here we
+are using 50 processors. The command to launch is (note that step-32.prm is
+the default):
 
-If we run the program as shown above (with the parameter file in the
-directory), the output will look roughly
-like this when run on 50 processors:
+<code>
+<pre>
+$ mpirun -n 50 ./step-32
+</pre>
+</code>
+
+Note that running a job on a cluster typically requires going through a job
+scheduler, which we won't discuss here. The output will look roughly like
+this:
 
 <code>
 <pre>
-- 
2.39.5