Megvii-BaseDetection / Megvii-BaseDetection/YOLOX

Too many false positive bounding bboxes in my YOLOX detection result

Open
#980 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
10.6k
Forks
2.5k
PR merge metrics
No merged PRs in 30d

Description

你好,我在训练yoloxs的时候,加载自己的数据,结果发现误检框非常多。因为同样的数据当时跑yolov5的时候误检是没有那么多的,所以我感觉应该不是数据问题。然后我就看了下代码在simOTA做assign gt的时候完全没有对负样本进行采样,同时看到这个issue(https://github.com/Megvii-BaseDetection/YOLOX/issues/725)里也提到了这点。那我理解即使我增加background的图片也无法降低误检,因为并没有采样negative anchor point并进行抑制,请问下我的理解是否正确,同时这个问题是否有解决的计划,谢谢。

Hello, I train yoloxs on my own dataset with too many false positive bounding bbox in result. I suppose that it has no problem with the dataset, because much fewer false positive boxes in yolov5s training with the same dataset. I notice that YOLOX does not sample negative anchor point in simOTA. And this issue mention this problem as well(https://github.com/Megvii-BaseDetection/YOLOX/issues/725). So is that means even if the dataset contains background images, YOLOX can not select negative anchor point for improve the false positive problem. Is that correct? Many Thanks for your Apply.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the simOTA ground-truth assignment logic and the linked issue #725, then compare how YOLOX handles background or negative locations with the reported YOLOv5 behavior. Done would require a maintainer-confirmed explanation of whether negative sampling is involved and whether a code change is planned.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, pytorch
Domain
computer-vision, machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.