Skip to content

docs: document GigaAM Multilingual Large CTC on the GigaAM model page - #256

Merged
cjpais merged 1 commit into
handy-computer:mainfrom
vlsi:gigaam-multilingual-docs
Nov 11, 2026
Merged

cjpais merged 1 commit into
handy-computer:mainfrom
vlsi:gigaam-multilingual-docs

Conversation

@vlsi

@vlsi vlsi commented Nov 11, 2026

Copy link
Copy Markdown
Contributor

PR #251 added a converter for gigaam-multilingual-large-ctc but updated only the porting docs. The user-facing page docs/models/gigaam.md still described the family as four Russian-only v3 variants, so a reader looking for Kazakh, Kyrgyz, Uzbek, or English found no way to get the model.

The page now names the variant in the intro and in "Choosing a variant", and a new section gives its languages, output, the convert, quantize, and run commands, the --language behavior (run: unsupported language outside ru, en, kk, ky, uz), and the quant parity checked on Metal. Sentences that held only for v3 (shared encoder, pre-built GGUFs) are scoped to v3. Every number and command comes from the family doc section GigaAM Multilingual Large CTC and scripts/convert-gigaam.py; scripts/catalog/render.py --check reports no stale regions.

Scope. The variant is not added to the README or to the catalog-rendered tables: they come from catalog/, and the variant has no published GGUF, WER, or benchmark yet, while the README says every published model is WER-tested. The input-limits section states that the 25 s window has not been checked on a longer clip for this variant. Part of #87.

PR handy-computer#251 added a converter for gigaam-multilingual-large-ctc but updated
only the porting docs. The user-facing page docs/models/gigaam.md still
described the family as four Russian-only v3 variants, so a reader
looking for Kazakh, Kyrgyz, Uzbek, or English found no way to get the
model.

The page now names the variant in the intro and in "Choosing a
variant", and a new section gives its languages, output, the convert,
quantize, and run commands, the --language behavior, and the quant
parity checked on Metal. Claims that held only for v3 (shared encoder,
pre-built GGUFs) are scoped to v3, and the input-limits section says
the 25 s window is unverified for this variant.

The variant stays out of the README and the catalog tables: those are
rendered from catalog/, and the variant has no published GGUF, WER, or
benchmark yet.

Part of handy-computer#87.

Assisted-by: Claude Opus 5.5
@vlsi
vlsi requested a review from cjpais as a code owner November 11, 2026 06:07
@cjpais
cjpais merged commit 60c5b51 into handy-computer:main Nov 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants