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

AUTO-604 Fix using different frame for global and local costmap #8

Merged
merged 10 commits into from
Feb 24, 2023

Conversation

doisyg
Copy link

@doisyg doisyg commented Feb 23, 2023

Mirror of nav2 PR: ros-navigation#3425

It is currently impossible to use a different global frame for the global and local costmap.
The use of worldToMap to check if the pose is inside the costmap works only if the pose to check is referenced relative to the costmap frame: https://github.com/ros-planning/navigation2/blob/9dca1cfa60af9cdc4f6111db960bae72fd85b17c/nav2_mppi_controller/src/path_handler.cpp#L66

Proposed fix is to replace transformPlanPosesToCostmapFrame and getGlobalPlanConsideringBounds by getGlobalPlanConsideringBoundsInCostmapFrame in order not to have to transform the pose from the global plan/global costmap frame to the controller/local costmap frame twice.

@doisyg doisyg requested review from a team and jayyoung and removed request for a team February 23, 2023 09:47
@doisyg
Copy link
Author

doisyg commented Feb 24, 2023

Approved upstream, waiting for test to pass: ros-navigation#3425

@doisyg doisyg merged commit d1832e9 into bau Feb 24, 2023
@doisyg doisyg deleted the AUTO-604_fix_check_costmap_bounds branch February 24, 2023 15:20
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