Investigate value differences between our ConfusionMatrix and YOLOv8 implementation
#227
Replies: 10 comments
|
@SkalskiP I found that |
|
Hi, @hardikdava 👋🏻! Yeah, I know the result matrix is transposed, but that's not the issue. :) But even if you consider that, there are still some differences. No worries, we will figure it out. 👍🏻 |
I'm not sure I understand this part. :) |
|
@SkalskiP I am investigating the issue with |
|
@hardikdava Oh, interesting. So if there are no detections, we are dropping the image from the dataset instead of loading |
Yeah, also the dataset has issue. I found that 1 image is present but relative annotation file is missing, also 1 annotation file is present and relative image is missing. 😆 |
|
@SkalskiP Summary of my experiments:
I do not see any other difference in the implementation. |
|
Excellent work, @hardikdava! Thanks a lot for the time you spend investigating the issue. So the takeaways are:
|
|
@SkalskiP Please convert this issue as |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Search before asking
Bug
We recently added object detection
ConfusionMatrixtosupervision. However, we noticed that ourConfusionMatrixvalue tends to differ from the one you get from YOLOv8. We would like to understand why that is happening. And fix any potential bugs in our codebase. Heda more here.All reactions