chore(model-gallery): propose variant groupings for review - #12180
Open
localai-org-maint-bot wants to merge 1 commit into
Open
localai-org-maint-bot wants to merge 1 commit into
localai-org-maint-bot wants to merge 1 commit into
Conversation
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This branch has not been deployed
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.
Proposed gallery variant groupings
This is a proposal, not a decision. The gallery agent adds one build per model and never joins an existing family, so entries that are alternative builds of the same weights drift apart as the gallery grows. This job re-applies the grouping heuristics from the manual sweeps and asks a human to confirm.
Each family below lists the parent, the variants, and the evidence that they are the same weights. Reject anything whose evidence you do not believe.
To decline a family permanently, add one line to
gallery/variant-exclusions.yamlin this pull request and close it:Proposed families (4)
kimodo-g1-rpkimodo-g1-rp-bf16name-modulo-quant,weight-filenamekimodo-g1-rp; same primary weight filename once quantization markers are stripped:kimodo-g1-rp-v1; same upstream repolocalai-io/kimodo-g1-rp-v1-ggml; differing quantization tokens:bf16,f32,g1kimodo-g1-rp-q4_kname-modulo-quant,weight-filenamekimodo-g1-rp; same primary weight filename once quantization markers are stripped:kimodo-g1-rp-v1; same upstream repolocalai-io/kimodo-g1-rp-v1-ggml; differing quantization tokens:f32,g1,q4_kkimodo-g1-rp-q4_k_mname-modulo-quant,weight-filenamekimodo-g1-rp; same primary weight filename once quantization markers are stripped:kimodo-g1-rp-v1; same upstream repolocalai-io/kimodo-g1-rp-v1-ggml; differing quantization tokens:f32,g1,q4_k_mkimodo-g1-rp-q5_kname-modulo-quant,weight-filenamekimodo-g1-rp; same primary weight filename once quantization markers are stripped:kimodo-g1-rp-v1; same upstream repolocalai-io/kimodo-g1-rp-v1-ggml; differing quantization tokens:f32,g1,q5_kkimodo-g1-rp-q6_kname-modulo-quant,weight-filenamekimodo-g1-rp; same primary weight filename once quantization markers are stripped:kimodo-g1-rp-v1; same upstream repolocalai-io/kimodo-g1-rp-v1-ggml; differing quantization tokens:f32,g1,q6_kkimodo-g1-seedkimodo-g1-seed-bf16name-modulo-quant,weight-filenamekimodo-g1-seed; same primary weight filename once quantization markers are stripped:kimodo-g1-seed-v1; same upstream repolocalai-io/kimodo-g1-seed-v1-ggml; differing quantization tokens:bf16,f32,g1kimodo-g1-seed-q4_kname-modulo-quant,weight-filenamekimodo-g1-seed; same primary weight filename once quantization markers are stripped:kimodo-g1-seed-v1; same upstream repolocalai-io/kimodo-g1-seed-v1-ggml; differing quantization tokens:f32,g1,q4_kkimodo-g1-seed-q4_k_mname-modulo-quant,weight-filenamekimodo-g1-seed; same primary weight filename once quantization markers are stripped:kimodo-g1-seed-v1; same upstream repolocalai-io/kimodo-g1-seed-v1-ggml; differing quantization tokens:f32,g1,q4_k_mkimodo-g1-seed-q5_kname-modulo-quant,weight-filenamekimodo-g1-seed; same primary weight filename once quantization markers are stripped:kimodo-g1-seed-v1; same upstream repolocalai-io/kimodo-g1-seed-v1-ggml; differing quantization tokens:f32,g1,q5_kkimodo-g1-seed-q6_kname-modulo-quant,weight-filenamekimodo-g1-seed; same primary weight filename once quantization markers are stripped:kimodo-g1-seed-v1; same upstream repolocalai-io/kimodo-g1-seed-v1-ggml; differing quantization tokens:f32,g1,q6_kkimodo-soma-rpkimodo-soma-rp-bf16name-modulo-quant,weight-filenamekimodo-soma-rp; same primary weight filename once quantization markers are stripped:kimodo-soma-rp-v1.1; same upstream repolocalai-io/kimodo-soma-rp-v1.1-ggml; differing quantization tokens:bf16,f32kimodo-soma-rp-q4_kname-modulo-quant,weight-filenamekimodo-soma-rp; same primary weight filename once quantization markers are stripped:kimodo-soma-rp-v1.1; same upstream repolocalai-io/kimodo-soma-rp-v1.1-ggml; differing quantization tokens:f32,q4_kkimodo-soma-rp-q4_k_mname-modulo-quant,weight-filenamekimodo-soma-rp; same primary weight filename once quantization markers are stripped:kimodo-soma-rp-v1.1; same upstream repolocalai-io/kimodo-soma-rp-v1.1-ggml; differing quantization tokens:f32,q4_k_mkimodo-soma-rp-q5_kname-modulo-quant,weight-filenamekimodo-soma-rp; same primary weight filename once quantization markers are stripped:kimodo-soma-rp-v1.1; same upstream repolocalai-io/kimodo-soma-rp-v1.1-ggml; differing quantization tokens:f32,q5_kkimodo-soma-rp-q6_kname-modulo-quant,weight-filenamekimodo-soma-rp; same primary weight filename once quantization markers are stripped:kimodo-soma-rp-v1.1; same upstream repolocalai-io/kimodo-soma-rp-v1.1-ggml; differing quantization tokens:f32,q6_kkimodo-soma-seedkimodo-soma-seed-bf16name-modulo-quant,weight-filenamekimodo-soma-seed; same primary weight filename once quantization markers are stripped:kimodo-soma-seed-v1.1; same upstream repolocalai-io/kimodo-soma-seed-v1.1-ggml; differing quantization tokens:bf16,f32kimodo-soma-seed-q4_kname-modulo-quant,weight-filenamekimodo-soma-seed; same primary weight filename once quantization markers are stripped:kimodo-soma-seed-v1.1; same upstream repolocalai-io/kimodo-soma-seed-v1.1-ggml; differing quantization tokens:f32,q4_kkimodo-soma-seed-q4_k_mname-modulo-quant,weight-filenamekimodo-soma-seed; same primary weight filename once quantization markers are stripped:kimodo-soma-seed-v1.1; same upstream repolocalai-io/kimodo-soma-seed-v1.1-ggml; differing quantization tokens:f32,q4_k_mkimodo-soma-seed-q5_kname-modulo-quant,weight-filenamekimodo-soma-seed; same primary weight filename once quantization markers are stripped:kimodo-soma-seed-v1.1; same upstream repolocalai-io/kimodo-soma-seed-v1.1-ggml; differing quantization tokens:f32,q5_kkimodo-soma-seed-q6_kname-modulo-quant,weight-filenamekimodo-soma-seed; same primary weight filename once quantization markers are stripped:kimodo-soma-seed-v1.1; same upstream repolocalai-io/kimodo-soma-seed-v1.1-ggml; differing quantization tokens:f32,q6_kDeclined by the ledger (9)
Candidates the heuristics found and the ledger has already settled. They are listed so the ledger's effect stays visible rather than silently shrinking the job's output.
kokoros+kokoros-cmn: different languages: one Kokoro release per language, not alternative builds of one modelkokoros+kokoros-de: different languages: one Kokoro release per language, not alternative builds of one modelkokoros+kokoros-ja: different languages: one Kokoro release per language, not alternative builds of one modelkokoros-cmn+kokoros-de: different languages: one Kokoro release per language, not alternative builds of one modelkokoros-ja+kokoros-cmn: different languages: one Kokoro release per language, not alternative builds of one modelkokoros-ja+kokoros-de: different languages: one Kokoro release per language, not alternative builds of one modelllama-3.2-1b-instruct:q4_k_m+bert-embeddings: different parameter sizes (segment "1b")mistralai_mistral-small-3.1-24b-instruct-2503+mistralai_mistral-small-3.1-24b-instruct-2503-multimodal: different capability surface: the multimodal entry adds a vision projectorwhisper-1+whisper-base: alias: identical payload, whisper-1 is the name OpenAI-compatible clients sendFound but refused (12)
Candidates the heuristics found but the authoring rules would not let this job write. They need a human edit or a rule change.
gemma-4-12b-it-q4+gemma-4-12b-it-q5+gemma-4-12b-it-q6+gemma-4-12b-it-q8+gemma-4-12b-it-qat-q4_0: the parent "gemma-4-12b-it-q4" defines YAML anchor &gemma-4-12b-it, and a variants key added there is inherited by the 3 entries that merge it (gemma-4-12b-it-q5, gemma-4-12b-it-q6, gemma-4-12b-it-q8). Grouping this family by hand also means adding an explicitvariants: []to each of those entriesglm-5.3-flash+glm-5.3-flash-q4+glm-5.3-flash-q8: "glm-5.3-flash-q4" already offers variants of its own, so it cannot itself be a variant targetgranite-4.2-30b-q4+granite-4.2-30b-q8+granite-4.2-30b:vllm: the parent "granite-4.2-30b-q4" defines YAML anchor &granite-4-2-30b, and a variants key added there is inherited by the 1 entries that merge it (granite-4.2-30b-q8). Grouping this family by hand also means adding an explicitvariants: []to each of those entriesgranite-4.2-3b-q4+granite-4.2-3b-q8+granite-4.2-3b:vllm: the parent "granite-4.2-3b-q4" defines YAML anchor &granite-4-2-3b, and a variants key added there is inherited by the 1 entries that merge it (granite-4.2-3b-q8). Grouping this family by hand also means adding an explicitvariants: []to each of those entriesgranite-4.2-8b-q4+granite-4.2-8b-q8+granite-4.2-8b:vllm: the parent "granite-4.2-8b-q4" defines YAML anchor &granite-4-2-8b, and a variants key added there is inherited by the 1 entries that merge it (granite-4.2-8b-q8). Grouping this family by hand also means adding an explicitvariants: []to each of those entriesornith-1.0-9b-q4+ornith-1.0-9b-q8+ornith-1.0-9b: "ornith-1.0-9b-q4" already offers variants of its own, so it cannot itself be a variant targetornith-1.5-35b-a3b-apex+ornith-1.5-35b-a3b-q4+ornith-1.5-35b-a3b-q8+ornith-1.5-35b-a3b-q5+ornith-1.5-35b-a3b-q6: the parent "ornith-1.5-35b-a3b-q4" defines YAML anchor &ornith-1-5-35b-a3b, and a variants key added there is inherited by the 3 entries that merge it (ornith-1.5-35b-a3b-q8, ornith-1.5-35b-a3b-q5, ornith-1.5-35b-a3b-q6). Grouping this family by hand also means adding an explicitvariants: []to each of those entriesornith-1.5-9b-uncensored+ornith-1.5-9b-uncensored-q4+ornith-1.5-9b-uncensored-q6+ornith-1.5-9b-uncensored-q8: "ornith-1.5-9b-uncensored-q4" already offers variants of its own, so it cannot itself be a variant targetqwen3.8-27b+qwen3.8-27b-q4+qwen3.8-27b-q8: "qwen3.8-27b-q4" already offers variants of its own, so it cannot itself be a variant targetqwen3.8-27b-uncensored+qwen3.8-27b-uncensored-q4+qwen3.8-27b-uncensored-q8: "qwen3.8-27b-uncensored-q4" already offers variants of its own, so it cannot itself be a variant targetspark-x2.5-4b+spark-x2.5-4b-q4+spark-x2.5-4b-q6+spark-x2.5-4b-q8: "spark-x2.5-4b-q4" already offers variants of its own, so it cannot itself be a variant targetwhisper-1+whisper-base-q5_1: the natural parent "whisper-base-q5_1" is already a variant of "whisper-base"; proposing it as a parent would nest variantsOpened by
.github/ci/variantproposals. Heuristics and the rejection ledger live there and in the ledger file; a wrong proposal is a bug in one of the two.