Fix inconsistent NMS implementation between CPU and CUDA #1556
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was an inconsistency in how
nms_threshold
was handled in NMS between CPU and GPU. More precisely, the difference arises with proposals that satisfyoverlap == nms_threshold
.We used
ovr >= iou_threshold
for CPUvision/torchvision/csrc/cpu/nms_cpu.cpp
Line 64 in cd17484
ovr > iou_threshold
for CUDAvision/torchvision/csrc/cuda/nms_cuda.cu
Line 63 in cd17484
This was caught during test refactorings in #1551, which exposed this inconsistency.
cc @rbgirshick @ppwwyyxx