RFC: Add early stopping for all LR schedulers based on validation score improvements #218
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an example implementation to address #215 , which allows early stopping based on validation metric improvements regardless of the learning rate scheduler used. Prior to this, only the plateau scheduler could trigger early stopping, and that was based on it reducing the learning rate of the optimizer to below the min_lr setting. This change allows for specifying a threshold of successive validation runs, which if no improvement on the validation score is observed, ends training early.
An example training config is also included (
configs/iwslt14_deen_bpe_early_stopping.yaml
).Note: I manually copied this from a personal fork that has a number of other changes, so I haven't been able to fully test it yet.