Aaron, Just to reiterate Luke some: We've been working on a vision of a domain specific tool chain based primarily in the scientific Python ecosystem that will allow us to do multibody dynamics and control work. One of the most important pieces is the core that we've developed in SymPy with you all's help (the mechanics package). We plan to continue to develop that and work on core pieces of SymPy to improve package and we hope that the work that branches into the core of SymPy (code gen, cse, plotting, etc) will be beneficial to all of SymPy. But we will soon be developing some parts of this tool chain that rely more on other software or that don't fit into SymPy's mission (we'll pitch these as the time comes to see where the best home is for them).
So, we're hoping to help potential GSoC applicants that are interested in our vision submit applications to both SymPy and other relevant projects this year. We may also apply to be a mentoring organization ourselves so that we can better facilitate that, but I'm not sure of the likelihood that we will be accepted. Never-the-less SymPy will have our help in development work and mentorship roles in the far foreseeable future. We would surely not be in the position to broaden our vision if SymPy hadn't taken us under their wing. Let us know if you have any thoughts on this plan. Jason On Monday, February 25, 2013 10:04:30 AM UTC-8, Luke wrote: > > On Sat, Feb 23, 2013 at 3:32 PM, Aaron Meurer > <asme...@gmail.com<javascript:>> > wrote: > > pydy.org gives a 404. You might want to fix that. > > I'm not sure why pydy.org was 404'ing, it is fine now. It is hosted > on a AWS t1.micro instance, so maybe it just got briefly overloaded. > > > You should also contact the SymPy list, as they will probably be the > > mentoring organization that you will apply to (unless you guys have > > some project that would live outside the SymPy code base, in which > > case, it can possibly also go under the umbrella of another project, > > such as Python). > > With regards to the mentoring organization, we are interested in > development of some things which are related to > sympy.physics.mechanics but are not symbolic in nature and as such > might not make sense to be part of sympy. Where the boundary is > exactly I am not certain, but I think the line is probably somewhere > near the point where sympy expressions get output as C code that is > then compiled to do some sort of numerical study. We have some ideas > of things we'd like to do be able to (in a generic sense) with this > numerical code, and it doesn't seem like this belongs in sympy. So we > were considering creating a project that depends on sympy and > specifcally sympy.physics.mechanics but isn't necessarily part of it. > This has code maintenance issues though, so we should verify that this > is absolutely necessary before we go this route. > > If people have thoughts on this, I would love to hear them. > > > You should also read > > https://github.com/sympy/sympy/wiki/GSoC-2013-application-template. In > > particular, we require at least one patch to SymPy to be accepted. > > Definitely. > > > By the way, can you guys make sure that > > https://github.com/sympy/sympy/wiki/GSoC-2013-ideas is up-to-date with > > all the potential ideas for the mechanics module? > > I have added a few ideas related to the sympy.physics.mechancis to the > bottom of the GSoC-2013 ideas list. I have added my name to the list > of potential mentors and would be interested in mentoring something > related to common subexpression elimination or > sympy.physics.mechanics. > > Luke > -- 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 sympy+unsubscr...@googlegroups.com. To post to this group, send email to sympy@googlegroups.com. Visit this group at http://groups.google.com/group/sympy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
