X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/dfe09e5c06ea550bdd21bc6ec3ea1a26d58569ec..52fd53c1927b271828348841b782281f64b7bef8:/doc/doxygen/outcomes_vizu.doc
diff --git a/doc/doxygen/outcomes_vizu.doc b/doc/doxygen/outcomes_vizu.doc
index d8a7ad3267..1c4381c20b 100644
--- a/doc/doxygen/outcomes_vizu.doc
+++ b/doc/doxygen/outcomes_vizu.doc
@@ -121,9 +121,8 @@ tracing/uncategorized
tracing/filename
:
A file with this name will be created to register the simulation. The file
- is in the Paje format and can be analyzed using Viva or Paje visualization
+ is in the Paje format and can be analyzed using Paje visualization
tools. More information can be found in these webpages:
- http://github.com/schnorr/viva/
http://github.com/schnorr/pajeng/
\verbatim
--cfg=tracing/filename:mytracefile.trace
@@ -202,7 +201,7 @@ TODO
\endverbatim
\li \c
-tracing/msg/vm
+tracing/vm
:
TODO
\verbatim
@@ -326,24 +325,6 @@ TODO
TODO
\endverbatim
-\li \c
-viva/categorized
-:
- This option generates a graph configuration file for Viva considering
- categorized resource utilization.
-\verbatim
---cfg=viva/categorized:graph_categorized.plist
-\endverbatim
-
-\li \c
-viva/uncategorized
-:
- This option generates a graph configuration file for Viva considering
- uncategorized resource utilization.
-\verbatim
---cfg=viva/uncategorized:graph_uncategorized.plist
-\endverbatim
-
Please pass \verbatim --help-tracing \endverbatim to your simulator
for the updated list of tracing options.
@@ -362,7 +343,6 @@ simulator):
--cfg=tracing:yes \
--cfg=tracing/uncategorized:yes \
--cfg=tracing/filename:mytracefile.trace \
- --cfg=viva/uncategorized:uncat.plist
\endverbatim
\li I want to trace only a subset of my MSG (or SimDAG) tasks.
@@ -377,7 +357,6 @@ recompiling, run your simulator with the following parameters:
--cfg=tracing:yes \
--cfg=tracing/categorized:yes \
--cfg=tracing/filename:mytracefile.trace \
- --cfg=viva/categorized:cat.plist
\endverbatim
@@ -453,23 +432,6 @@ several options to analyze this trace file:
file format. Consider this option if you need to understand the
causality of your distributed simulation.
-- Visualize the behavior of your simulation with treemaps (specially
- if your simulation has a platform with several thousand resources),
- provided by the Viva
- visualization tool. See Viva's wiki for
- further details on what is a treemap and how to use it.
-
-- Correlate the behavior of your simulator with the platform topology
- with an interactive, force-directed, and hierarchical graph
- visualization, provided by Viva. Check Viva's wiki for
- further details. This research report,
- published at ISPASS 2013, has a detailed description of this
- visualization technique.
-
- You can also check our online tutorial
section that contains a dedicated tutorial with several
@@ -484,123 +446,4 @@ several options to analyze this trace file:
href="http://lists.gforge.inria.fr/pipermail/simgrid-user/">mailing
list archive for old messages regarding tracing and analysis.
-\subsection tracing_viva_analysis Viva Visualization Tool
-
-This subsection describe some of the concepts regarding the Viva Visualization Tool and
-its relation with SimGrid traces. You should refer to Viva's website
-for further details on all its visualization techniques.
-
-\subsubsection tracing_viva_time_slice Time Slice
-
-The analysis of a trace file using the tool always takes into account
-the concept of the time-slice. This concept means that what
-is being visualized in the screen is always calculated considering a
-specific time frame, with its beggining and end timestamp. The
-time-slice is configured by the user and can be changed dynamically
-through the window called Time Interval that is opened
-whenever a trace file is being analyzed. Users are capable to select
-the beggining and size of the time slice.
-
-\subsubsection tracing_viva_graph Hierarchical Graph View
-
-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 Property List
-Format to describe the configuration) can be created for any
-SimGrid-based simulator using the
---cfg=viva/uncategorized:graph_uncategorized.plist or
---cfg=viva/categorized:graph_categorized.plist (if the
-simulator defines resource utilization categories) when executing the
-simulation.
-
-\subsubsection basic_conf Basic Graph Configuration
-
-The basic description of the configuration is as follows:
-\verbatim
-{
- node = (LINK, HOST, );
- edge = (HOST-LINK, LINK-HOST, LINK-LINK, );
-\endverbatim
-
-The nodes of the graph will be created based on the node
-parameter, which in this case is the different "HOST"s and
-"LINK"s of the platform used to simulate. The edge
-parameter indicates that the edges of the graph will be created based
-on the "HOST-LINK"s, "LINK-HOST"s, and
-"LINK-LINK"s of the platform. After the definition of these
-two parameters, the configuration must detail how the nodes
-(HOSTs and LINKs) should be drawn.
-
-For that, the configuration must have an entry for each of
-the types used. For HOST, as basic configuration, we have:
-
-\verbatim
- HOST = {
- type = square;
- size = power;
- values = (power_used);
- };
-\endverbatim
-
-The parameter size indicates which variable from the trace
-file will be used to define the size of the node HOST in the
-visualization. If the simulation was executed with availability
-traces, the size of the nodes will be changed according to these
-traces. The parameter type indicates which geometrical shape
-will be used to represent HOST, and the values parameter
-indicates which values from the trace will be used to fill the shape.
-
-For LINK we have:
-
-\verbatim
- LINK = {
- type = rhombus;
- size = bandwidth;
- values = (bandwidth_used);
- };
-}
-\endverbatim
-
-The same configuration parameters are used here: type (with a
-rhombus), the size (whose value is from trace's bandwidth
-variable) and the values.
-
-\subsubsection custom_graph Customizing the Graph Representation
-
-Viva is capable to handle a customized graph representation based on
-the variables present in the trace file. In the case of SimGrid, every
-time a category is created for tasks, two variables in the trace file
-are defined: one to indicate node utilization (how much power was used
-by that task category), and another to indicate link utilization (how
-much bandwidth was used by that category). For instance, if the user
-declares a category named request, there will be variables
-named prequest and a brequest (p
-for power and b for bandwidth). It is important to notice that
-the variable prequest in this case is only available for HOST,
-and brequest is only available for LINK. Example:
-suppose there are two categories for tasks: request and compute. To
-create a customized graph representation with a proportional
-separation of host and link utilization, use as configuration for HOST
-and LINK this:
-
-\verbatim
- HOST = {
- type = square;
- size = power;
- values = (prequest, pcomputation);
- };
- LINK = {
- type = rhombus;
- size = bandwidth;
- values = (brequest, bcomputation);
- };
-\endverbatim
-
-This configuration enables the analysis of resource utilization by MSG
-tasks through the identification of load-balancing issues and network
-bottlenecks, for instance.
-
*/