Cool. I like where this is going. You might want to see if you can get access to https://github.com/pydy somehow (or is that already you guys who own that?).
Aaron Meurer On Feb 25, 2013, at 5:19 PM, Gilbert Gede <gilbertg...@gmail.com> wrote: I added a few more points to our entry on the Ideas page, and my name as a mentor. We came up with a rough roadmap for PyDy (http://pydy.org/roadmap), and I actually think there is enough work for a student's GSoC project that would be entirely within SymPy. That being said though, at this point it would be more beneficial (for both groups) to do some work on things outside the SymPy codebase. There's quite a bit of work to go on bringing physics.mechanics from where it is now to where it is accessible by "the masses", which would increase visibility for SymPy. We should probably put "Powered by SymPy", or something like that, on the PyDy page, and try and show of some of SymPy's non-mechanics abilities within the PyDy examples. But for now (this year), I agree that work on PyDy could still be a SymPy project. -Gilbert On Monday, 25 February 2013 12:31:54 UTC-8, Aaron Meurer wrote: > > On Feb 25, 2013, at 11:04 AM, Dale Lukas Peterson > <hazel...@gmail.com<javascript:>> > 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. > > This is a great example of what Matthew suggested earlier on this list > about using GSoC to support external projects that use SymPy. So even > if most of the code doesn't directly go in SymPy, we could still > consider "hosting" such a project. If it really is completely separate > from SymPy (except for the inevitable bug fix patches to SymPy), you > might want to have the student also apply to Python. Then they will > have a better chance of being accepted regardless of how the slots > work out. If you do decide to go this route, you should decide soon, > as Python requires orgs that they umbrella to apply to them. > > Aaron Meurer > > > > >> 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+un...@googlegroups.com <javascript:>. > > To post to this group, send email to sy...@googlegroups.com<javascript:>. > > > Visit this group at http://groups.google.com/group/sympy?hl=en. > > 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 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. -- 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.
