Home Developers Capabilities Heatsink Thermal Resistance

Verified calculation capability

Heatsink Thermal Resistance Calculation Capability

Junction temperature from effective θJA or θJC+θCS+θSA, or required heatsink θSA,max = (Tj,max−Ta)/P − θJC − θCS. · Electrical · Thermal

Capability ID electrical.thermal.heatsink_rth · version 1.1.0

Model

Effective θJA

Solve modes: junction effective ja · junction heatsink stack · required heatsink sa · rise · rth

Inputs / Outputs

Canonical symbols for this capability. Agent schemas remain the contract.

SymbolQuantityUnitRole
TaAmbient temperature (°C)°Cinput / output
PDevice power dissipation converted to heat (W). ≥ 0 on rise models; > 0 when solving θSA.Winput / output
Rth_JAEffective / application junction-to-ambient thermal resistance (°C/W ≡ K/W)input / output
Rth_JCJunction-to-case thermal resistance (°C/W)input / output
Rth_CSCase-to-sink / TIM interface thermal resistance (°C/W). 0 means the interface is neglected.input / output
Rth_SASink-to-ambient thermal resistance (°C/W) — the heatsink. Input on stack mode; output as Rth_SA_required on required mode.input / output
Tj_maxRequired on required_heatsink_sa. Optional on rise models for thermal margin.°Cinput / output
thermal_pathJA = effective θJA; JC+CS+SA = explicit heatsink stack; required_SA = solved θSA,max. Not interchangeable models.output
Rth_C_perHeadline resistance: θJA or θtotal on rise models; θSA,max on required_heatsink_saWoutput
Rth_totaloutput
Rth_total_max(Tj,max−Ta)/P in required modeoutput
Rth_SA_requiredoutput
dT°Coutput
dT_JC°Coutput
dT_CS°Coutput
dT_SA°Coutput
Tj°Coutput
margin°Coutput

Assumptions / Validity

Declared scope for this capability. Do not use it outside this domain.

Assumptions

Example

One numerical check. The calculator page holds worked steps and FAQ.

Ta=25, P=10, Tj_max=150, θJC=1.5, θCS=0.5 → θSA,max=10.5

Open this example in the calculator

Trust

CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance. Computational verification is defined by CVP. Supplemental domain review (internal) and named expert review are defined by the Review policy and do not by themselves determine CVP conformance.

CVP
CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance· View Manifest · CVP overview · Specification
Assurance
Engineering
Declared partition coverage
PASS · 4/4 declared partitions (ja, stack, required-sa, invalid-domain)
Calculation version
1.1.0
Verification
17/17 calculation tests · 4/4 legacy golden · 5/5 legacy boundary · 8/8 legacy property
Production surface contract
4/4
Versions
Calculation 1.1.0 · CVP protocol 1.0.0-proposed
CVP identity
3/3 property · digest e84796291008
Reference
O1 model · O2 expected_values · O2 numerical_behavior
Interfaces
PASS · UI (SSR) / REST / MCP
ui-ssr is query-result HTML, not a live browser session.
CVP suite
4/4 golden · 8/8 CVP boundary · 9/9 invalid · 3/3 property · 3/3 metamorphic · 2/2 round-trip · 3/3 cross-interface · 1/1 cross-calculator · 4/4 CVP contract
Supplemental domain review
Internal · Pass · electrical-engineer
Named expert review
Not performed
Version lock
Supported (409 VERSION_MISMATCH)
Artifact consistency
Build verified · 1.1.0 (workspace artifacts agree)
Review-policy tier
Internally reviewed — catalog token internally_reviewed; supplemental; not CVP status
This calculator CURRENT · Public schema 1.1.0 matches · Semantic contract ✓ · Production attested · Public/cache ✓ · Origin ✓

Call this capability

Human page, REST, and MCP share the same engine and calculation_version. Build verified hashes workspace artifacts only. After deploy, attest:production GETs canonical URLs twice — the public/cached view an Agent actually hits, and origin — including every /capabilities/{id} HTML page. Public Capability HTML version must match catalog before production attestation passes. Live Trust rows above fetch /.well-known/calculatorx-production-attestation.json and the output schema const. Build hashes: release integrity. That proves currently published page / engine / schema / evidence / MCP agree — not that a historical version is independently immutable. Reference Calculation Standard — Production surface contract 4/4.

Tool id
heatsink-rth
Engine
heatsink-rth
REST
POST /api/v1/calc/heatsink-rth
MCP
execute_calculation with capability_id: "electrical.thermal.heatsink_rth"
Agent input schema
Canonical (MCP / Agent)
Output schema
JSON Schema (latest)
Versioned input schema
Immutable pin (1.1.0)
Versioned output schema
Immutable pin (1.1.0)

Operations

Declared calculation modes for this capability.

References

Human-readable sources plus CVP reference evidence classes.

Sources

Reference evidence classes: O1 model · O2 expected_values · O2 numerical_behavior

Try with an agent

Inspect this capability via same-origin MCP, then call execute_calculation.

curl -sS -X POST 'https://www.calculatorx.com/mcp' \
  -H 'Content-Type: application/json' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -H 'Mcp-Method: tools/call' \
  -H 'Mcp-Name: inspect_capability' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"inspect_capability","arguments":{"capability_id":"electrical.thermal.heatsink_rth"}}}'

Inspect the trust tier and required assurance level before execution. Pin calculation_version (1.1.0) when reproducibility matters. Full protocol notes: MCP docs.