Allow Apeiron to use custom checkpoints - #126
Open
anagainaru wants to merge 2 commits into
Open
Conversation
This file contains hidden or 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
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.
Model harnesses can define custom checkpoints. If the model requires metadata beyond weights (e.g., preprocessing scalers, feature names, architecture parameters). This PR introduces an optional
build_checkpoint_payload()function that the model harness can overwrite (by default only weights are saved which is the current behavior of Apeiron).This will ensure that the checkpoints and the input model can have the same elements (i.e. the checkpoints can be used as input model for Apeiron using the same model harness used to create them)
Documentation
Testing
Closes #125