|
|
|
|
Subject: RE : tracking computing time
From: christophe LE PAGE (le_page@cirad.fr)
Date: Sun Oct 01 2006 - 11:21:11 CEST
Dear Paul,
For questions out of the scope of Cormas, please use directly VisualWorks
mailing list (http://wiki.cs.uiuc.edu/VisualWorks/vwnc+mailing+list)
A very useful resource!
Clp
> -----Message d'origine-----
> De : owner-cormas@cirad.cirad.fr [mailto:owner-cormas@cirad.cirad.fr] De
> la part de Paul Caplat
> Envoyé : samedi 30 septembre 2006 01:50
> À : Mehdi Saqalli; christophe.le_page@cirad.fr; cormas@cirad.fr
> Objet : Re: tracking computing time
>
> Dear Mehdi and All,
> I am pretty sure the AT profiling is an amazing tool, but I don't know
> why (mac user fate ?) I cannot load the AT profiling UI parcel
> ("format not valid"), and the "Tools ->Advanced" menu is grayed.
>
> I have even installed VW again, but nothing changes.
> Help !!!!!!!!!!
>
> Paul
>
> 2006/9/29, Mehdi Saqalli <msqalli@yahoo.com>:
> > A VERY USEFUL TOOL: I should recommend this. it works beyond my
> expectations
> > !!
> > due certainly because of my non-programming background, I've had let
> several
> > functions working in the program for no use and spending plenty of CPU
> !!!
> > It definitely increase the speed of the program and then may be i'll
> have my
> > phD...
> > thanks "Hristof The Horseman ?"
> >
> > Christophe Le Page <christophe.l@chula.ac.th> a écrit :
> > As the reference manual for "Advanced Tools" exists, I'll just make use
> of
> > the rude acronym RTFM…
> > So please have a look, in the "doc" directory of your VW installation
> > directory, at the file "ToolGuide.pdf", chapter "System Profilers",
> section
> > "Analysing the profiler report".
> > HTH (nicer acronym ;->) !
> >
> > I'm quite sure that displaying the spatial grid window is VERY
> > time-consuming, so for long and big simulations, it has to be closed. As
> for
> > the "simulation panel control" window, even if the current time step is
> > redisplayed at each time step, I would be very surprised that this is
> > causing the major pb you are mentionning.
> > But bur all the other Cormas GUI windows, fixed, I really don't believe
> they
> > can consume time during a simulation run. What about probes, especially
> if
> > you save them in a local file?
> >
> > By the way, here is one way to investigate more deeply the distribution
> of
> > the computing time used during one time step of your cormas model:
> > 1. Load the parcel "AT Profiling" from VisualWorks main menu
> > 2. Select "Tools -> Advanced -> Profiles -> Time" from VisualWorks
> > main menu: it opens a code editor window called "profile execution
> time".
> > Read the explanations and do the 3 tests to understand how this tool
> > operates
> > 3. Initialize your cormas model
> > 4. In the "profile execution time" window, enter, select then
> evaluate
> > the code below:
> > |c|
> > c := CormasNS.Kernel.Cormas allInstances first.
> > self profile: [c runStepByStep]
> > Bonne traque!
> >
> >
> > I would be curious to know if you get drastic changes when including a
> > first instruction in your scheduling method
> > step: t
> > t = 1 ifTrue: [self simManager cormas simulationWin close].
> > ...
> >
> > ________________________________
> > Découvrez un nouveau moyen de poser toutes vos questions quelque soit
> le
> > sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos
> > opinions et vos expériences. Cliquez ici.
> >
> >