Electric potential difference → Useful heat
Electric potential differenceEttingshausen effectTemperature gradientThermal expansionMechanical stress or strainElastocaloric effectUseful heat
Epistemic state of the route
- known constituent relations
- 5 / 6 established or replicated · weakest constituent demonstrated
- constituent maturity floor
- K4 · experimentally observed
- search for this exact route
- Not assessed — complete composition not searched.
- recorded-pathway overlap
- shares relations, in order, with Bimetallic-strip piezoelectric harvester · 2/6 relations shared
- route-level evidence
- 0 sources for the complete composition · 8 cited by the constituent steps
- boundaries and interfaces
- BOUNDARY compatible · no region transition
Explorematrix context · physics checks · steps · route evidence · constituent evidence · cite
Matrix context
D = disequilibrium row · C = coupling family column. A cell reads the state of the atlas for that pair.
D.06 × C.01 · Electric potential difference × Thermoelectricfamily: ThermoelectricD.06 × C.08 · Electric potential difference × Heat engine (thermomechanical)family: Heat engine (thermomechanical)D.06 × C.09 · Electric potential difference × Caloric (magneto/electro/elasto)family: Caloric (magneto/electro/elasto)
Typed bounds on this route
Every limit the atlas holds for this route, as constraint records: reached through bounded_by claims on the route's own entities. Hard bounds (an upper bound or a formula) decide the thermodynamic-bound check above; benchmarks, constitutive relations and resource limits are listed and never decisive. No prose limit exists anywhere (pass 42).
- Carnot limit · formula-bound · hard, filtered out by its applicabilityη ≤ 1 − T_c/T_h for any heat engine between reservoirs at T_h and T_c
Steps
- 01electrical → thermal
- a current in a conductor with a perpendicular magnetic field
solid · conductor required · magnetic field requiredrefs [1] [2] - 02thermal → thermalrefs [2] [3]
- 03thermal → mechanicalrefs [4] [5]
- 04mechanical → mechanical
- non-uniform thermal expansion is mechanically incompatible across adjacent regions of a solid, or is constrained by an adjoining material or structure, producing a strain or stress gradient; the constraining region may be the cooler part of the same continuous specimen rather than a separate stiffer body
solidrefs [6] [5] - 05mechanical → thermal
- stress large enough to drive the martensitic transformation of a shape-memory alloy
solidrefs [7] [8] - 06thermal → thermal · loss to thermalrefs [7]
Evidence for the complete composition · 0
No source on record for this exact composition. The sources below support the individual steps, not the route as a whole.
Evidence for the constituent relations · 8
- [1]A. von Ettingshausen, W. Nernst. Ueber das Auftreten electromotorischer Kräfte in Metallplatten, welche von einem Wärmestrome durchflossen werden und sich im magnetischen Felde befinden (1886)
- [2]H. B. Callen. The application of Onsager's reciprocal relations to thermoelectric, thermomagnetic, and galvanomagnetic effects (1948)
- [3]H. J. Goldsmid. Introduction to Thermoelectricity (2nd ed.) (2016)
- [4]A. Bejan. Advanced Engineering Thermodynamics (4th ed.) (2016)
- [5]S. Iwakiri, Y. Miyata, T. Mori. Observation of universal thermopolarization effect in insulators (2026)
- [6]J. F. Nye. Physical Properties of Crystals: Their Representation by Tensors and Matrices (1985)
- [7]J. Tušek et al.. A regenerative elastocaloric heat pump (2016)
- [8]X. Moya, S. Kar-Narayan, N. D. Mathur. Caloric materials near ferroic phase transitions (2014)
Cite this route
Physical Transformation Atlas (2026). route p-26d61bdff0: Electric potential difference → Ettingshausen effect → Temperature gradient → Thermal expansion → Mechanical stress or strain → Elastocaloric effect → Useful heat. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/path/26d61bdff0
Ids and matrix addresses are stable across revisions; the revision hash identifies the exact canonical files the record was compiled from and is meta.data_hash in every /api export. Reuse terms: see the license field in any export.