-
Notifications
You must be signed in to change notification settings - Fork 134
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
why FeTrIL acc is so bad #22
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
It seems that you failed at the base training stage, did you wrongly modify the code for base training? |
yes, In line 104: https://github.com/G-U-N/PyCIL/blob/master/models/fetril.py#L104 I removed this line's comment, otherwise an error will be reported |
your training log? |
sorry, it lost. please wait 10 minutes |
sorry final result:
I had set all BN layers : track_running_stats=False, so acc is bad. set track_running_stats=True will got good performance. so, why does this happen, in order to compare my algorithm fairly, I should set track_running_stats=False for all BN Layers. |
Glad to see you have reproduced the ideal results in our framework. For your question: Setting |
wait..... look this repo(task increment learning): https://github.com/sahagobinda/GPM/blob/main/main_cifar100.py all of BN layers are set track_runing_stats to false, but got good performance....... maybe this is another question? |
I have no responsibility to answer questions outside our framework, thanks. |
I'm sorry I was negligent |
config:
final result:
I can provide log if you need.
The text was updated successfully, but these errors were encountered: