You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not an issue, but just wanted to say thanks for this library! As you saw I wrote python bindings for this library. Not sure exactly where this will lead, but at least I am very happy to be able to get about 250.000 solutions/second.
I am not sure exactly what I want to support. I see there is URDF support, but wanting to get rid of URDF files in my workflow was a prime motivation for me to move away from the ikfast libraries I was using. For now I will first use the library myself and see if there is any external interest. I might want to add support for external axes (linear tracks, rotary tables, positioners etc.), but still undecided on that. Also of interest is collision detection. I would be happy to discuss these topics some time
The text was updated successfully, but these errors were encountered:
Thanks for being interested in my project. rs-opw-kinematics uses three-number versioning, with the last digit incremented if there are no API changes, the middle digit if there are no breaking changes (features only added), and the last third digit when there are breaking changes. I do not think there will be a need for breaking changes anytime soon.
If you need changes to make your integration work easier, let me know. I am always ready to review and likely accept a good pull request or just describe the needed improvements.
The last version, 1.5.0, can return poses of the robot's intermediate joints. This is preparation for implementing collision detection and can also be used for robot rendering. I will use an existing Rust library to detect collisions.
Not an issue, but just wanted to say thanks for this library! As you saw I wrote python bindings for this library. Not sure exactly where this will lead, but at least I am very happy to be able to get about 250.000 solutions/second.
I am not sure exactly what I want to support. I see there is URDF support, but wanting to get rid of URDF files in my workflow was a prime motivation for me to move away from the ikfast libraries I was using. For now I will first use the library myself and see if there is any external interest. I might want to add support for external axes (linear tracks, rotary tables, positioners etc.), but still undecided on that. Also of interest is collision detection. I would be happy to discuss these topics some time
The text was updated successfully, but these errors were encountered: