\subsection tracing_tracing_enabling Enabling using CMake
-With the sources of SimGrid, it is possible to enable the tracing
-using the parameter <b>-Denable_tracing=ON</b> when the cmake is executed.
-The section \ref tracing_tracing_functions describes all the functions available
-when this Cmake options is activated. These functions will have no effect
-if SimGrid is configured without this option (they are wiped-out by the
+With the sources of SimGrid, it is possible to enable the tracing
+using the parameter <b>-Denable_tracing=ON</b> when the cmake is
+executed. The sections \ref instr_category_functions, \ref
+instr_mark_functions, and \ref instr_uservariables_functions describe
+all the functions available when this Cmake options is
+activated. These functions will have no effect if SimGrid is
+configured without this option (they are wiped-out by the
C-preprocessor).
\verbatim
\li \c TRACE_category_with_color(const char *category, const char *color)
\li \c MSG_task_set_category(m_task_t task, const char *category)
\li \c MSG_task_get_category(m_task_t task)
-
-\li <b>\c TRACE_sd_set_task_category (SD_task_t task, const char *category)</b>:
-This function should be called after the creation of a SimDAG task, to define the
-category of that task. The first parameter \c task must contain a task that was
-created with the function \c MSG_task_create. The second parameter
-\c category must contain a category that was previously defined by the function
-\c TRACE_category.
+\li \c SD_task_set_category(SD_task_t task, const char *category)
+\li \c SD_task_get_category(SD_task_t task)
\subsection instr_mark_functions Tracing marks functions
\li \c TRACE_declare_mark(const char *mark_type)
options accepted by the tracing system of SimGrid as of today, you
can use them by running your simulator with the <b>--cfg=</b> switch:
-\li <b>\c
+\li <b>\c
tracing
</b>:
Safe switch. It activates (or deactivates) the tracing system.
--cfg=tracing:1
\endverbatim
-\li <b>\c
+\li <b>\c
tracing/categorized
</b>:
It activates the categorized resource utilization tracing. It should
--cfg=tracing/categorized:1
\endverbatim
-\li <b>\c
+\li <b>\c
tracing/uncategorized
</b>:
It activates the uncategorized resource utilization tracing. Use it if
--cfg=tracing/uncategorized:1
\endverbatim
-\li <b>\c
+\li <b>\c
tracing/filename
</b>:
A file with this name will be created to register the simulation. The file
--cfg=tracing/onelink_only:1
\endverbatim
-\li <b>\c
+\li <b>\c
tracing/smpi
</b>:
This option only has effect if this simulator is SMPI-based. Traces the MPI
--cfg=tracing/smpi:1
\endverbatim
-\li <b>\c
+\li <b>\c
tracing/smpi/group
</b>:
This option only has effect if this simulator is SMPI-based. The processes
--cfg=tracing/smpi/group:1
\endverbatim
-\li <b>\c
+\li <b>\c
tracing/msg/process
</b>:
This option only has effect if this simulator is MSG-based. It traces the
--cfg=tracing/disable_destroy:1
\endverbatim
-\li <b>\c
+\li <b>\c
triva/categorized
</b>:
This option generates a graph configuration file for Triva considering
--cfg=triva/categorized:graph_categorized.plist
\endverbatim
-\li <b>\c
+\li <b>\c
triva/uncategorized
</b>:
This option generates a graph configuration file for Triva considering
For that, you will need to create tracing categories using the
<b>TRACE_category (...)</b> function (as explained above),
and then classify your tasks to a previously declared category
-using the <b>TRACE_msg_set_task_category (...)</b>
-(or <b>TRACE_sd_set_task_category (...)</b> for SimDAG tasks). After
+using the <b>MSG_task_set_category (...)</b>
+(or <b>SD_task_set_category (...)</b> for SimDAG tasks). After
recompiling, run your simulator with the following parameters:
\verbatim
./your_simulator \
m_task_t req2 = MSG_task_create("2nd_request_task", 10, 10, NULL);
m_task_t req3 = MSG_task_create("3rd_request_task", 10, 10, NULL);
m_task_t req4 = MSG_task_create("4th_request_task", 10, 10, NULL);
- TRACE_msg_set_task_category (req1, "request");
- TRACE_msg_set_task_category (req2, "request");
- TRACE_msg_set_task_category (req3, "request");
- TRACE_msg_set_task_category (req4, "request");
+ MSG_task_set_category (req1, "request");
+ MSG_task_set_category (req2, "request");
+ MSG_task_set_category (req3, "request");
+ MSG_task_set_category (req4, "request");
m_task_t comp = MSG_task_create ("comp_task", 100, 100, NULL);
- TRACE_msg_set_task_category (comp, "computation");
+ MSG_task_set_category (comp, "computation");
m_task_t finalize = MSG_task_create ("finalize", 0, 0, NULL);
- TRACE_msg_set_task_category (finalize, "finalize");
+ MSG_task_set_category (finalize, "finalize");
//(...)
special configurations tunned to SimGrid needs. This part of the documentation
explains how to configure and use Triva to analyse a SimGrid trace file.
-- <b>Installing Triva</b>: the tool is available in the Inria's Forge,
+- <b>Installing Triva</b>: the tool is available in the Inria's Forge,
at <a href="http://triva.gforge.inria.fr">http://triva.gforge.inria.fr</a>.
Use the following command to get the sources, and then check the file
<i>INSTALL</i>. This file contains instructions to install
--gc_apply Apply the configuration
--gc_hide Hide the GraphConfiguration window
\endverbatim
-Triva expects that the user choose one of the available options
+Triva expects that the user choose one of the available options
(currently <em>--graph</em> or <em>--treemap</em> for a visualization analysis)
and the trace file from the simulation.
the end (that depends on the time simulated by SimGrid). The middle of the
window, in the square named <i>Time Slice Configuration</i>, contains the
aspects related to the time-slice, including its <i>start</i> and its
-<i>size</i>. The gray rectangle in the bottom of this part indicates the
-<i>current time-slice</i> that is considered for the drawings. If the checkbox
+<i>size</i>. The gray rectangle in the bottom of this part indicates the
+<i>current time-slice</i> that is considered for the drawings. If the checkbox
<i>Update Drawings on Sliders Change</i> is not selected, the button
<i>Apply</i> must be clicked in order to inform triva that the
new time-slice must be considered. The bottom part of the window, in the space
For <em>LINK</em> we have:
-\verbatim
+\verbatim
LINK = {
type = rhombus;
size = bandwidth;
