[fix] not predicting objects at x<=0 or y<=0 #2122
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yukkysaito
approved these changes
Mar 14, 2019
amc-nu
reviewed
Mar 14, 2019
..._predictor/packages/naive_motion_predict/nodes/naive_motion_predict/naive_motion_predict.cpp
Show resolved
Hide resolved
|
@amc-nu Can you check? |
amc-nu
approved these changes
Mar 14, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Status
DEVELOPMENT
Description
Modify evaluation method for invalidity so that object at x<=0 or y<= 0 would be predicted.
Related issue
autowarefoundation/autoware_ai#618
Todos
Steps to Test or Reproduce
Objects at x<=0 or y=0 are predicted.
You can check resulst by subscribing to
/prediction/motion_predict//prediction/motion_predictor/path_markers