+ - :ref:`Describing Algorithms with the S4U interface <S4U_doc>` (in C++)
+ - :ref:`Simulating existing MPI programs with the SMPI toolsuite <SMPI_doc>`
+ (in C, C++, or Fortran)
+ - In some cases, you may want to replay an execution trace in the simulator. This
+ trace lists the events of your application or of your workload, and
+ your application is decomposed as a list of event handlers that are
+ fired according to the trace. SimGrid comes with a build-in support
+ for MPI traces (with solutions to import traces captured by several
+ MPI profilers). You can reuse this mecanism for any kind of trace
+ that you want to replay, for example to study how a P2P DHT overlay
+ reacts to a given workload.
+ - Simulating algorithms with one of the legacy interfaces: :ref:`MSG
+ for distributed algorithms <MSG_doc>` (in :ref:`C <MSG_doc>` or
+ :ref:`Java <Java_doc>`) and SimDAG for
+ centralized algorithms (in C). SimGrid was founded in 1998, and
+ many interfaces were proposed along the way. MSG (introduced
+ around 2002) and SimDag (introduced before 2000), are still present
+ in SimGrid. They do not evolve anymore, but given their popularity,
+ they will not be removed until at least 2020. That being said, our
+ goal is to make S4U so useful that these legacy APIs become useless
+ and obsolete.
+ - We are currently working on the ability to modify any existing
+ application so that it can run on top of SimGrid. This project,
+ called `Remote-SimGrid
+ <git@framagit.org:simgrid/remote-simgrid.git>`_, is highly
+ experimental at this point.