Add exact robust-code constructions and residual precision (CAP0-03, SLM-79)#327
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 36 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…SLM-79)
Torch-free coding-theory utilities for arity analysis: exact robust-code
constructions (Hamming/Singleton/GV bounds, MDS + shortened ternary-Hamming),
residual precision (trit-planes/ECOC), and arity suggestions.
smallest_injective_arity delegates to main's canonical
report.min_alphabet_for_capacity (exact integer K^d search) — a single source
of truth for capacity. Additive package exports; the canonical arity package
(canonical/minimize/report/state_graph) is untouched.
- arity/{coding,precision,suggest}.py + 16 tests + design doc.
- Deferred as out-of-scope: the report CodingMetadata/ArityReport contract and
the analyzer stub the source branch also carried (those targeted the retired
arity stub #323, not main's canonical ExactArityReport from #354).
Canonical arity no-regression: test_arity_analysis 21 passed unchanged.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017NWyjZwGMUPHXZhtqQVzUJ
c17d9e2 to
71e9175
Compare
Tyler-R-Kendrick
changed the title
2 participants
CAP0-03 (SLM-79): exact robust-code constructions and residual precision
Adds torch-free coding-theory utilities to the arity analysis package.
What's here (7 files, +708/−0, on current
main)arity/coding.py— exact robust-code constructions: Hamming / Singleton / GV bounds,verify_code, MDS + shortened ternary-Hamming.smallest_injective_aritydelegates to main's canonicalreport.min_alphabet_for_capacity(exact integer K^d search) — a single source of truth for capacity.arity/precision.py— residual precision (trit-planes / ECOC).arity/suggest.py— arity suggestions (imports onlycoding.py).arity/__init__.py— additive CAP0-03 re-exports; canonical exports and modules untouched, never imports the retired stub.Scope
The
coding/precision/suggestmodules are self-contained (stdlib only) — not coupled to the deleted arity stub. Deferred as out-of-scope: the source branch'sreport.pyCodingMetadata/ArityReportcontract, theanalyzer.pystub, and the--include-coding-metadataflag — all targeting the retired stub (#323), not main's canonical arity package (#354).Verification (torch-free)
test_arity_analysis.py21 passed (unchanged); canonical files byte-identical; stub absent.test_arity_coding+test_arity_suggest: 16 passed.ruff/repo_policy/diff-checkclean.🤖 Generated with Claude Code