-
Notifications
You must be signed in to change notification settings - Fork 696
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
How to use InformedRRTstar in Moveit? #792
Comments
Thanks for reporting an issue. Because we're a volunteer community, providing a pull request with suggested changes is always welcomed. |
From a quick glance it seems not to be integrated yet. That's not very hard however. Please have a look at this commit moveit/moveit@51cff82 and try to do the same for InformedRRTstar. Then please open a pull request (PR) so everybody can enjoy it |
I have achieved to call InforemedRRTstar in moveit. But now I don't know which optimization_objective to choice. |
Please provide a PR to add InformedRRTstar so others can profit as well. I don't understand your question unfortunately but generally you can add the optimization_objective to your ompl_planning.yaml as you can see here: https://ros-planning.github.io/moveit_tutorials/doc/ompl_interface/ompl_interface_tutorial.html#ompl-optimization-objectives |
After few days research,I know that InformedRRTstar should choice "PathLengthOptimizationObjective" as optimization_objective in ompl_planning.yaml. InfomedRRTstar will use PathLengthDirectInfSampler as informed sample. But i encounter a problem: in the algorithm of PHS, the GoalSample should be used , but the goal state can not be sampled. |
Description
I want to use InformedRRTstar in moveit. How should I configure in moveit?
Your environment
Steps to reproduce
Tell us how to reproduce this issue. Attempt to provide a working demo, perhaps using Docker.
Expected behaviour
Tell us what should happen
Backtrace or Console output
Use gist.github.com to copy-paste the console output or segfault backtrace using gdb.
The text was updated successfully, but these errors were encountered: