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

does the widget automatically retrain when all items are manually labelled? #78

Open
credelosa opened this issue Sep 20, 2022 · 2 comments

Comments

@credelosa
Copy link

Hello @janfreyberg! It's me again.

This is more of an inquiry regarding the widget retraining mechanism. Does the widget automatically retrain when all items are manually labelled? Let's say you have 10 items to manually label. After labeling the 5th item, you press retrain then label the rest of the items. Is the final model trained on all 10 items or just up until the 5th item? If it's the latter, is this on purpose? If so, what is the advantage over automatically returning a model trained on all labelled items? :)

Thank you!

@janfreyberg
Copy link
Owner

Hi! The retraining mechanism was actually never fully designed for returning a model for further use at the end. I was envisioning that people would take the labels at the end, and re-train a model outside of the superintendent workflow.

So no, at the moment the model is not re-trained on all data at the end, and I would recommend to retrain a model separately afterwards! This also forces you to be a bit more deliberate about what data you use for re-training. For example, you may want to split data into a train and validation set before you re-train your final model.

Does that make sense? Or is there a big advantage in having superintendent do this for you?

@credelosa
Copy link
Author

Yup that makes sense. I was thinking that it could be a helpful having an optional parameter (default to False) where the widget would automatically retrain at the end. With this, your concern with users being deliberate about what data to use for re-training would still hold while having the flexibility of having the automation at the end or not. :)

What do you think?

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