GDumb memory update
See original GitHub issueGDumb
does not remove samples when the number of classes increases.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
GDumb: A Simple Approach that Questions Our Progress in ...
Given a memory budget, the sampler greedily stores samples from a data-stream while making sure that the classes are balanced, and, at inference,...
Read more >GDumb: A Simple Approach that Questions Our Progress in ...
Given a memory budget, the sampler greedily stores samples from a data-stream while making sure that the classes are balanced, and, at inference,...
Read more >Continual Learning With a Memory of Diverse Samples
where a model is strongly confident. Algorithm 1 summarizes our proposed diversity-aware memory update algorithm. Following GDumb [38], we also.
Read more >Continual Recognition with Adaptive Memory Update
Our continual recognition model with adaptive memory update is capable of overcoming the problem of catastrophic forgetting with various new ...
Read more >GDumb: A Simple Approach that Questions ... - ResearchGate
To validate this, we propose GDumb that (1) greedily stores samples in memory as they come and; (2) at test time, trains a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok, the last error has nothing to do with
GDumb
and it appears to be a bug inSplitFMnist
. I will create a new issue to track it and close this as soon as GDumb is ready.This is the error raised with GDumb (after the callback name modification) when using
scenario = SplitFMnist(5)
. I noticed that this error is not raised with SplitMNIST, though.