X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/4687083c4888112c130c66c2a77e89b8b40e8c6d..2b42d41396af291a6b62bdb027f18e7d77f127f9:/doc/tracing.doc
diff --git a/doc/tracing.doc b/doc/tracing.doc
index a6f8857c16..c67ff5118b 100644
--- a/doc/tracing.doc
+++ b/doc/tracing.doc
@@ -575,37 +575,8 @@ visualization was generated with the following configuration:
\endhtmlonly
-- Understading Triva - colors: An important issue when using Triva is how
- to define colors. To do that, we have to know which variables are defined in
-the trace file generated by the SimGrid library. The parameter --list
-lists the variables for a given trace file:
-\verbatim
-$ Triva -l masterslave_forwarder.trace
-iFile
-c platform
-c HOST
-v power
-v is_slave
-v is_master
-v task_creation
-v task_computation
-v pcompute
-v pfinalize
-c LINK
-v bandwidth
-v latency
-v bcompute
-v bfinalize
-c user_type
-\endverbatim
-We can see that HOST has seven variables (from power to pfinalize) and LINK has
-four (from bandwidth to bfinalize). To define a red color for the
-pcompute and bcompute (which are defined based on user category
-compute), execute:
-\verbatim
-$ defaults write Triva 'pcompute Color' '1 0 0'
-$ defaults write Triva 'bcompute Color' '1 0 0'
-\endverbatim
-Where the three numbers in each line are the RGB color with values from 0 to 1.
+- Understading Triva - colors: Colors are now registered in
+trace files. See the tracing API to how to define them for your
+simulator.
*/
\ No newline at end of file