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

Add validate every n epochs #111

Open
alexriedel1 opened this issue Feb 3, 2022 · 3 comments
Open

Add validate every n epochs #111

alexriedel1 opened this issue Feb 3, 2022 · 3 comments

Comments

@alexriedel1
Copy link

Hey, as an enhancement for custom model training, I propose to add a configuration argument so that the trainer does not evaluate after every epoch but a specification to validate every n epochs.

This would speed up the training process as the validation on adversarial examples can take quite a long time and maybe doesn't make sense in the early stages of a training.

@tamltlkdn
Copy link

Hello, why do we need to validate the adversarial examples during training? Are we using/reporting the best model instead of the last model??

@alexriedel1
Copy link
Author

We want to know if the model is improving (learning) during the training

@tamltlkdn
Copy link

I verified by myself and find that the PGD 7 ACC reaches its peak after the lr is dropped (probably at 100 epoch or 150 epoch). The final (at 200 epoch) model achieves a lower PGD 20 than the best model. I load the pre-trained model ResNet50 provided in this repo and it said the epoch is 152. It looks like they provide the best one, not the last model.

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

2 participants