Skip to content

[Bug]: Fastdup only accepts one object per image in COCO format #350

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

Closed
kasperschnack opened this issue Nov 15, 2024 · 4 comments
Closed
Labels
bug Something isn't working

Comments

@kasperschnack
Copy link

kasperschnack commented Nov 15, 2024

What happened?

When using fastdup with a COCO format dataset, it only recognizes and processes one object per image, first one in the list of annotations, even when multiple objects are present in the annotations.

What did you expect to see?

I expected fastdup to process and recognize all annotated objects per image in the COCO format dataset, allowing for handling images with multiple images.

What version of fastdup were you runnning on?

2.13

What version of Python were you running on?

Python 3.9

Operating System

Mac OS Sonoma 14.7.1 (23H222)

Reproduction steps

  1. Prepare a COCO format dataset with multiple objects annotated per image

put all images and annotations.json in imgs/ folder

  1. Run fastdup on the prepared dataset using jupyter notebook
import fastdup

fd = fastdup.create(input_dir="imgs/")
fd.run()

fd.explore()
  1. Observe the output and visualizations

Notice that only one object per image is recognized and processed

Relevant log output

No errors are shown

Attach a screenshot [Optional]

image

Only category 133 is shown for image 706. If i switch around the order of the categories such that 54 is first - that is the one that will be registered

Contact Details [Optional]

[email protected]

@kasperschnack kasperschnack added the bug Something isn't working label Nov 15, 2024
@Tompil3r
Copy link
Collaborator

Hi @kasperschnack,
fastdup removes bounding boxes with the exact same coordinates in the same image. Hope this clears things up.

@kasperschnack
Copy link
Author

Hi @Tompil3r

Thank you very much for that clarification! Indeed that solves the mystery!

@kasperschnack
Copy link
Author

Maybe it would be a good idea to print a warning when this happens? Other people might be confused by this as well

@dbickson
Copy link
Collaborator

This is a great idea. We will add this warning and report once completed soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants