[docs] tuto MPI: update smpirun replay syntax

Did not work on my machine due to missing hostfile,
but I think it was already failing for the same reason.

diff --git a/docs/source/Tutorial_MPI_Applications.rst b/docs/source/Tutorial_MPI_Applications.rst
index de4fb1f..a0b5b92 100644 (file)
--- a/docs/source/Tutorial_MPI_Applications.rst
+++ b/docs/source/Tutorial_MPI_Applications.rst
@@ -451,25 +451,19 @@ replay it on a different platform with the same amount of nodes. The
 replay is much faster than live simulation, as the computations are
 skipped (the application must be network-dependent for this to work).
 
 replay is much faster than live simulation, as the computations are
 skipped (the application must be network-dependent for this to work).
 

-You can even generate the trace during as live simulation, as follows:
+You can even generate the trace during the live simulation as follows:

 
 .. code-block:: shell
 
 
 .. code-block:: shell
 

-   $ smpirun -trace-ti --cfg=tracing/filename:LU.A.32 -np 32 -platform ../cluster_backbone.xml bin/lu.A.32 
+   $ smpirun -trace-ti --cfg=tracing/filename:LU.A.32 -np 32 -platform ../cluster_backbone.xml bin/lu.A.32

 
 The produced trace is composed of a file ``LU.A.32`` and a folder
 
 The produced trace is composed of a file ``LU.A.32`` and a folder

-``LU.A.32_files``. To replay this with SMPI, you need to first compile
-the provided ``smpi_replay.cpp`` file, that comes from
-`simgrid/examples/smpi/replay
-<https://framagit.org/simgrid/simgrid/tree/master/examples/smpi/replay>`_.
+``LU.A.32_files``. You can replay this trace with SMPI thanks to ``smpirun``
+with the following command:

 
 .. code-block:: shell
 
 
 .. code-block:: shell
 

-   $ smpicxx ../replay.cpp -O3 -o ../smpi_replay
-
-Afterward, you can replay your trace in SMPI as follows:
-
-   $ smpirun -np 32 -platform ../cluster_torus.xml -ext smpi_replay ../smpi_replay LU.A.32
+   $ smpirun -np 32 -platform ../cluster_torus.xml -replay LU.A.32

 
 All the outputs are gone, as the application is not really simulated
 here. Its trace is simply replayed. But if you visualize the live
 
 All the outputs are gone, as the application is not really simulated
 here. Its trace is simply replayed. But if you visualize the live


@@ -478,7 +472,12 @@ unchanged. The simulation does not run much faster on this very
 example, but this becomes very interesting when your application
 is computationally hungry.
 
 example, but this becomes very interesting when your application
 is computationally hungry.
 

-.. todo:: smpi_replay should be installed by SimGrid, and smpirun interface could be simplified here.
+.. todo::
+
+    The commands should be separated and executed by some CI to make sure
+    the documentation is up-to-date.
+
+    An hostfile should be given to smpirun.

 
 Lab 3: Execution Sampling on EP
 -------------------------------
 
 Lab 3: Execution Sampling on EP
 -------------------------------