For the latest 2 entries, you have basically 2 ways to give it as an input :
\li You can program it, either using the Lua console (\ref MSG_Lua_funct) or if you're using MSG some
-of its platform and deployments functions(\ref msg_easier_life). If you want to use it, please refer
+of its platform and deployments functions(\ref msg_simulation). If you want to use it, please refer
to its doc. (you can also check the section \ref pf_flexml_bypassing but this is strongly deprecated, as there is a new way to do it properly, but not yet documented).
\li You can use two XML files: a platform description file and a deployment
description one.
availability changes over time using the availability_file
attribute and a separate text file whose syntax is exemplified below.
+
+<b>IMPORTANT NOTE:</b> the numeric separator in both trace and availability depends on your system locale. Examples below holds for LC_NUMERIC=C.
+
+
<b>Adding a trace file</b>
\verbatim
<platform version="1">
\subsection pf_storage Storage
<b>Note : This is a prototype version that should evolve quickly, this is just some doc valuable only at the time of writing this doc</b>
-This section describes the storage management under SimGrid ; nowadays it's only usable with MSG. It relies basically on linux-like concepts. You also may want to have a look to its corresponding section in \ref m_file_management ; functions access are organized as a POSIX-like interface.
+This section describes the storage management under SimGrid ; nowadays
+it's only usable with MSG. It relies basically on linux-like concepts.
+You also may want to have a look to its corresponding section in \ref
+msg_file_management ; functions access are organized as a POSIX-like interface.
\subsubsection pf_sto_conc Storage Main concepts
Basically there is 3 different entities to know :
