From 217e8b24b05ec8de6f7a639fa02aa999a066e6e5 Mon Sep 17 00:00:00 2001 From: schnorr Date: Tue, 13 Apr 2010 09:41:35 +0000 Subject: [PATCH] removing old text about paje visualization git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@7546 48e7efb5-ca39-0410-a469-dd3cf9ba447f --- doc/FAQ.doc | 24 +----------------------- 1 file changed, 1 insertion(+), 23 deletions(-) diff --git a/doc/FAQ.doc b/doc/FAQ.doc index 6e5182f062..58ae53bbc5 100644 --- a/doc/FAQ.doc +++ b/doc/FAQ.doc @@ -72,29 +72,7 @@ filter (e.g. with bash): ./msg_test small_platform.xml small_deployment.xml 2>&1 | ../../tools/MSG_visualization/colorize.pl \endverbatim -We also have a more graphical output. Have a look at MSG_paje_output(). It -generates an input to Paje. -
-\htmlonly - -\endhtmlonly -
- -Visualization with Paje can be seen as a kind of postmortem -analysis. However, as soon as you start playing with big simulations, -you'll realize that processing such output is kind of tricky. There is -so much generic information that it is hard to find the information -you are looking for. - -As a matter of fact, logging really depends on simulations (e.g. what -kind of events is important...). That is why we do not propose a big -dump of your whole simulation (it would slow everything down) but give -you neat tools to structure you logs. Have a look at \ref XBT_log. In -fact, rather than a post-mortem analysis, you may want to do it on the -fly. The process you are running can do whatever you want. Have you -thought about adding a global structure where you directly compute the -information that are really important rather than writing everything -down and then processing huge files? +We also have a more graphical output. Have a look at section \ref faq_tracing. \subsection faq_C Argh! Do I really have to code in C? -- 2.20.1