Add new entry in Release_Notes.

[simgrid.git] / docs / source / Outcomes.rst

diff --git a/docs/source/Outcomes.rst b/docs/source/Outcomes.rst
index 152fe61..152e8e2 100644 (file)
--- a/docs/source/Outcomes.rst
+++ b/docs/source/Outcomes.rst
@@ -3,6 +3,18 @@
 Simulation outcomes
 ###################
 
+.. raw:: html
+
+   <object id="TOC" data="graphical-toc.svg" type="image/svg+xml"></object>
+   <script>
+   window.onload=function() { // Wait for the SVG to be loaded before changing it
+     //var elem=document.querySelector("#TOC").contentDocument.getElementById("DeployBox")
+     //elem.style="opacity:0.93999999;fill:#ff0000;fill-opacity:0.1;stroke:#000000;stroke-width:0.35277778;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1";
+   }
+   </script>
+   <br/>
+   <br/>
+
 .. _outcome_logs:
 
 Textual logging
@@ -13,7 +25,7 @@ should use SimGrid's logging facilities, that are inspired from `Log4J <https://
 severity and their topic. There  is four main concepts in SimGrid's logging mechanism:
 
 The **category** of a message represents its topic. These categories are organized as a hierarchy, loosely corresponding to SimGrid's modules architecture. :ref:`Existing categories
-<logging_categories>` are documented online, but some of them may be disabled depending on the compilation options. Use ``--help-log-categories`` on the command line to see 
+<logging_categories>` are documented online, but some of them may be disabled depending on the compilation options. Use ``--help-log-categories`` on the command line to see
 the categories actually provided a given simulator.
 
 The message **priority** represents its severity. It can be one of ``trace``, ``debug``, ``verb``, ``info``, ``warn``, ``error`` and ``critical``. Every category has a configured
@@ -37,11 +49,10 @@ change the settings at runtime.
 Graphical and statistical logging
 *********************************
 
-To be written. For now, see `this page <https://simgrid.org/contrib/R_visualization.html>`_. 
+To be written. For now, see `this page <https://simgrid.org/contrib/R_visualization.html>`_.
 
 Building your own logging
 *************************
 
-You can add callbacks to the existing signals to get informed of each and every even occuring in the simulator. These callbacks can be used to write logs on disk in the format that
+You can add callbacks to the existing signals to get informed of each and every even occurring in the simulator. These callbacks can be used to write logs on disk in the format that
 you want. Some users did so to visualize the behavior of their simulators with `Jaeger <https://www.jaegertracing.io/>`_.
-