Skip to content

repro/numerics: measured L4/L5 GF16 vs bf16/fp16 accuracy oracle (Closes #1072) - #1073

Closed
gHashTag wants to merge 1 commit into
masterfrom
repro/numerics-l4-l5-oracle
Closed

repro/numerics: measured L4/L5 GF16 vs bf16/fp16 accuracy oracle (Closes #1072)#1073
gHashTag wants to merge 1 commit into
masterfrom
repro/numerics-l4-l5-oracle

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Summary

Closes #1072.

Fills the L4 (differential) and L5 (comparative) TBD cells in docs/NUMERICS_VALIDATION.md with measured, reproducible round-trip accuracy numbers for GoldenFloat GF16 (E6M9) versus bfloat16 and IEEE float16, per docs/GF16_BFLOAT16_NMSE_PROTOCOL.md.

What's added

  • repro/numerics/nmse_gf16.py — round-trips real -> format -> real through the GF16 codec SSOT (conformance/gf16_ref.py), ml_dtypes.bfloat16, and numpy.float16; computes NMSE, NMSE ratios, max-abs-err, a ULP-like (kappa-approx) metric, and an overflow/saturation rate over D_NORM, D_LOG, D_RELU, D_PHI, D_DEEP, plus a documented wide-range extension D_WIDE. Enforces the L5 identity witness and aborts non-zero on failure or negative NMSE.
  • repro/numerics/nmse_manifest.json — protocol section-6 manifest (seed 2718281, 2,000,000 samples/distribution).
  • repro/numerics/README.md — measured results table + honest interpretation.
  • docs/NUMERICS_VALIDATION.md — TBD cells in sections 4/5/6 replaced with measured values; section 11 + closing line updated.

Measured headline (host, unsealed)

  • GF16 NMSE is ~16x lower than bf16 (ratio ~0.063, 9 vs 7 mantissa bits).
  • fp16 is ~4x more accurate than GF16 near 1.0 (10 vs 9 mantissa bits) — stated plainly.
  • On D_WIDE (log2|x|~U(-28,28)) fp16 overflows 21.4% of samples; GF16 (max ~4.29e9) and bf16 lose none — the honest exponent/mantissa tradeoff (protocol section 3.3), matching IBM DLFloat (DOI 10.1109/ARITH.2019.00023) and Popescu et al. (arXiv:2103.15940).

Honesty (R5-HONEST)

Host-measured, unsealed => informational, not a silicon certifying claim. D_PHI is an identity sanity check, not a superiority claim. ASCII-only. L6 SSOT untouched.

Closes #1072.

Add repro/numerics/{nmse_gf16.py,nmse_manifest.json,README.md} and fill the
L4/L5 TBD cells in docs/NUMERICS_VALIDATION.md with measured, reproducible
round-trip NMSE/ULP numbers for GF16 (E6M9) vs bfloat16 and float16, per
docs/GF16_BFLOAT16_NMSE_PROTOCOL.md. Host-measured, unsealed => informational,
not a silicon certifying claim. D_PHI is an identity sanity check.

Closes #1072
@gHashTag
gHashTag force-pushed the repro/numerics-l4-l5-oracle branch from 7af9080 to aa395e9 Compare June 14, 2026 11:38
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-06-14 11:38:23 UTC

Summary

Status Count
Total Open PRs 10
PRs with Failing Checks 8
PRs with All Checks Green 2
READY 1
FAILING 8
PENDING 0

@github-actions

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@gHashTag

Copy link
Copy Markdown
Owner Author

Этот PR полностью перекрыт уже смерженным #1075 (коммит 2962148 на master). #1075 был собран поверх ветки #1073 и squash-merge'нут, поэтому master уже содержит все изменения из #1073 ПЛЮС сертифицирующий NMSE-манифест и seal-hash honesty. Мердж #1073 (aa395e9) сейчас УДАЛИЛ бы repro/numerics/nmse_manifest_protocol_v1.json и repro/numerics/validate_manifest.py и откатил бы улучшения Makefile/docs. Измеренный L4/L5 oracle живёт на master. Работа отслеживается в #1072. Закрываю как superseded.

@gHashTag gHashTag closed this Jun 14, 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.

L4/L5 measured numeric-accuracy oracle: GF16 vs bf16/fp16 (repro/numerics)

1 participant