Skip to content
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

nms() in do_detect() in utils.py should perform per class per image, no? #29

Open
love2learn-7179 opened this issue May 20, 2020 · 6 comments

Comments

@love2learn-7179
Copy link

I thought we should perform nms per class per image, no?
def nms(boxes, nms_thresh): in tool/utils.py

@HotaekHan
Copy link

ordinally NMS perform as class agnostic because of overlapped boxes.

@liuxufenfeiya
Copy link

in author'nms, too many 'for' caused the speed too slow
my P4000 GPU result:
darknet: 30 fps
tf-yolov4: 25 fps
pytorch-yolov4: 12 fps

@Tianxiaomo
Copy link
Owner

Thank you very much for your suggestions. I will optimize the NMS in the future, and you are welcome to join us.
@love2learn-7179 @HotaekHan @liuxufenfeiya

@GlassyWing
Copy link

it needs performs for each class, but this can be optimized by adding offset, For details, please refer to the nms implementation in torchvision

@HotaekHan
Copy link

@GlassyWing Could you point out the code?

@GlassyWing
Copy link

GlassyWing commented May 26, 2020

@GlassyWing Could you point out the code?

The code could be see at
https://github.com/pytorch/vision/blob/3d65fc6723f1e0709916f24d819d6e17a925b394/torchvision/ops/boxes.py#L45

The comments have explained the process in more detail

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants