This repository has been archived by the owner on Jul 1, 2024. It is now read-only.
Take a separate argument for loading checkpoints, take paths for pretrained checkpoints #379
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.
Summary:
There are now two arguments for checkpoints -
checkpoint_folder
: This is where checkpoints are saved to. Checkpoints are saved inside a subdirectory (the flow id) within this foldercheckpoint_load_path
: This is where checkpoints are loaded from. This can be a file or a directory.Note that this means that training will not automatically resume by picking up a checkpoint from the
checkpoint_folder
if the user doesn't specify acheckpoint_load_path
, but I think explicit is better than implicit in this scenario.Also, renamed
pretrained_checkpoint_folder
topretrained_checkpoint_path
and updated the help string to reflect the fact that this doesn't need to be a folder anymore.Updated the Getting started tutorial to reflect the changes.
Differential Revision: D19760255