/ Модель

Характеристики

Контекст
256 токенов
Параметры
24 832
Размер весов
1 МБ
Лицензия
Своя лицензия
Архитектура
minimax_m2 · MoE
Библиотека
transformers
Опубликована
7 сен 2026

minimax-m2-tiny-random-bf16

Генерация текстаТекст → текст3 профессии

Небольшая случайно инициализированная модель MiniMax M2 для отладки, воспроизводимости и тестирования инструментов работы с причинными языковыми моделями.

141скачиваний за 30 дней0лайковвеса обновлены7 сен 2026

Бенчмарки

Как модель справилась с задачами пользователей ailist и что о ней публикуют открытые лидерборды

Тесты пользователейпока нет

Никто ещё не опубликовал тест этой модели. Соберите бенчмарк из своих задач — результат появится здесь.

  1. Добавьте модель в бенчмарк

    Вместе с другими моделями категории «Текст» — сравнение идёт внутри одной категории.

  2. Опишите свои задачи

    Напишите запросы, при необходимости приложите файлы и эталонные ответы.

  3. Запустите и опубликуйте

    Модели ответят на каждую задачу, судья оценит ответы. Опубликованный результат появится на этой странице.

Публичные оценки

Из открытых лидербордов. Сравнивайте результаты одного теста при одинаковых условиях — отсутствие оценки не значит, что модель хуже.

В подключённых источниках результатов для этой модели пока нет.

Что умеет модель

Описание составлено по карточке модели и метаданным Hugging Face

malaiwah/minimax-m2-tiny-random-bf16 — небольшой эталонный случайный чекпойнт семейства MiniMax M2, созданный пользователем malaiwah для обучения, отладки и воспроизводимости рабочих процессов QFS. Это не копия обученной производственной модели и не содержит унаследованных от неё весов или данных обучения.

Модель предназначена для генерации текста через pipeline text-generation и реализует причинную языковую модель с архитектурой sigmoid/top-k MoE, коррекцией маршрутизации, RMSNorm для Q/K и частичным RoPE. В метаданных указаны 24,8 тыс. параметров, контекст до 256 токенов, библиотека Transformers и CPU-ориентированный сценарий использования. В README также отмечены независимый байтовый токенизатор на 272 токена, отсутствие визуальных параметров и отсутствие MTP.

Чекпойнт удобен для проверки загрузки тензоров, адаптеров моделей, декодеров хранилища, захвата скрытых состояний, воспроизводимости и регрессионного тестирования на небольших синтетических наборах. Сгенерированный текст не обладает полезным семантическим качеством, поэтому модель не подходит для ассистентов, оценки качества языка, прикладного инференса или сравнения производительности. Лицензия указана как other с условиями minimax-upstream-terms.

Сценарии применения

  • отладка загрузки и строгой проверки тензоров
  • тестирование адаптеров архитектуры MiniMax M2
  • захват и воспроизведение скрытых состояний
  • регрессионное тестирование QFS на синтетических данных
  • проверка воспроизводимости CPU-инференса

Ограничения

Веса не обучены, поэтому текст не имеет полезного семантического качества и модель не предназначена для ассистирования или оценки языковых способностей. Не подтверждены точность обученной модели, поведение на длинном контексте, производительность, совместимость с производственными весами и работа FP8 на GPU или других ускорителях.

Для каких профессий подходит3

Разделы каталога профессий, в задачах которых используется эта модель

Все профессии

Карточка модели

README от автора на Hugging Face, как он его опубликовал

Открыть на Hugging Face

MiniMax M2: a tiny toolchain fixture

A small, independently initialized random-weight reference model for learning, debugging, and reproducing QFS capture workflows. It is a base/root fixture, not a quantized child.

These weights are untrained, not an assistant, and not a language-quality benchmark. Generated text has no useful semantic quality. No upstream trained weights or training data are implied by an architecture name.

Weight lineage

This checkpoint was initialized directly for an architecture test. It was not fine-tuned from a production model and does not inherit that model's trained weights. Architecture/configuration lineage is documented separately from weight lineage.

Browse the Random Architecture Fixtures collection. A random base may also serve as the common source for an aligned quantization family.

At a glance

PropertyObserved value
Artifact roleBase/reference model; capture role root
Serialized top-level weight files117,688 bytes (0.112 MiB); metadata, tokenizer and evidence excluded
Generated parameters55,024
Included vision parameters0; inclusion is not vision-quality evidence
Saved semantic tensors39 (parameters and buffers are not interchangeable)
Fixture vocabulary272 tokens; independent byte tokenizer, not upstream vocabulary
CPU stackPython 3.12; Torch 2.11.0+cpu; Transformers 5.16.1; two Torch threads in the recorded capture workflow
Remote model codeNot required: native Transformers class behind QFS

Size is serialized artifact size, not runtime RAM or a capacity/performance guarantee. Packed-array element counts are not model parameter counts.

What is actually included

Complete native text causal LM: sigmoid/top-k MoE routing with correction bias, per-layer flattened Q/K RMSNorm and half-head partial RoPE. No MTP. Official FP8 weights are not reproduced or CPU-qualified.

The repository file inventory includes config.json, generation_config.json, tokenizer.json, tokenizer_config.json, build-manifest.json, support.json, requirements-cpu.txt. Exact build/runtime/license inventories are linked below. A file may describe historical provenance without being an executable entry point.

Good community uses—and boundaries

  • Learn how to download pinned artifacts, seal a small synthetic token panel, capture hidden states and replay a full vocabulary head.
  • Debug model-family adapters, strict tensor loading, storage decoders, or reproducibility tooling without downloading a production-sized checkpoint.
  • Reproduce a narrowly scoped result, report an adapter/reader regression, and retain the source, panel and runtime identities needed to explain it.

Not established: trained-model accuracy; useful instruction following; quantizer optimization quality; original production-weight compatibility; GPU/NPU/serving-kernel parity; cross-hardware determinism; long-context behavior outside the recorded panel; throughput or paid-compute admission.

Original-release limitations

Official config requests dynamic FP8 e4m3fn with 128x128 blocks (router gate/correction bias/head exclusions), despite nominal dtype BF16. Native CPU random BF16 fixture does not exercise FP8 loading, dequantization or kernels. Original capture requires already-downloaded licensed weights and a supported sufficiently provisioned FP8 runtime, normally CUDA; no production hardware fit or performance claim. Original config advertises use_mtp=true, three MTP modules/one transformer layer; the native M2 causal LM has no MTP implementation. Never add dummy MTP state. Unexpected source MTP tensors must remain a strict refusal unless an exact reviewed tensor-name inventory is independently pinned with QFS existing unexpected-tensor allowlist; no broad missing/mismatch flags are permitted.

Model family, root dataset and evidence

This model is the base/root of its own random fixture family, not a reproduction of the trained upstream model. The fidelity-root dataset repository is the family reference location. A link is not a claim that registration or publication has completed.

The historical CPU evidence bundle retains two independent captures at first/ and repeat/, plus comparison/. Its repository root is a receipt bundle, not a single canonical QFS dataset. Those recorded same-machine/same-stack forced comparisons reported 0.0 nats on 252 synthetic scored positions; that is not a trained-quality result or a transferable hardware floor. The original detailed receipt and caveats remain authoritative.

Runtime requirements and safe local reproduction

Replay the published evidence without loading a model

This uses QFS's existing NumPy FP64 comparator in a Torch-free environment. It reads the stored hidden states and each side's own head. No model forward, remote model code, GPU, upload or registry mutation is involved. Runtime receipts name the actual backend; last-bit differences from another FP64 implementation are not a new quality claim. Synthetic exact controls remain zero.

Set QFS to a reviewed Quant Fidelity Suite checkout and use Bash:

: "${QFS:?Set QFS to your reviewed QFS checkout}"
WORK=$(mktemp -d)
export OMP_NUM_THREADS=2 MKL_NUM_THREADS=2 OPENBLAS_NUM_THREADS=2
python3.12 -m venv "$WORK/replay-env"
"$WORK/replay-env/bin/pip" install 'numpy==2.5.3' 'huggingface-hub==1.30.0'
"$WORK/replay-env/bin/hf" download malaiwah/qfs-fixture-root-captures-v1 --repo-type dataset \
  --revision f53b204091c988ce4a2161af81886f3018745559 --include 'roots/minimax-m2/**' --local-dir "$WORK/evidence"
"$WORK/replay-env/bin/python" "$QFS/bin/fidelity_dataset.py" verify \
  "$WORK/evidence/roots/minimax-m2/first" --verify-tensors
"$WORK/replay-env/bin/python" "$QFS/bin/fidelity_dataset.py" verify \
  "$WORK/evidence/roots/minimax-m2/repeat" --verify-tensors
"$WORK/replay-env/bin/python" "$QFS/bin/fidelity_dataset.py" compare \
  --reference "$WORK/evidence/roots/minimax-m2/first" \
  --candidate "$WORK/evidence/roots/minimax-m2/repeat" \
  --out "$WORK/replayed" --device cpu --replay-device numpy --replay-dtype float32 \
  --vocab-chunk 8192 --verify-tensors --self-compare --force-compute

Reconstructed format comparisons are intentionally advisory and normally return exit code 2 while writing a valid receipt. Inspect that receipt; do not silence refusals or interpret an advisory result as a production-quality ranking.

Capture the actual checkpoint

