AMRNAV-6916 Goal checker: Check for x and y separately #89
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Basic Info
Description of contribution
Reason for change:
There is often a tradeoff while reaching goals: We want the AMR to drive as close as it can to the goal, without oscillating close to it. The AMR can easily adjust its x-coordinate compared to the goal by driving forward or backwards.
However, it cannot drive sideways, so it cannot correct sideways error easily. Instead, then it has to drive forward, turn, and drive backwards again.
Thus: We want to split the checker to check directions individually in the goal frame. Currently one can already pass "yaw". Please add options to pass "x" and "y" as well. Then
if "x" or "y" is defined, also check these values
if "xy" is not defined in the BT node, use "infinite" by default.
Changes in this PR:
Result:
x and y are checked separately