Repository navigation
Refactor model variant selection into explicit routing tables - #1256
Merged
Merged
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-family and variant selection currently uses separate conditionals and local lookup code. This change adds
ModelRouteTable<Key, Impl>and explicit model-local registration tables, retaining one selected descriptor for execution and family identity.Migrates Parakeet/Phonon2/Bark3/Haas, PocketTTS/Gradium Phonon, VibeVoice ASR, RoFormer, Audio Flamingo, Irodori RF/MF, and SeedVC. Irodori selects sampler and properties together; RoFormer registrations use named policy assignments. Routing stays at load, session, or request boundaries. Model specs, graph math, backend dispatch, and public options are unchanged.
Validation