Capture uses a separate pinned Torch CPU environment. The input below is the original token-panel format, not a sealed capture's internal panel/ folder. The native source, tokenizer and model revisions remain explicit. Set AUTHOR to your own HF handle; the dataset repository argument is attribution only and nothing is uploaded by these commands.

: "${AUTHOR:?Set AUTHOR to your Hugging Face handle}"
"$WORK/replay-env/bin/hf" download malaiwah/minimax-m2-tiny-random-bf16 --revision d4825603496f1c636385af403e891aaf20e9afe6 --local-dir "$WORK/model"
"$WORK/replay-env/bin/hf" download malaiwah/minimax-m2-tiny-random-bf16 --revision d4825603496f1c636385af403e891aaf20e9afe6 --local-dir "$WORK/source"
"$WORK/replay-env/bin/hf" download malaiwah/qfs-fixture-root-captures-v1 --repo-type dataset \
  --revision f53b204091c988ce4a2161af81886f3018745559 --include 'requirements-capture.txt' --include 'roots/minimax-m2/input-panel/**' \
  --local-dir "$WORK/inputs"
python3.12 -m venv "$WORK/capture-env"
"$WORK/capture-env/bin/pip" install -r "$WORK/inputs/requirements-capture.txt"
"$WORK/capture-env/bin/python" "$QFS/bin/fidelity_dataset.py" architectures prepare \
  --architecture minimax-m2 --model-dir "$WORK/model" \
  --model-repository malaiwah/minimax-m2-tiny-random-bf16 --model-revision d4825603496f1c636385af403e891aaf20e9afe6 \
  --panel "$WORK/inputs/roots/minimax-m2/input-panel" --tokenizer-root "$WORK/source" \
  --author "$AUTHOR" --dataset-repository "$AUTHOR/minimax-m2-tiny-random-bf16-capture" \
  --dataset-id "fidelity--$AUTHOR.minimax-m2-tiny-random-bf16" --out "$WORK/workflow"

Inspect workflow.json. This launcher executes its exact capture/verification commands and selects the Torch-free interpreter only for the final comparison:

export OMP_NUM_THREADS=2 MKL_NUM_THREADS=2 OPENBLAS_NUM_THREADS=2
"$WORK/replay-env/bin/python" - "$WORK/workflow/workflow.json" <<'PY'
import json, subprocess, sys
workflow = json.load(open(sys.argv[1]))
for step in workflow["commands"]:
    argv = list(step["argv"])
    if step["step"] == "compare":
        argv[0] = sys.executable
    result = subprocess.run(argv)
    if result.returncode:
        raise SystemExit(result.returncode)
PY

Use the actual root at malaiwah/minimax-m2-tiny-fidelity-root-v1@0429feb8bc3f427e89e0ba2a341d28b82d431b0e. The community collection groups models and captures. Custom code, where required above, is explicitly pinned and executed only after your consent; hash verification is provenance, not a sandbox.

Licensing and detailed provenance

  • Fixture repository license: Exact upstream LICENSE retained conservatively; independently generated random weights, no upstream weights copied. Native Transformers runtime separately Apache-2.0. No vendored runtime Python.
  • Summary: MiniMax-M2.7 pinned NON-COMMERCIAL LICENSE: personal/noncommercial uses permitted; any commercial use requires prior written MiniMax authorization and Built with MiniMax M2.7 attribution. Exact upstream terms retained; no claim that the upstream release is MIT.

Selected original provenance fields (full tensor/component evidence remains in the linked inventories):

{
  "generation": "Complete seeded native FP32 initialization rounded to BF16; exact semantic native save/reload including dtype required. No loader guard overrides.",
  "generator_sha256": "3eb685652c96791a1a7da0e9da453426ade42e50f5a5bdeb9ef3abc4a9523299",
  "lineage": {
    "relationship": "architecture lineage only; no source weights copied",
    "repository": "MiniMaxAI/MiniMax-M2.7",
    "revision": "d494266a4affc0d2995ba1fa35c8481cbd84294b"
  },
  "native_fp32_exceptions": [],
  "parameter_count": 55024,
  "scope": "Complete native text causal LM: sigmoid/top-k MoE routing with correction bias, per-layer flattened Q/K RMSNorm and half-head partial RoPE. No MTP. Official FP8 weights are not reproduced or CPU-qualified.",
  "seed": 20260907,
  "versions": {
    "safetensors": "0.8.0",
    "tokenizers": "0.23.2",
    "torch": "2.11.0+cpu",
    "transformers": "5.16.1"
  },
  "vision_parameter_count": 0
}

Как запустить

На своей GPU в ailist. Цена — по текущим предложениям провайдеров

GPU в ailist

Универсальный рантайм · transformers

Можно запустить

Подбираем GPU…

Класс архитектуры
MiniMaxM2ForCausalLM
Ревизия весов
a8eff3b

0 моделей