-
Notifications
You must be signed in to change notification settings - Fork 1
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
About the differences on the training strategies when "_pt" in model name or not. #1
Comments
It is kind of our fault for not cleaning up these code, since these options are defined for models that are deleted in the final paper.
So, in a word, just ignore them. I will add a commit later to remove these code. |
I get it! Thank you so much! |
Thank you so much for your prominent work in your MProtoNet, and sincerely thank you for your code available on Github too.
Recently, we have some doubts about the usage of (a) "_pt" in model name and (b) best_grid["fixed"] in tumor_cls.py.
In the commands you supply in the repository, the model names all end with "_pmX". Therefore, according to the code, MProtoNet will update in mode "joint" and "last_layer" (every 10 epochs) while training. However, we notice that when "_pt" is in the model name and best_grid["fixed"]=False, there is also another branch, where the net.features will not update at the begging, but start to optimize when current epoch >= wu_e. We also notice that the vanilla ProtoPNet updates in the latter way (fix the net.features at the begging).
Will there be a significant difference between two kinds of training strategies? Hope to receive your kindest reply!
The text was updated successfully, but these errors were encountered: