Skip to content

Fix incorrect world <-> map coordinates conversions (backport #5049)#5074

Merged
SteveMacenski merged 1 commit intojazzyfrom
mergify/bp/jazzy/pr-5049
Apr 10, 2025
Merged

Fix incorrect world <-> map coordinates conversions (backport #5049)#5074
SteveMacenski merged 1 commit intojazzyfrom
mergify/bp/jazzy/pr-5049

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Apr 10, 2025

The conversion between world and map continuous (!) coordinates do not require a +/-0.5. This offset is only required when converting discrete map cell indexes to the coordinates of its center.


Basic Info

Info Please fill out this column
Ticket(s) this addresses #4735
Primary OS tested on Ubuntu
Robotic platform tested on Custom robot
Does this PR contain AI generated software? No

Description of testing performed

Description of contribution in a few bullet points

Description of documentation updates required from your changes

Description of how this change was tested


Future work that may be required in bullet points

For Maintainers:

  • Check that any new parameters added are updated in docs.nav2.org
  • Check that any significant change is added to the migration guide
  • Check that any new features OR changes to existing behaviors are reflected in the tuning guide
  • Check that any new functions have Doxygen added
  • Check that any new features have test coverage
  • Check that any new plugins is added to the plugins page
  • If BT Node, Additionally: add to BT's XML index of nodes for groot, BT package's readme table, and BT library lists

This is an automatic backport of pull request #5049 done by [Mergify](https://mergify.com).

* Fix incorrect world <-> map coordinates conversions

The conversion between world and map continuous (!) coordinates do not
require a +/-0.5. This offset is only required when converting discrete
map cell indexes to the coordinates of its center.

Signed-off-by: Dylan De Coeyer <dylan.decoeyer@quimesis.be>

* nav2_smac_planner: fix smoother test when path is in collision

The added pose was indeed invalid, but the it was ignored by the
smoother, since considered as a cusp.

Instead, let's make the end of the plan invalid as it won't be ignored.
Also, let's duplicate the last pose to make the orientation estimation
fail, rather than adding a new arbitrary pose.

Signed-off-by: Dylan De Coeyer <dylan.decoeyer@quimesis.be>

---------

Signed-off-by: Dylan De Coeyer <dylan.decoeyer@quimesis.be>
(cherry picked from commit 3ec7c33)
@mergify
Copy link
Contributor Author

mergify bot commented Apr 10, 2025

@mergify[bot], all pull requests must be targeted towards the main development branch.
Once merged into main, it is possible to backport to @jazzy, but it must be in main
to have these changes reflected into new distributions.

@SteveMacenski SteveMacenski merged commit 1a8b493 into jazzy Apr 10, 2025
6 of 8 checks passed
@SteveMacenski SteveMacenski deleted the mergify/bp/jazzy/pr-5049 branch April 10, 2025 19: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