-
Notifications
You must be signed in to change notification settings - Fork 658
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(lidar_centerpoint): non-maximum suppression target decision logic #9595
fix(lidar_centerpoint): non-maximum suppression target decision logic #9595
Conversation
Thank you for contributing to the Autoware project! 🚧 If your pull request is in progress, switch it to draft mode. Please ensure:
|
…distance calculation Signed-off-by: Taekjin LEE <[email protected]>
883dbec
to
948af5f
Compare
… pedestrian Signed-off-by: Taekjin LEE <[email protected]>
Signed-off-by: Taekjin LEE <[email protected]>
@technolojin Would you separate the PR for transfusion? I want to make the PR as small as possible (OK for image_projection_based_fusion and centerpoint as those two packages are dependent) |
perception/autoware_image_projection_based_fusion/config/pointpainting.param.yaml
Show resolved
Hide resolved
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9595 +/- ##
==========================================
- Coverage 29.59% 29.59% -0.01%
==========================================
Files 1442 1443 +1
Lines 108512 108514 +2
Branches 41409 41405 -4
==========================================
- Hits 32119 32115 -4
- Misses 73269 73278 +9
+ Partials 3124 3121 -3
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Sentry. |
...lidar_centerpoint/include/autoware/lidar_centerpoint/postprocess/non_maximum_suppression.hpp
Show resolved
Hide resolved
Signed-off-by: Taekjin LEE <[email protected]> fix: implement non-maximum suppression logic to the transfusion Signed-off-by: Taekjin LEE <[email protected]> refactor: remove unused parameter iou_nms_target_class_names Signed-off-by: Taekjin LEE <[email protected]> Revert "fix: implement non-maximum suppression logic to the transfusion" This reverts commit b8017fc. fix: revert transfusion modification
44e2cf7
to
8d9311a
Compare
@kminoda |
@technolojin I'm OK with it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
fix non-maximum suppression target decision logic
Before: If both of the object class are in the target label, caluclate IoU. If not, check distance and calculate IoU if the distance is less than a threshold.
After: If the label pair is not the same and one of them is pedestrian, do not suppress. Then, check distance and calcuclate IoU only if the distance is within a threshold.
optimize non-maximum suppression search range
Keep the squared value of the distance threshold.
remove NMS type
Since there is no other NMS option, remove the logic and parameter to select NMS type.
Related links
NMS PR: #1935
Issue:
How was this PR tested?
Performance test https://evaluation.tier4.jp/evaluation/reports/16239dd4-5213-5843-ada0-49341293bb6d?project_id=prd_jt
Execution test https://evaluation.tier4.jp/evaluation/reports/26db2be4-4fe5-5fe9-8221-320a88f318d7?project_id=prd_jt
Notes for reviewers
Remove unused parameter autowarefoundation/autoware_launch#1267 will be merged after this PR.
Interface changes
Parameter
iou_nms_target_class_names
will be removed.Effects on system behavior
None.