lmm_solve (experts only; check the code for more info).
If you compiled SimGrid accordingly, you can use packet-level network
-simulators as network models (see \ref pls). In that case, you have
+simulators as network models (see \ref pls_ns3). In that case, you have
two extra models, described below, and some \ref options_pls "specific
additional configuration flags".
- - \b NS3: Network pseudo-model using the NS3 tcp model instead of an
- analytic model
+ - \b NS3: Network pseudo-model using the NS3 tcp model
Concerning the CPU, we have only one model for now:
- \b Cas01: Simplistic CPU model (time=size/power)
\section options_tracing Configuring the tracing subsystem
-The \ref tracing "tracing subsystem" can be configured in several
+The \ref outcomes_vizu "tracing subsystem" can be configured in several
different ways depending on the nature of the simulator (MSG, SimDag,
SMPI) and the kind of traces that need to be obtained. See the \ref
tracing_tracing_options "Tracing Configuration Options subsection" to
equal to 1.
Of course, you can set any arbitrary filenames you want (so the start and end don't have to be
-in the same file), but be aware that this mechanism only supports \i consecutive calls!
+in the same file), but be aware that this mechanism only supports @em consecutive calls!
\note
Please note that you must pass the \b -trace-call-location flag to smpicc
