Closed HovorunBh closed 6 days ago
All modified and coverable lines are covered by tests :white_check_mark:
Files | Coverage Δ | |
---|---|---|
...2_smac_planner/include/nav2_smac_planner/utils.hpp | 98.64% <100.00%> (ø) |
Thanks! All good points, well explained, and with visual examples!
Basic Info
Description of contribution in a few bullet points
For reproducing the issue see the test I added
We noticed that ComputePathThroughPoses with SmacPlannerHybrid when asked to generate path through poses that are on the same line (in this example: [{x: 2, y: 0}, {x: 4, y: 0}, {x: 6, y: 0}]) generates path like this:
It is assumed that end of path1 is the start of path2, but when end of path1 is converted from map to world, and then back to map it ends up in a different costmap cell.
When we convert world to map coordinates we add 0.5
Therefore when we convert map to world I think we should subtract 0.5. Otherwise we end up in the next costmap cell With this change path looks like more straight:
Description of documentation updates required from your changes
Future work that may be required in bullet points
For Maintainers: