-
Notifications
You must be signed in to change notification settings - Fork 546
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
Exception when using persistent roadmaps #1303
Comments
I am also facing a similar issue, but while attempting to use AnytimePathShortening |
I figured it out! Config parsing in the planning pipeline is unable to parse This can be gotten around by using |
The documentation was fixed here: moveit/moveit2_tutorials#460 I'm going to close the issue now. Thanks for tracking this down! |
Sorry for replying so late. I tried your solution @FarisHamdi and it works perfectly. Thank you! |
Description
I am currently using Moveit2 in combination with ROS Foxy to control a Universal Robot UR10e. The purpose is to try different planning algorithms for trajectory generation and validate them.
So far everything worked fine more or less (had some build problems). Then I found the feature of persistent roadmaps which came with OMPL 1.5.0 which I wanted to try of course. After adapting the ompl_planning.yaml accordingly I tried planning with the new planner but got a screen full of exceptions produced by Moveit.
This is my first report, so please excuse any mistakes or missing information and let me know. Also tips for improvements are welcome.
My environment
Steps to reproduce
So my ompl_planning.yaml looks like:
Rebuilding the corresponding package ur_moveit_config
Start my Robot Control driver in simulation mode which I have from: https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver
ros2 launch ur_bringup ur_control.launch.py ur_type:=ur10e use_fake_hardware:=true launch_rviz:=false
Start Moveit with Rviz:
ros2 launch ur_bringup ur_moveit.launch.py ur_type:=ur10e use_fake_hardware:=true launch_rviz:=true
Expected behaviour
Actual behaviour
Backtrace or Console output
If you wonder why there are no other planners in the ompl_planning.yaml, I removed them all just to be sure there is no error there. They work without any problems at all.
I also just kept:
But the error still occurs, so it must be the option multi_query_planning_enabled
Any ideas?
The text was updated successfully, but these errors were encountered: