Skip to content

Remove Costmap 2D #350

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

Open
wants to merge 1 commit into
base: humble
Choose a base branch
from
Open

Remove Costmap 2D #350

wants to merge 1 commit into from

Conversation

amock
Copy link

@amock amock commented Apr 14, 2025

Removed costmap 2d as discussed in #346

@Rayman
Copy link
Contributor

Rayman commented Apr 14, 2025

For me its a bit strange that the costmap 2d is not included in the core mbf repo. This means mbf is not a plug and play replacement for navigation2. This means adoption will be slower.

You can also choose to just not release these packages yet, and wait until they are migrated?

(I'm not a maintainer, I've only used mbf during ROS 1)

@amock
Copy link
Author

amock commented Apr 14, 2025

Actually, I don't think MBF itself can be a plug-and-play replacement for Nav2; only a 2d costmap-based implementation of MBF can be. If you want, you can still create a separate repository with such an implementation, which could serve as a plug-and-play replacement for Nav2.

I believe this step simply makes MBF truly and more obviously independent of any specific map representation. That said, I'm not sure if this is the best approach, which is why I started the discussion in issue #346.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants