fix(lane_change): check obj predicted path when filtering #9385
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
If there’s object that crosses predicted target lanes but it is not in target lane or target preceding lane, then the object will be treated as other lane object and will be ignored.
This PR aims to fix this.
Before PR
The following video shows the use case.
If the object is not in cyan lane (current) or blue (target preceding), then it will be considered as others object (purple cube).
cap-.2024-11-19-18-13-39.mp4
With PR
Object is now considered as target lane leading object (cyan cube)
cap-.2024-11-19-17-55-12.mp4
Related links
Parent Issue:
How was this PR tested?
Notes for reviewers
None.
Interface changes
None.
Effects on system behavior
None.