-
Notifications
You must be signed in to change notification settings - Fork 51
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 epoch #20
Comments
Note that the Check out the following two graphs from the README, they show the evaluation metric over the update steps. During training, the model only sees the images without defects. Because we want the model to learn what the characteristics of a good sample, it might be desired to "overfit" to these images. |
thanks for your explanation, |
In README, you mentioned ' The --epoch parameter takes the number of update steps and not their definition of epochs.'. |
Correct. If you look into the paper on arxiv page 12 (Appendix 3) they specify how many update steps they use:
Which makes me think they use |
thanks for your prompt reply! yes, I have noticed that in the paper, |
When run run_training.py,the epoch is 10000.Is it necessary?10000 is too large,and the MVTec is small.I worry about overfit.Can i set epoch smaller?for example,set epoch 4000?
Thanks!
The text was updated successfully, but these errors were encountered: