-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Add training.before_update
callback
#11739
Add training.before_update
callback
#11739
Conversation
This callback can be used to implement training paradigms like gradual (un)freezing of components (e.g: the Transformer) after a certain number of training steps to mitigate catastrophic forgetting during fine-tuning.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you find out if there is an easy way to test this?
Nothing short of bundling a small, toy corpus file and invoking the |
Can you add some minimal tests for this? It doesn't look like there are any training-specific callback tests yet, but there are similar tests for the |
I think you should be able to test this with |
Ah, didn't realize the extra data wouldn't be included anyway. I'll try out your suggestion. |
It's not that we can't add extra data with some additional settings, and it might make sense to have one toy As I've mentioned a few times, the extra CLI tests in the CI should probably be moved into a proper test suite that's separate from the package tests and we can have the CI run both, and that would be an easier place for longer/larger tests. |
Co-authored-by: Adriane Boyd <adrianeboyd@gmail.com>
Description
This callback can be used to implement training paradigms like gradual (un)freezing of components (e.g: the Transformer) after a certain number of training steps to mitigate catastrophic forgetting during fine-tuning.
Types of change
New feature
Checklist