[Ns-developers] simulator API roadmap
gjcarneiro at gmail.com
Wed Apr 7 07:01:01 PDT 2010
On Wed, Apr 7, 2010 at 12:38 PM, Mathieu Lacage <
mathieu.lacage at sophia.inria.fr> wrote:
> On Wed, 2010-04-07 at 10:54 +0100, Gustavo Carneiro wrote:
> > 3) late in 3.9, I would like to remove
> > Simulator::Next/RunOneEvent.
> > Why not make Simulator::RunOneEvent only available in a downcasted
> > class?
> Because it's easy to change pyviz to make it work with the new API
I'll defer judgment on that until pyviz is ported to the new API and tested.
I spent a lot of time thus far getting a smooth animation in pyviz, and
allow a setting to control simulation speed, and make sure the GUI doesn't
freeze when the simulation is too heavy to run in real-time. I definitely
do not have time in the near future to do this again from scratch with a new
> and I
> want to make sure that others will not do what pyviz does so that we
> don't get new code which does not work gratuitously with all schedulers.
> > I mean, the functionality is there, I don't see what maintenance
> > effort will be required to just make an existing method public...
> > I don't really care if PyViz works with real-time scheduler or mpi or
> > whatever; it's not supposed to work---or even needed to work---with
> > anything but the simplest scheduler.
> _I_ do care about making pyviz work with the other schedulers :)
> i.e., I have hacked it in the past to do just that for a couple of
That's interesting. Maybe I lack vision, but what are the reasons for using
other schedulers with pyviz? Pyviz is mainly a graphical debugging tool. I
don't understand what you gain by MPI or real-time scheduler (anything else
Gustavo J. A. M. Carneiro
INESC Porto, UTM, WiN, http://win.inescporto.pt/gjc
"The universe is always one step beyond logic." -- Frank Herbert
More information about the Ns-developers