-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running OMPL Using PyBind11 #449
Conversation
…Sailbot/sailbot_workspace into user/SPDonaghy/test-pybind11
This reverts commit d79836a.
Do you need anything from me on this? Or is it all working now? |
I still have issues accessing the classes and function from the pyompl module. If you are free could you help look through what could possibly causing this issue? If you're busy, then it's fine. I will be working on it on Saturday. |
I see you've made some changes Did it work before turning it into a cmake project? What are the steps to build the module now? |
To build sailompl, you just need to run tasks: build package - sailompl. Or Just run the build.sh script for sailompl to build the python bindings. Then you can just run ros2 launch or python3 and import sailompl |
I'll try reverting back to my last commit and see if I can get it working. I'll let you know! |
Is this the behavior we are looking for?
|
That looks good! We currently are not publishing desired heading as that is not yet fully implemented. |
Awesome ok I will test on rpi soon and then submit for review. |
I'm thinking to just have a short build script that builds the bindings and then creates a symlink to the bindings in the directories where ROS and Python look for python modules. Then just update a couple environment variables in .bashrc and it all works fine. |
PR #452 is a better implementation of OMPL bindings using PyBind11. Therefore, I will close this PR. |
Description
Verification
ros2 launch local_pathfinding main_launch.py
on RPIros2 launch local_pathfinding main_launch.py
on X86Resources
Extra Notes and Commands