-
Notifications
You must be signed in to change notification settings - Fork 63
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 epochs is 5? #7
Comments
@gongshaojie12 I just used a fairly standard number of epochs. I observed no increased performance by running them for a larger period of time. You can try it to train them for more time and let me know if that yields better results. Ping me if you want to do so (particularly regarding downloading the data, I haven't documented that very much) |
Hi @finiteautomata I set epochs to 30, As can be seen from the figure, from the third epoch, |
@gongshaojie12 great, thanks for your experiments. I understand that you observed no performance increase by setting a larger number of epochs; moreover, it seems that ~5 epochs seems to be ok. What dataset are you using? SemEval (English) or TASS(Spanish)? |
Hi @finiteautomata The dataset I used is |
@gongshaojie12 that is the dataset used for English Emotion Analysis. As you can see, that dataset is small-sized – the same occurs with the Spanish version of EmoEvent, and the Sentiment Analysis in Spanish (TASS). We used 10 epochs for Sentiment Analysis in English as that dataset is bigger (around 50k instances) |
Hi @finiteautomata Thanks for your reply. What if I want to get more EmoEvent data? |
@gongshaojie12 if you want to get more data, you should collect and annotate your own corpus. You can get more information on how the authors did so here https://github.com/fmplaza/EmoEvent-multilingual-corpus |
OK,Thanks a lot |
Closing this. Feel free to reopen or send email if you have any doubt |
Hi,I noticed that the
epochs
is 5 during training, why not set it a bit larger? Is it because theepochs
are set too large to cause overfitting? Thanks!The text was updated successfully, but these errors were encountered: