-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add support for additional local planner algorithms #202
Comments
Some of those (RRT, potentially D*) are really much more effective global planners. RRTs aren't exactly fast unless you're caching things or precomputing. I might also recommend a simple carrot local planner. I have had one for personal use for some time, its not quite generalized enough for general use, but I can revisit it and see if that makes sense to place here. |
Good call on the carrot planner. Even if it doesn't push the envelope on the interfaces, it would make a good example planner, and might be actually useful in some simple use cases. |
That's generally the conventional "first step" when hacking any robot (mobile, arm, etc) to just make it track some arbitrary carrot pointer that can be changed on the fly. I think that's a generally good choice as an example, but really only useful to diff drive small robots (and even then, depending on feature set, only good for R&D). I can revisit my code for it and see if I can generalize it enough for this repo |
That would be great. Thanks! |
Removed RRT and D*Lite. |
Closing since this isn't addressing a specific need. Work on TEB is covered by other issues. |
* reduced resolution and changed topic name * more realistic max cutoff * prepare for use_sim_time * fix typo Co-authored-by: Johannes Plapp <johannes.plapp@logivations.com>
To ensure the navigation stack interfaces are complete and general enough, additional local planners that are substantially different from DWA should be ported to ROS2 and the new architecture.
Possibilities for consideration include:
The text was updated successfully, but these errors were encountered: