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

memory_size,memory_per_class #2

Closed
LifeIsBright-heihei opened this issue Jan 7, 2022 · 5 comments
Closed

memory_size,memory_per_class #2

LifeIsBright-heihei opened this issue Jan 7, 2022 · 5 comments
Labels
question Further information is requested

Comments

@LifeIsBright-heihei
Copy link

Hello, thank you very much for the code you provided. Can you tell me what the parameter memory_size and memory_per_class represents?

@LifeIsBright-heihei
Copy link
Author

If the number of pictures in the second increment is much smaller than that in the first increment, how should I set these two parameters

@G-U-N
Copy link
Owner

G-U-N commented Jan 12, 2022

When fixed memory is set to false, memory size is used, which means that we keep memory size images for all the old classes, which means that for each of the k old categories, we keep memory size/k(floor) images.

On the contrary, when fixed memory is set to true, memory_per_class will be used, which means that we will keep memory_per_class images for each category. In other words, its memory size increases with the number of categories.

@G-U-N
Copy link
Owner

G-U-N commented Jan 12, 2022

In most cases, to be fair, when training cifar100 and imagenet100, we set memory size to 2000, and when training imagenet1000, we set memory size to 20000.

@G-U-N G-U-N added the question Further information is requested label Jan 12, 2022
@LifeIsBright-heihei
Copy link
Author

When fixed memory is set to false, memory size is used, which means that we keep memory size images for all the old classes, which means that for each of the k old categories, we keep memory size/k(floor) images.

On the contrary, when fixed memory is set to true, memory_per_class will be used, which means that we will keep memory_per_class images for each category. In other words, its memory size increases with the number of categories.

I probably understand. Thank you for your explanation

@G-U-N
Copy link
Owner

G-U-N commented Jan 12, 2022

Thanks for your interests. 😊

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

No branches or pull requests

2 participants