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

Pausing costmap converstion when the costmap is stopped #11

Open
nirwester opened this issue Aug 20, 2019 · 0 comments
Open

Pausing costmap converstion when the costmap is stopped #11

nirwester opened this issue Aug 20, 2019 · 0 comments

Comments

@nirwester
Copy link

Currently the converter continuously parses the costmap, even when this is stopped and didn't change from the previous execution. Since the CPU usage of most of the plugins is relevant (often consumes an entire core on our platforms), it would be useful to pause the parsing if the costmap is stopped.

Unfortunately it is currently not easy to check if the costmap is stopped; I made a PR to expose the stopped status of the costmap2D_ros here

ros-planning/navigation#913

Can you think about any alternative that could avoid this unnecessary computation? Maybe comparing the current costmap with the latest used one?

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

1 participant