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

Introduction of training phases #52

Open
GilesStrong opened this issue Jun 5, 2020 · 0 comments
Open

Introduction of training phases #52

GilesStrong opened this issue Jun 5, 2020 · 0 comments
Labels
disruptive Something which will likely cause large or breaking changes enhancement New feature or request low priority Not urgent and won't degrade with time

Comments

@GilesStrong
Copy link
Owner

Idea

Currently, training of a model uses the same settings, callbacks, and data for the entire training process. It could well be the case that the user wishes to change certain aspects at set points during the training. A simple example could be changing the LR cycle callbacks. A more complicated example could be changing the training data during training, e.g. from Delphes to Gent4 simulations. Another example could be starting with parts of the model frozen, and then unfreezing them at a set point (e.g. pre-training a part of the model to work better on low-level information before introducing high-level information)

This could potentially be allowed by defining training phases, each with their own sets of settings, callbacks, and data.

This idea will no doubt require large changes to fold_train_ensemble, and some sort of 'trigger' callback to move to the next training phase.

@GilesStrong GilesStrong added enhancement New feature or request low priority Not urgent and won't degrade with time disruptive Something which will likely cause large or breaking changes labels Jun 5, 2020
@GilesStrong GilesStrong changed the title Training phases Introduction of training phases Jun 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
disruptive Something which will likely cause large or breaking changes enhancement New feature or request low priority Not urgent and won't degrade with time
Projects
None yet
Development

No branches or pull requests

1 participant