Add support for fine-tuning #30
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
josejimenezluna
approved these changes
Aug 15, 2022
mrwnmsr
approved these changes
Aug 15, 2022
kmaziarz
force-pushed
the
kmaziarz/finetuning
branch
from
5cd0369
to
b21bceb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As discussed in #21, fine-tuning models was not fully supported, as preprocessing data for fine-tuning would need to know about atom featurisers and motif vocabulary built during pretraining, and there was no way to plug those in. I add support for this here, and explain how to perform fine-tuning in
README.md.