fix(avoidance): get nearest target object #3155
Merged
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.
Description
Fix bug in searching nearest target object that satisfies following two conditions:
Before this PR, the
stop_target_object
is overwitten unintentionally by bihind object since the loop never breaks.NOTE:
target_objects
is sorted byobject.longitudinal
, sotarget_objects.front()
is the nearest object intarget_objects
.Related links
Tests performed
Before this PR.
Since only one object is detected, the stop point is inserted in front of the object.
At the moment of detection behind object, the stop point moves to in front of the behind object. It is an unexpected behavior.
After this PR.
The stop point never changes even if the behind object is detected.
Notes for reviewers
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.
In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.
Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.
After all checkboxes are checked, anyone who has write access can merge the PR.