Thanks for the information Sachin. I will take a look at the code. -Meghana
On Thursday, February 11, 2016 at 4:33:12 PM UTC+5:30, Sachin Joglekar wrote: > > Implementing vector integration would be good. To replace physics.vector, > you would need to write a sub-library (mostly in sympy.physics), that would > build on top of sympy.vector by adding time-dependent variables. Have a > look at the code of physics.vector module, to get an idea of the > functionality you would need to build. I had written code > <https://github.com/sympy/sympy/pull/2187/files> during GSoC 2013 to > implement a Reference Frame on top of a simple vector module. That could be > a starting point for you to design your potential work. While writing your > proposal, get acquainted with the basic examples in physics.mechanics. This > will help you make sure that your module satisfies all the current > requirements of the mechanics package. > > On Thursday, February 11, 2016 at 3:29:51 PM UTC+5:30, > meghana.m...@gmail.com wrote: >> >> Jason, >> >> Thanks for the information. From what I have gathered, (from going >> through the sympy.physics.vector package and wiki pages on the vector >> module) , it seems like some of the functions involving kinematics have not >> been implemented yet in the sympy.vector package. Is this a possible thing >> to work on ? (if sympy.physics.vector package is to be replaced with >> sympy.vector, these need to be implemented). Am I missing out on something >> ?Are there other things that need to be changed in sympy.vector ? >> >> -Meghana >> >> On Thursday, February 11, 2016 at 1:34:09 AM UTC+5:30, Jason Moore wrote: >>> >>> Meghana, >>> >>> One long term goal is to remove the sympy.physics.vector package and >>> replace it with more general one, i.e. sympy.vector. >>> >>> Jason >>> >>> >>> Jason >>> moorepants.info >>> +01 530-601-9791 >>> >>> On Wed, Feb 10, 2016 at 11:56 AM, <meghana.m...@gmail.com> wrote: >>> >>>> Hi everyone, >>>> I wanted to know what the TODOs are for the vector module. I would like >>>> to work on vector integration and would be applying for GSoC 2016 for the >>>> same. However, just implementing vector integration is not sufficient work >>>> for an entire summer (as pointed out by Aaron). I would like to know if >>>> there are any related functionalities that are in the roadmap of the >>>> vector >>>> module that can be implemented in addition to vector integration for a >>>> summers worth of work. >>>> >>>> -Meghana >>>> >>>> -- >>>> 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. >>>> To post to this group, send email to sy...@googlegroups.com. >>>> Visit this group at https://groups.google.com/group/sympy. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/sympy/3537c662-a397-4963-8441-5742d6e80e04%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/sympy/3537c662-a397-4963-8441-5742d6e80e04%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- 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 https://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/7d3f6466-e623-4e4d-a242-75436731e302%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
