I don't there is any way to know how active the development will be. We presented it at two conferences for the first time in the last couple of months and have some people showing interest because of that. But for now it is just the core devs side project and we use it in our research.
Jason moorepants.info +01 530-601-9791 On Tue, Aug 13, 2013 at 1:56 PM, Aaron Meurer <[email protected]> wrote: > It's not too hard to make Travis test against the git version of > SymPy, so that you will know right away when the tests break. We could > also add PyDy tests to our own Travis tests. > > The question I would ask is, how active do you expect the development > to be, especially after this summer? > > Aaron Meurer > > On Tue, Aug 13, 2013 at 11:33 AM, Jason Moore <[email protected]> > wrote: > > Yes, for now we could just package SymPy with PyDy as a git submodule. > Then > > change the namespace so you > > > > from pydy import ReferenceFrame, etc > > > > and > > > > from pydy.visualization import VisualizationFrame > > > > We'd still have: > > > > from sympy import symbols > > > > But at least it would be one package. > > > > > > Jason > > moorepants.info > > +01 530-601-9791 > > > > > > On Tue, Aug 13, 2013 at 12:39 PM, Chris Dembia <[email protected]> > wrote: > >> > >> Those 2 points are very interesting. > >> > >> Can we have two ways to obtain PyDy? Maybe using git submodules or > >> something? I know this could turn into a mess, as it potentially > requires > >> maintenance of two different code bases: > >> > >> sympy.physics.mechanics, which is PyDy without viz > >> > >> and PyDy, downloaded from pydy.org, etc., which contains VIZ. > >> > >> This seems to combine the best of both worlds (mainly: keeps us with > SymPy > >> but avoids bringing VIZ and javascript into SymPy), with the cost being > >> greater necessary maintenance. > >> > >> > >> On Tue, Aug 13, 2013 at 8:49 AM, Jason Moore <[email protected]> > wrote: > >>> > >>> I think a new PyDy distribution may be the way to go too, not sure > about > >>> the timing yet. We can still interact with SymPy and contribute just > as much > >>> as the past but we do throw away this feature of being part of SymPy: > >>> > >>> Any changes made to SymPy must pass our tests. > >>> > >>> This has been very valuable so far and relieves us from having to deal > >>> with the whole version deal (SymPy versions have historically come out > slow, > >>> but may change now that the process is mostly automated.). But we could > >>> setup tests in SymPy's Travis system for the PyDy package at least > till the > >>> SymPy API stablizes enough for us. > >>> > >>> I've noticed too how having this pydy viz project this summer feels > more > >>> lonely. The mailing list, the irc channel, and general chatter about > things > >>> is low because we have few members in pydy. As oppose to our > development > >>> happening in the SymPy realm and we get comments and contributions > from lots > >>> of people. > >>> > >>> > >>> > >>> Jason > >>> moorepants.info > >>> +01 530-601-9791 > >>> > >>> > >>> On Tue, Aug 13, 2013 at 11:42 AM, Chris Dembia <[email protected]> > >>> wrote: > >>>> > >>>> I vote option #3; a new distribution. > >>>> > >>>> Aside from testing, is the purpose of having pydy in sypmy the > >>>> visibility of the package? > >>>> > >>>> I feel that if we have a package that has dependencies that sympy, in > >>>> general, does not have, then we should not place that package within > sympy. > >>>> > >>>> The reason I vote for #3 is because if I were new to pydy, this is > how I > >>>> would want to obtain the software. I wouldn't want to download 2 > different > >>>> modules. > >>>> > >>>> > >>>> > >>>> > >>>> On Tue, Aug 13, 2013 at 7:09 AM, Jason Moore <[email protected]> > >>>> wrote: > >>>>> > >>>>> Once GSoC ends it will rely on a brand new vector calculus package > that > >>>>> Prasoon is working on, so not so stable. > >>>>> > >>>>> But right now, it relys on SymPy pieces like Symbol, taking > >>>>> derivatives, Matrices, substitutions and replacements. Gilber could > comment > >>>>> more fully as he knows the code base best. > >>>>> > >>>>> > >>>>> Jason > >>>>> moorepants.info > >>>>> +01 530-601-9791 > >>>>> > >>>>> > >>>>> On Tue, Aug 13, 2013 at 10:00 AM, Matthew Rocklin < > [email protected]> > >>>>> wrote: > >>>>>> > >>>>>> On what subset of SymPy does PyDy and sympy.mechanics rely? How > >>>>>> stable is this subset? > >>>>>> > >>>>>> > >>>>>> On Tue, Aug 13, 2013 at 8:53 AM, Jason Moore <[email protected]> > >>>>>> wrote: > >>>>>>> > >>>>>>> Tarun's making good progress on the pydy viz package. The python > code > >>>>>>> is basically done and he's working on the js stuff now. > >>>>>>> > >>>>>>> https://github.com/PythonDynamics/pydy-viz > >>>>>>> > >>>>>>> Couple of questions for the group: > >>>>>>> > >>>>>>> 1. Where should this package belong? > >>>>>>> > >>>>>>> Options are: > >>>>>>> > >>>>>>> in sympy.physics.mechanics > >>>>>>> in a standalone package (as it is now) > >>>>>>> in a new PyDy distribution that includes visualization as a package > >>>>>>> other > >>>>>>> > >>>>>>> These also beg the questions: > >>>>>>> > >>>>>>> - should we create a new PyDy package that has all the mechanics > code > >>>>>>> and the new stuff and make SymPy a dependency? > >>>>>>> - just push everything into sympy? (people have varying opinions on > >>>>>>> this practice) > >>>>>>> > >>>>>>> If we are in SymPy our tests are in SymPy, which is super > beneficial > >>>>>>> because we rely so heavily on SymPy's code base. It will be more > so once the > >>>>>>> new vector calc module is done. But there is also confusion > because we have > >>>>>>> two names: SymPy and PyDy and installation is weird. We are going > to > >>>>>>> continue to develop numerical and visualization related stuff that > doesn't > >>>>>>> really fit into SymPy's mission as a CAS, but you do find similar > stuff in > >>>>>>> Mathematica, for example. > >>>>>>> > >>>>>>> Any thoughts? > >>>>>>> > >>>>>>> Jason > >>>>>>> moorepants.info > >>>>>>> +01 530-601-9791 > >>>>>>> > >>>>>>> -- > >>>>>>> You received this message because you are subscribed to the Google > >>>>>>> Groups "sympy" group. > >>>>>>> To unsubscribe from this group and stop receiving emails from it, > >>>>>>> send an email to [email protected]. > >>>>>>> To post to this group, send email to [email protected]. > >>>>>>> Visit this group at http://groups.google.com/group/sympy. > >>>>>>> > >>>>>>> For more options, visit https://groups.google.com/groups/opt_out. > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> You received this message because you are subscribed to the Google > >>>>>> Groups "sympy" group. > >>>>>> To unsubscribe from this group and stop receiving emails from it, > send > >>>>>> an email to [email protected]. > >>>>>> To post to this group, send email to [email protected]. > >>>>>> Visit this group at http://groups.google.com/group/sympy. > >>>>>> > >>>>>> For more options, visit https://groups.google.com/groups/opt_out. > >>>>>> > >>>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> You received this message because you are subscribed to the Google > >>>>> Groups "PyDy" group. > >>>>> To unsubscribe from this group and stop receiving emails from it, > send > >>>>> an email to [email protected]. > >>>>> To post to this group, send email to [email protected]. > >>>>> Visit this group at http://groups.google.com/group/pydy. > >>>>> > >>>>> For more options, visit https://groups.google.com/groups/opt_out. > >>>> > >>>> > >>>> -- > >>>> You received this message because you are subscribed to the Google > >>>> Groups "PyDy" group. > >>>> To unsubscribe from this group and stop receiving emails from it, send > >>>> an email to [email protected]. > >>>> To post to this group, send email to [email protected]. > >>>> Visit this group at http://groups.google.com/group/pydy. > >>>> > >>>> For more options, visit https://groups.google.com/groups/opt_out. > >>>> > >>>> > >>> > >>> > >>> -- > >>> You received this message because you are subscribed to the Google > Groups > >>> "PyDy" group. > >>> To unsubscribe from this group and stop receiving emails from it, send > an > >>> email to [email protected]. > >>> To post to this group, send email to [email protected]. > >>> Visit this group at http://groups.google.com/group/pydy. > >>> For more options, visit https://groups.google.com/groups/opt_out. > >> > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "PyDy" group. > >> To unsubscribe from this group and stop receiving emails from it, send > an > >> email to [email protected]. > >> To post to this group, send email to [email protected]. > >> Visit this group at http://groups.google.com/group/pydy. > >> For more options, visit https://groups.google.com/groups/opt_out. > > > > > > -- > > You received this message because you are subscribed to the Google Groups > > "PyDy" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > To post to this group, send email to [email protected]. > > Visit this group at http://groups.google.com/group/pydy. > > For more options, visit https://groups.google.com/groups/opt_out. > > -- > You received this message because you are subscribed to the Google Groups > "PyDy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/pydy. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. For more options, visit https://groups.google.com/groups/opt_out.
