Hi,While going through ideas , I found this idea , Classical Mechanics: Efficient Equation of Motion Generation with Python, very appealing . I wanted to know if this idea is outdated or is being considered for this year's GSoC .
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/sympy/7f6f725c-a4a0-4c11-895b-a4eb1e83f837n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAP7f1AgguJTXrTiNpZVS-oe9-jT8BjeSqRiJRPCmbhj4mC4b5A%40mail.gmail.com.
On Sun, Feb 7, 2021 at 2:24 PM Jason Moore <moore...@gmail.com> wrote:
Sudeep,The topics related to sympy.physics.vector/mechanics are still possibilities. I will have time to mentor this summer if someone wants to do projects in this realm.We have not updated the ideas page yet for this year so those could be adjusted. Off the top of my head here are some things that I think are priorities:- Finish and enhance the work of Sahil Shekhewat so that models can be built with body and joint specifications (unmerged GSOC work).- Finish and enhance the work of James Milam (jbm950) that adds a FeatherstoneMethod. This is one way to increase the computational efficiency. One thing that is missing are nice implementations of spatial vectors and their operators.- Finish and enhance the work of Nikhil Pappu. The Autolev parser needs to be battle tested on some examples and bugs worked out. We need the tests in the private gitlab repo to actually be run by SymPy. (merged, but not polished GSOC work).- The Linearizer class was updated by James Crist, but I think it is effectively broken for more complex problems. This needs to be fixed and we need examples of it working for systems with holonomic and nonholonomic constraints.- Improve symbolic computational speed. Hard examples need to be profiled and the Python implementations improved, work on the core differentiation algorithms to maximize speed, and ensure that optional dependencies on symengine function and help for hard problems.- Develop a more comprehensive set of examples. I've started creating more and migrating threse to the PyDy documentation: https://pydy.readthedocs.io/en/latest/#examples. One barrier to user adoption is the lack of examples that are clearly written that cover all types of dynamic systems.- I've recently discovered that for some problems the resulting symbolic equations are in a form that results in numerical error accumulation in the arithmetic. This is problematic and figuring out what this issue is and remedying it would be a nice improvement.- All of these PRs are hanging: https://github.com/sympy/sympy/pulls?q=is%3Aopen+is%3Apr+label%3Aphysics.mechanics and it would be nice to resolve them and get them merged.- If work can be done on PyDy, as has in the past, there are several things there too 1) support DAEs, 2) improve the visualizer in a number of ways, 3) migrate examples to jupyter-sphinx, etc.At this point, I'm generally in disfavor of proposing any new features or extensions to the library over fixing and improving what we already have. As you can see, we have several GSoC projects that were not fully polished off or were not merged at all.Jason
--
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.
I would like to know if the idea, Continuum Mechanics: Create a Rich 2D Beam Solving System, will be considered this time or not.I would also like to know if it is better to
- implement more features in the existing beam module
- Or expand the continuum mechanics module to implement other structures like trusses and frames.
To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/4dfce88f-13ac-4b8f-a295-e3db775ca74cn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CANV73fFWXeJqWNe8PWm4y5GC2F0%3DJyiNoN-HCz_uGnGfBx%3DZMw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/46e97251-1908-4bc4-af73-20faba189babn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAP7f1AirYPVS0vaN-kxmw%2BbqzHfwTA%2BRB0SmP7cU9BEQ-aPGgA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CANV73fFijGVbjwPaOx0OKh4fDtHYKqV01rj_TQp4tL3VVpc%3D%2Bw%40mail.gmail.com.
Jason,
I would definitely like to work on physics mechanics/vectors project in this summer as physics has been my favourite subject and I'm really eager to learn more physics to code it and I think I can learn it myself while coding plus you could help me if I get stuck somewhere.So which would be better to implement first, spatial vector or Featherstone method? If possible can you please share notes or pdf link of related topic as it would be nice to have a headstart.
To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAJUjCNkE5y8EHxhG1XhfsFQax05SognCNM_5zPGR72JYaVffvg%40mail.gmail.com.
James worked with Featherstone's book "Rigid Body Dynamics Algorithms". But I think that the spatial vector implementation used in simbody may be a good thing to copy.I also think that focusing on improving end-user use of the software is more bang for the buck and adding the Featherstone algorithm doesn't add much for general users.Jason
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAJUjCNnZaG17SAshVAVANcMbUMiGMKD4-Y0sr02TVfjZGhgsDQ%40mail.gmail.com.
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAJUjCNnYjAqYz6z_sSum_-WLAGwP0FNotfSQvwxotNKcqqqs_A%40mail.gmail.com.
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAJUjCNmYppkxNO91SpEuMBXhbbHx26bnWF8-ioxA5NiECuWtFg%40mail.gmail.com.
Sudeep,We don't tell you what is "good to go". Every applicant can propose whatever they want. The applications are judged on the scope, the likelihood of success, the writer's communication, alignment with sympy's roadmap, and their applicant's interaction with the community.Jason--On Wed, Feb 10, 2021 at 4:07 PM Sudeep Sidhu <sudeepma...@gmail.com> wrote:Jason,--I'll surely look into it.So is JointsMethod good to go as GSoC project?On Wed, 10 Feb 2021, 19:15 Jason Moore, <moore...@gmail.com> wrote:Sudeep,The only thing I can think of to look it is how people do this in other dynamics software. Many of them let the user define a system based on descriptions of rigid bodies and different joint types. That description is the used to define the mathematics of the kinematics. The software Simbody does it, for example: https://github.com/simbody/simbody You can see that the concept of a "mobilizer" is used.Jason
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 view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAJUjCNmYppkxNO91SpEuMBXhbbHx26bnWF8-ioxA5NiECuWtFg%40mail.gmail.com.
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 view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAP7f1AhSTDWC2n-z5h-jCLugdrvqPNMMWa96ck27E2Y-ttbJjQ%40mail.gmail.com.
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAJUjCN%3DNo%2BonpynE4PqsL%3Dk_%2BZF1e9-_kWr%3Do9ivgf%2B8xr17qg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAP7f1AirRMUN%3DYbdbjtTiuvwg3isUSSP28ziywQ6toLc_YZt-Q%40mail.gmail.com.
So shall I create a new wiki page for 2021 proposals on sympy repository and share my google docs link there as done in previous years?
--On Sat, 13 Mar 2021, 16:58 Jason Moore, <moore...@gmail.com> wrote:Sudeep,Please see the GSoC instructions: https://github.com/sympy/sympy/wiki/GSoC-Student-Instructions. We recommend the wiki.Jason--On Fri, Mar 12, 2021 at 1:39 PM Sudeep Sidhu <sudeepma...@gmail.com> wrote:Jason,--I have prepared my draft proposal for GSoC'21. Where shall I share it so that you and others can review it.Sudeep Sidhu
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 view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAJUjCN%3DNo%2BonpynE4PqsL%3Dk_%2BZF1e9-_kWr%3Do9ivgf%2B8xr17qg%40mail.gmail.com.
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 view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAP7f1AirRMUN%3DYbdbjtTiuvwg3isUSSP28ziywQ6toLc_YZt-Q%40mail.gmail.com.
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 view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAJUjCNkDNmjhA%3DD85C9NBfWiS02S4Tkf-8vkf6hh3tDws_vqyA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CALkUZDmtmaDrQd2JpLSEyG7uSWXpqdTYhhvkXUrHLXDEZmakQQ%40mail.gmail.com.
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAJUjCN%3D2tJ35-q8TDtP9ynuOL12veroncDqXgX4rrq1d_nP4dw%40mail.gmail.com.