fix: Normalize ASR MRoPE metadata for runtime - #146
Open
suharvest wants to merge 1 commit into
Open
Conversation
Signed-off-by: suharvest <suharvest@gmail.com>
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 does this PR do?
Extends the existing runtime RoPE normalization to recognize checkpoint
metadata that combines
rope_type: linearwithmrope_section.That combination describes an MRoPE layout used by Qwen3-ASR checkpoints, but
the runtime accepts the existing normalized
default + mrope_sectionform.Without this normalization, export preserves
linearand the runtime does notselect its MRoPE path.
The input dictionary is copied rather than mutated. Ordinary linear RoPE
metadata without
mrope_sectionremains unchanged.Scope
Validation
2 passed.linear + mrope_sectionbecomesdefault + mrope_sectionwithout mutating the source.git diff --check, and merge-treevalidation pass.
This is a configuration-normalization regression test. A complete
export → build → inference validation requires the model and GPU environment
and is still requested from CI/device testing.
Closes #142.