feat(nova-evaluation): Add checkpoint_is_instruct_tuned to InferenceConfig#374
Open
amaz-jmoul wants to merge 1 commit intoaws:release_v2from
Open
feat(nova-evaluation): Add checkpoint_is_instruct_tuned to InferenceConfig#374amaz-jmoul wants to merge 1 commit intoaws:release_v2from
amaz-jmoul wants to merge 1 commit intoaws:release_v2from
Conversation
tang-ti
approved these changes
Feb 18, 2026
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.
What's changing and why?
This parameter is used during evaluation runs on CPT models. We need to add it here so validations pass when using SMHP.
A customer tried to use this parameter which is supported by the evaluation container but got a validation error because it is not present here.
Before/After UX
Before:
Customer tries to use the new checkpoint_is_instruct_tuned = "false" parameter, but failed due to pydantic validation error since it's not here.
After:
Customer is able to set checkpoint_is_instruct_tuned = "false" and run CPT evaluation.
How was this change tested?
We have verified that the checkpoint_is_instruct_tuned parameter works with the evaluation container internally.
Are unit tests added?
No
Are integration tests added?
No
Reviewer Guidelines
One of the following must be true: