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

Explanation why to use cifar10-2 #43

Open
vinnik-dmitry07 opened this issue Apr 18, 2023 · 0 comments
Open

Explanation why to use cifar10-2 #43

vinnik-dmitry07 opened this issue Apr 18, 2023 · 0 comments

Comments

@vinnik-dmitry07
Copy link

image

(Database0 represents unique images that are not in the train set)

When we test our model, we assume that it corresponds to a real-world situation when we can train seen database before making unseen queries. Therefore we can include the train set in the database set. However, in the case of NUS and COCO classes of datasets are not balanced. We have no guarantee that we have 193734//21=9225 images of every class. Empirically, I have found that in nuswide_21 code.py we can set train_num up to ~2100. I do not know why someone decided to put only 500 per class, but I definitely know that Train <= Database.
Thus, we have 3 scenarios:

  1. CIFAR is balanced, therefore we can use Train = Dataset
  2. NUS: we try to balance, therefore we Train <= Dataset
  3. COCO: we do not balance (too hard?), Train <= Dataset
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

1 participant