You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, tagger.py wouldn't run unless you provide all three splits. Especially for fine-tunning is highly recommendable to not use the test set, since that would actually lead to overfitting on the test set (since you are getting feedback from your model's performance on the test set). You can of course set the test split to be the same as the dev, then you are running the same evaluation twice, which is wasteful.
The text was updated successfully, but these errors were encountered:
I just saw there is the include_test param in the config file. I guess that's is redundant with the fact of actually providing a path for --test... we could get rid of that config param.
Currently, tagger.py wouldn't run unless you provide all three splits. Especially for fine-tunning is highly recommendable to not use the test set, since that would actually lead to overfitting on the test set (since you are getting feedback from your model's performance on the test set). You can of course set the test split to be the same as the dev, then you are running the same evaluation twice, which is wasteful.
The text was updated successfully, but these errors were encountered: