Hello everyone,
I have been contributing to SymPy and engaging with the community for a few months now. I’ve fixed bugs, participated in discussions, and opened issues. Thus I have gained some familiarity with the codebase, also I have been programming in Python for 2+ years.
I'm interested in contributing to SymPy Mechanics for GSoC 2025, specifically under the project "Classical Mechanics: Implement Wrapping Geometry and Pathways for Musculoskeletal Modeling" as listed on the ideas page.
I've been exploring and studying the existing WrappingCylinder and WrappingSphere classes, as well as the LinearPathway and ObstaclePathway. I believe a valuable addition would be:
Implementation Plan:
As with any software development endeavor, these additions will be accompanied by exhaustive tests, documentation and example usage.
I think these additions could significantly enhance the biomechanics modeling capabilities of SymPy, especially for musculoskeletal simulations.
I'd love to hear any feedback, especially on:
Would this contribution align well with SymPy's current roadmap? I'm open to any guidance or suggestions to refine my approach.
Thanks!
Rushabh Mehta
--
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 visit https://groups.google.com/d/msgid/sympy/48b5a2ee-ffe7-4085-811f-0139b583924dn%40googlegroups.com.
Hello Jason,
Thanks for pointing me towards OpenSim. It is an interesting tool, and I've spent some time researching it. I now have a much clearer understanding of the types of wrapping geometries and pathways commonly used in musculoskeletal models.
OpenSim supports several standard wrapping geometries such as:
In OpenSim, the shortest muscle path is calculated using a combination of points and wrapping geometries. It doesn't solve for the geodesic (shortest path on a curved surface) explicitly but instead uses a combination of line segments and wrap points, and then numerically computes everything needed.
How This Informs My Proposal
Given this, I think SymPy Mechanics can be enhanced in the following ways:
1. Expand WrappingGeometry to Support More Surfaces
2. Introduce GeodesicPathway for Shortest Path Calculation
3. Symbolic Force Calculation Along the Geodesic
Queries
My main concern at the moment is:
The feasibility of computing geodesics for non-trivial surfaces (like ellipsoids or tori) using SymPy's dsolve(). Is it powerful enough?Best regards,
Rushabh Mehta