file. Normally, the tracing considers all routes (no matter their
size) on the platform file to re-create the resource topology. If this
option is activated, only the routes with one link are used to
-register the topology within an AS. Routes among AS continue to be
+register the topology within a netzone. Routes among netzones continue to be
traced as usual.
\verbatim
--cfg=tracing/onelink-only:yes
\li <b>\c
tracing/precision
</b>:
-TODO
+This option determines the precision of timings stored in the trace file. Make sure
+you set \ref options_model_precision to at least the same value as this option! (Traces
+cannot be more accurate than the simulation; they can be less accurate, though.)
+
+The following example will give you a precision of E-10 in the trace file:
\verbatim
-TODO
+--cfg=tracing/precision:10
\endverbatim
\li <b>\c
\subsubsection tracing_viva_graph Hierarchical Graph View
-%As stated above (see section \ref tracing_tracing_analyzing), one
+As stated above (see section \ref tracing_tracing_analyzing), one
possibility to analyze SimGrid traces is to use Viva's graph view with
a graph configuration to customize the graph according to the
traces. A valid graph configuration (we are using the non-XML <a
