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

Unpopular feature request: add costmap source to collision monitor #4794

Open
tonynajjar opened this issue Dec 12, 2024 · 1 comment
Open

Comments

@tonynajjar
Copy link
Contributor

Feature request

Feature description

I know the collision monitor bypasses the costmap on purpose for faster response but for my application I care less about faster response and more about leveraging the persistence of some of the costmap layers because I lack a 360 degrees perception coverage.
So I'm proposing a CM source that does collision-checking against a costmap it subscribes to.
What do you think?

Implementation considerations

@SteveMacenski
Copy link
Member

I'd merge a PR as long as the documentation in the readme and website warned against doing it for the reasons you know about (but that you can if needed)

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

No branches or pull requests

2 participants