moebiusT7's picture
v1.0.1 public package + figures + paper PDF (DOI 10.5281/zenodo.21875513)
21bbd75 verified
|
Raw
History Blame Contribute Delete
2.97 kB

Reproduce

Environment, model digests, and suite/label SHA-256: ENVIRONMENT.md.

Harness

Public at github.com/mobius-style/mmv, directory operate-fr-bench/ (AGPL-3.0). The four profiles used here (gemma4_12b_…, gemma4_12b_qat_…, gemma4_26b_…, gemma4_26b_a4b_qat_…, all …route_transformer_plus_validator_v3_1) share identical governance flags; both Q4_0 profiles pin extra.num_ctx: 8192 because their Modelfiles declare a 262,144-token context whose KV allocation fails on a 16 GB card (load feasibility only — suite prompts are far below 8,192 tokens). think: false everywhere. Unload the previous model (ollama stop <tag>) between cells; a resident sibling model causes CUDA allocation failure.

Models (Ollama tags)

gemma4:12b (PTQ Q4_K_M, 11.9B dense) · gemma4:12b-it-qat (QAT Q4_0, 11.9B dense) · gemma4:26b (PTQ Q4_K_M, 25.8B MoE) · gemma4:26b-a4b-it-qat (QAT Q4_0, 25.2B MoE, ~4B active). Content digests in ENVIRONMENT.md.

Runs (sequential, one cell at a time, from operate-fr-bench/)

python3 -m harness.run_eval --suite configs/suite_smoke.yaml   --profile <PROFILE> --out reports/<CELL>.jsonl
python3 -m harness.score    --results reports/<CELL>.jsonl --labels data/labels/smoke100_route_labels.jsonl --out reports/<CELL>_smoke_summary.json
python3 -m harness.run_eval --suite configs/suite_core500.yaml --profile <PROFILE> --out reports/<CELL>_core500.jsonl
python3 -m harness.score    --results reports/<CELL>_core500.jsonl --labels data/labels/core500_route_labels.jsonl --out reports/<CELL>_core500_summary.json

Determinism baselines and controls: Smoke-100 repeats for all four cells (12B same-day; 26B 8–10 h later across a date boundary; all 100/100 byte-identical, including the CPU-offloaded 26B-PTQ cell), plus a num_ctx: 8192 control re-run of the 12B-PTQ cell (100/100 byte-identical vs default context).

Suite availability

The OPERATE-FR Smoke-100 / Core-500-candidate items are project-local and not redistributed (they are identified by SHA-256 in ENVIRONMENT.md). Reproduction on the same items requires access to the private suite archive; reproduction of the design on other routing suites requires only the public harness.

Analysis

OPFR_BENCH_ROOT=/path/to/operate-fr-bench python3 analysis/analyze_2x2.py

Deterministic (bootstrap seed 20260810; the interaction is reported with a stem-clustered CI — primary, since Core-500 is 100 stems × 5 paraphrases — and a task-iid CI). Regenerates every routing table in data/ from row level, including the per-family table (families read from the suites' authoritative family fields). The safety rates quoted in the paper come from the harness scorer's summary outputs, archived privately with the raw rows. Row-level artifacts (13 runs, 2,900 rows, 0 errored) are excluded from the public package (see README.md); their SHA-256 hashes are in data/RAW_ARTIFACT_HASHES.sha256.