wrong result of differentiable 3D IoU, occurring larger than 1
See original GitHub issueHello,
I apply function diff_iou_rotated_3d
from mmcv.ops to implement 3D IoU loss.
However, the computed IoU can be larger than 1 in some circumstances, which is wrong by definition.
But if I compute the specified predicition and target where IoU > 1 occurred, the result might be right.
This bug could be related to parallelization in cuda file, but I couldn’t locate the problem code.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
A Metric and A Loss for Bounding Box Regression
Intersection over Union (IoU) is the most popular evalu- ation metric used in the object detection ... I) Similar to IoU, the value...
Read more >IoU3D - PyTorch3D
We introduce a new algorithm which computes the exact IoU of two oriented 3D boxes. Our algorithm is based on the simple observation...
Read more >220 - What is the best loss function for semantic segmentation?
IoU and Binary Cross-Entropy are good loss functions for binary semantic segmentation. but Focal loss may be better. Focal loss is good for ......
Read more >3D Multi-Object Tracking with Differentiable Pose Estimation
over time for reliable object pose tracking to address these shortcomings. ... Figure 1: We investigate the task of 3D multi-object tracking ...
Read more >Unsupervised Learning of 3D Object Categories from Videos ...
Our evaluation demonstrates performance improvements over several deep monocular ... value σ(x,z)∈(0,1] representing the opaqueness of the 3D space.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @Angericky ,
According to the author of the original rotated iou implementation the result may be inaccurate in some corner cases 1, 2. Actually it is a bug. However even in current implementation the rotated iou loss is extremely useful for object detection 3, 4.
I downgrade pytorch to 1.7 and the bug still exists. Oh I found the wrong value
3.5672
in your result.txt at line 1972