Skip to content
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

Closed
crdelsey opened this issue Oct 18, 2018 · 6 comments
Closed

Add support for additional local planner algorithms #202

crdelsey opened this issue Oct 18, 2018 · 6 comments
Labels
3 - Low Low Priority enhancement New feature or request

Comments

@crdelsey
Copy link
Contributor

crdelsey commented Oct 18, 2018

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:

@SteveMacenski
Copy link
Member

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.

@mkhansenbot mkhansenbot added the enhancement New feature or request label Oct 18, 2018
@mkhansenbot mkhansenbot added this to To do in Navigation 2 Kanban via automation Oct 18, 2018
@mkhansenbot mkhansenbot added this to the November 2018 milestone Oct 18, 2018
@crdelsey
Copy link
Contributor Author

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.

@SteveMacenski
Copy link
Member

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

@crdelsey
Copy link
Contributor Author

That would be great. Thanks!

@crdelsey
Copy link
Contributor Author

Removed RRT and D*Lite.

@mjeronimo mjeronimo added 2 - Medium Medium Priority 3 - Low Low Priority and removed 2 - Medium Medium Priority 3 - Low Low Priority labels Nov 5, 2018
@crdelsey crdelsey moved this from Incoming Issues to Other Issues in Navigation 2 Kanban Jan 22, 2019
@crdelsey crdelsey added 3 - Low Low Priority and removed 2 - Medium Medium Priority labels Jan 28, 2019
@crdelsey crdelsey moved this from Medium Priority Issues to Low Priority Issues in Navigation 2 Kanban Jan 28, 2019
@crdelsey crdelsey removed this from the D Turtle Release milestone Jan 29, 2019
@orduno orduno mentioned this issue Feb 13, 2019
18 tasks
@crdelsey
Copy link
Contributor Author

crdelsey commented Oct 1, 2019

Closing since this isn't addressing a specific need. Work on TEB is covered by other issues.

@crdelsey crdelsey closed this as completed Oct 1, 2019
ghost pushed a commit to logivations/navigation2 that referenced this issue Mar 7, 2022
* 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 - Low Low Priority enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants