FUMO / Research · Model evaluation and behavior analysis
Models are more than a score.
A comparative view of model scores, reasoning-trace text similarity, item-level outcomes, and version differences under documented evaluation conditions.
1 Start at the center model2 A shorter line means higher measured similarity3 Click any dot to recenter
Highest 0.899 · Lowest 0.765Compare every outer dot to the center
DS V4Selected
Center modelDeepSeek V4 Pro
Highest similarity in this setHY3
Character 3–5-gram · Higher is closer0.899 / 1.000
How to read: Each outer model is compared only with the center. Distances are rescaled within the selected center model and show relative order only; use the printed 0–1 values for absolute differences.
02
Current finding
Choose model versions
Performance on the same tasks / GPT 5.5 → 5.6 Sol → 6 Astra
Code analysis, translation & rewriting improves; agent tool use declines.
Across the same 68 tasks and 3 attempts per task, task pass rate followed 81.37% → 86.27% → 89.71% across versions. 5.5 → 5.6 Sol: coding implementation records 4 more passes; extraction & compression records 2 more passes; translation & rewriting records 2 fewer passes. 5.6 Sol → 6 Astra: code analysis records 6 more passes; translation & rewriting records 2 more passes; agent tool use records 2 fewer passes.
Pass rate · three attempts per task
GPT 5.581.37%GPT 5.6 Sol86.27%GPT 6 Astra89.71%
What changed
Sol strengthens implementation and information processing; Astra improves code analysis and restores translation performance. Implementation gains are smaller, while tool execution slips slightly.
5.55.6 Sol6 AstraPasses / attempts
Code analysis
17/24 → 18/24 → 24/24+6 attempts
Translation & rewriting
12/12 → 10/12 → 12/12+2 attempts
Agent tool use
29/30 → 30/30 → 28/30-2 attempts
Coding implementation
21/45 → 25/45 → 26/45+1 attempts
Critique & verification
26/27 → 27/27 → 27/270 attempts
Observed · FUMO Capability Evaluation · Each model answers the same 68 tasks three times. Bars show passes by category; changes compare 6 Astra with 5.6 Sol. Five categories with the largest differences are shown. See methods
03
Capability complementarity
Outcome overlap on matched tasks
Totals show how many. Outcomes show which.
Whether totals are similar or far apart, models may share some passes and each solve items the other misses. Both-pass, one-sided-pass, and both-fail counts reveal capability overlap, complementarity, and gaps hidden by totals.
24 models276 possible pairs68 matched now
24 configurations are eligible. Each pair uses only shared tasks with three graded attempts per model. Score cards retain each model’s own coverage; some models still have missing results.
Check-level labels can coexist with a task pass. These exploratory, non-exclusive counts are neither failed-answer totals nor prevalence estimates.
05
Interpretive limits
Scope and limits of interpretation.
All reported values and conclusions are conditional on the listed tasks, model versions, run configurations, and scoring rules.
Scope of inferenceEvaluation-conditional
All comparisons are conditional on the evaluated task set and run settings.
Similarity, category-level differences, and failure labels describe observations under specified conditions. Estimates may change with the task distribution, reasoning settings, tool policy, or model version.
Capability complementarityMatched-task outcomes
Aggregate scores do not identify which tasks each model passes.
Shared passes indicate overlap, while one-sided passes indicate relative strengths; together with shared failures, they describe complementarity and gaps within the evaluated task set.
Limits to generalizationSample coverage
Current results do not directly generalize to untested tasks or later model versions.
Task coverage, repetition count, and model-version changes all affect the estimates. Rare failures and cross-domain conclusions require additional independent replication.
06
Methods & data
Data definitions, inclusion rules, and computation.
From raw runs to displayed metrics, each step retains an explicit comparison unit and denominator. The rules below describe the data shown on this page, rather than a generic methodology statement.
01Raw runs
Lock model version, reasoning configuration, tasks, and repeats.
02Validity checks
Identify infrastructure failures, incomplete runs, and unresolved grades.
03Eligible cohort
Set the denominator actually used by each metric.
04Aggregation
Compute attempt success and stable-task pass separately.
05Pairwise comparison
Partition outcomes only where both models have valid results.
A run-level measure whose denominator excludes invalid observations.
Stable-task passall repeats pass ÷ eligible tasks
Used only for repeated-run benchmarks and kept separate from attempt success.
Matched-task overlapboth pass + one-sided pass + both fail
The four cells sum to the eligible matched items for the active model pair.
95% uncertainty intervaltask-level bootstrap
Trace-prefix intervention intervals use task-level resampling, keeping repeated observations grouped within each task.
Trace-text similaritycharacter 3–5-gram / word 1–3-gram
Two 0–1 text scales are reported separately; results with different task coverage are not pooled.
Check labelsexploratory, non-exclusive counts
One answer may carry multiple check labels even when it passes; counts are not prevalence estimates.
FUMO Capability Evaluation data updated 2026-09-12 · Evaluation methods. Evaluation data is continually reviewed. Additional runs and scoring-rule revisions may change scores and eligible sample counts.