[SciPy-Dev] Thoughts on creating a toolbox for analysis of nonlinear dynamical system analysis

[Ilhan Polat]

My problem with nonlinear tools is that they are exceedingly generic; even
the name itself "anything not linear". This applies particularly to
dynamics and control. Many attempts get overwhelmed quickly over the
generalness though I wholeheartedly agree with the sentiment. A non-GUI,
simulink-like tool would be great indeed.

If the scope gets narrower and it does one thing or two sufficiently well
and quick then it might(!) find a place in, say, sp.integrate or sp.signal.
but otherwise it would be indeed out of scope.

Pydstool or BMSpy require really dedicated contributors because of the
specialization needed to improve the code. Hence my jerk knee response
would be first to get their reaction about the roadmap they have in mind.


On Fri, Mar 23, 2018, 16:40 Joseph Slater <joseph.c.slater at gmail.com> wrote:

>
>
> > On Mar 23, 2018, at 11:28 AM, Ralf Gommers <ralf.gommers at gmail.com>
> wrote:
> >
> >
> >
> > On Fri, Mar 23, 2018 at 8:24 AM, Sayantan Majumdar <
> emailforsayantan at gmail.com> wrote:
> > I work with Nonlinear Dynamical Systems and there are no good toolboxes
> that provide fast and stable tools for the analysis of such systems.
> >
> > there were a lot of good toolboxes in the 80's( I heard ) and there are
> some packages where those algorithms have been re-implemented and sometimes
> used, like the PyDSTool package.But its too slow and everything is not
> stable in it plus some important tools are not there.
> >
> > This can be a good thing to start in this gsoc right?
> >
> > No, that's not a good topic for GSoC, because it's too large in scope
> and because there's no mentoring project for it if you try to start
> something from scratch.
> >
> > Ralf
> >
>
> I concur with Ralf, while also agreeing with the need. I have taken a
> small step with my package mousai which at this time is a rather limited
> harmonic balance solver that certainly needs improvements for greater
> robustness (on github, and pypi- https://josephcslater.github.io/mousai/).
> I have spent more time adding issues than anything else lately. I would
> certainly welcome anyone who wants to join forces. At some time, merging
> into scipy would be a goal, but I don't believe that it's worthy right now.
>
> Ralf: There was a recent discussion on the frustrations of lack of SciPy
> contributors- mousai is an example, along with my other projects, some more
> relevant to potential future inclusion in SciPy, some less.
>
> I'm concerned with PyDSTool: I don't know that it is being maintained, and
> my observation was that the overhead for being able to use it is very high.
> My interest would be in connecting aerodynamic and structural codes (likely
> commercial) together. These could include millions of states. PyDSTool
> seemed to me to expect hand coded equations a bit much. Maybe it's just me,
> but it looks great but I thought the overhead to get into using it was
> off-putting for most engineers/students.
>
> Joe
>
>
>
>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at python.org
> https://mail.python.org/mailman/listinfo/scipy-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20180323/f4081a36/attachment.html>