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

[Question]: Difference Between train and fine_tune Methods in ModelTrainer #3377

Closed
AAnirudh07 opened this issue Nov 27, 2023 · 2 comments
Closed
Labels
question Further information is requested

Comments

@AAnirudh07
Copy link

Question

I noticed the documentation on the difference between the ModelTrainer's train() and fine_tune() methods is empty. Based on this example, it seems like train() is for FLAIR embeddings, and fine_tune() is for Transformer embeddings. Is this the only distinction, or are there other differences? Any insights would be much appreciated!

@AAnirudh07 AAnirudh07 added the question Further information is requested label Nov 27, 2023
@AAnirudh07 AAnirudh07 changed the title [Question]: Difference Between train and fine_tune Methods in ModelTrainer [Question]: Difference Between train and `fine_tune Methods in ModelTrainer Nov 27, 2023
@AAnirudh07 AAnirudh07 changed the title [Question]: Difference Between train and `fine_tune Methods in ModelTrainer [Question]: Difference Between train and fine_tune Methods in ModelTrainer Nov 27, 2023
@helpmefindaname
Copy link
Collaborator

Hi @AAnirudh07
exactly, the only difference is the set of default parameters. Train is usually used for a feature extraction method, where you have a frozen weight and some LSTM layers afterwards while fine_tune is used for fine_tuning the whole embeddings, (e.g. using transformers with finetune=True

@AAnirudh07
Copy link
Author

Gotcha, thank you! I'll go ahead and close this issue now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants