Safely spawn fine tuned model #494
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
Intex32
force-pushed
the
safely-spawn-fine-tuned-model
branch
from
a657003 to
d5e7380
Compare
Montagon
approved these changes
Oct 19, 2023
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 Aallam implemented the new fine tuning OAI API, we can now more safely spawn a fine tuned model by it's fine tuning job id (rather than the model id). Previous method of spawning model by it's ID is still available. The advantage of the new approach: The fine tuning job includes information about the base model which we can use to check if spawning this model is valid. Previously you could spawn a model with an invalid base model, exceptions were thrown when querying.