electrical.adc.error_budget

Three distinct suites: educational examples on the calculator page, this legacy regression count (11/11 golden + boundary), and the CVP verification suite below. They are not the same number. Property, metamorphic, round-trip, O3, and interface statuses/checks are recorded in the CVP Manifest . SKIP (0/0) means that suite has no published vectors.

This calculator CURRENT · Public schema 1.0.0 matches · Semantic contract ✓ · Production attested · Public/cache ✓ · Origin ✓

CVP verification suite

Protocol checks from the Evidence Manifest. Distinct from the legacy regression suite above. Verification revision 2026-10-28.meta-metrics-v2. Calculation version 1.0.0. CVP 1.0.0-proposed. 6/6 golden · 5/5 CVP boundary · 5/5 invalid · 4/4 property · 6/6 metamorphic · 6/6 cross-interface · 6/6 CVP contract. digest 2a02032d97a8. Static DC LSB/V/%FS error-budget vs independent O2 (same V8, ≤2 ULP on err_LSB, LSB_V, err_V, err_pct_FS, codes). Not measured converter accuracy, not datasheet TUE that omits DNL, not O3.

• Golden (oracle-backed) 6 / 6
• CVP boundary 5 / 5
• Invalid input 5 / 5
• Property 4 / 4
• Metamorphic 6 / 6
• Cross-interface 6 / 6
• CVP contract 6 / 6
• Interfaces PASS · UI (SSR) / REST / MCP
• Interface claim ui-ssr is query-result HTML, not a live browser session. Error-path engine·REST·MCP 4/4 (status, code, calculation_version). SSR compared on URL-canonical requested calculations; empty query is idle (not an error) and JSON-typed object/array inputs are REST/MCP-only. Probes use local Node handlers (query-result, calc API, MCP executeCalculation), not live production HTTP.
• Verified scope static DC LSB error-budget calculation
• Assurance Engineering

• release artifacts aligned PASS
• schema output required declared PASS
• schema valid input executes PASS
• engine success output validates schema PASS
• schema rejects incomplete input PASS
• rest success payload validates schema PASS

Fingerprint sha256:7223200bb31f9c768edc3b8bcd4d3b69bd7d0eac85a0c46ddb757502c253dfab

Input schema sha256:10e5d92e79e9a2192a81c1c96a7383d4b4eebb8d7dfdb7daa0d93f348e2e321f · Output schema sha256:bc2424d86172e14ac883bcf4d96c07f9a749d435f507adbf95b431d27c6877dc · Build-time SHA-256 digests prove published artifacts agree with each other (release_integrity.scope=workspace). Production attestation GETs canonical URLs twice (public/cached view and origin), including Capability HTML, via npm run attest:production --write (published at /.well-known/calculatorx-production-attestation.json) and fails if the public Capability page advertises a different calculation_version. This is artifact consistency, not an independent immutable release log.

Tool

adc-error-budget

Engine

adc-error-budget

Engine build

2026-09-10

Evidence core

2026-09-05T02:35:39.217Z

Rendered

2026-11-10T05:18:41.755Z

Last reviewed

2026-09-03

Assumptions

• Gain, offset, INL, and DNL values are already referred to LSB.
• RSS assumes contributors can be treated as independent/uncorrelated.
• FSR_V represents the full ADC input span.
• CalculatorX includes DNL as a separate RSS/worst-case contributor. Some ADC datasheets define TUE using gain, offset, and INL only.

Limitations

• Static DC errors only.
• Quantization ±0.5 LSB is separate unless included in the INL/DNL terms you enter.
• CalculatorX includes DNL as a separate RSS/worst-case contributor. Some ADC datasheets define TUE using gain, offset, and INL only.