Thermodynamic energy conversion efficiencies
Atlas use: this paper is cited as evidence by 11 claims and 1 named pathway. Bibliographic record verified against Crossref on 2026-09-19.
Exploreatlas context · claims citing it · pathways citing it · cite
Atlas context
Derived from the citing claims only: the families, matrix cells and routes those claims take part in.
D = disequilibrium row · C = coupling family column. A cell reads the state of the atlas for that pair.
- Incandescent lampcomposition evidence recorded
- Solar thermal collector (hot water)composition evidence recorded
- Thermophotovoltaic conversioncomposition evidence recorded
- Concentrating solar-thermal plantcomposition evidence recorded
- Combustion-driven micro-thermophotovoltaic generatorcomposition evidence recorded
- Incident radiation flux → Photothermal absorption → Temperature gradient → Thermal emission → Light4/4 established
- Chemical potential difference → Combustion → Temperature gradient → Thermal emission → Light4/4 established
- Electric potential difference → Peltier effect → Temperature gradient → Thermal emission → Light4/4 established
- Electric potential difference → Ettingshausen effect → Temperature gradient → Thermal emission → Light4/4 established
- Radiative imbalance with the sky → Radiative sky cooling → Temperature gradient → Thermal emission → Light4/4 established
- Nuclear binding-energy difference → Nuclear fission → Temperature gradient → Thermal emission → Light4/4 established
- Nuclear binding-energy difference → Nuclear fusion → Temperature gradient → Thermal emission → Light2/4 established
first 12 of 88 routes shown
Claims citing this source · 11
Named pathways citing this source · 1
- Incandescent lampcommercial
Cite this source
Physical Transformation Atlas (2026). source source:landsberg-tonge-1980: Thermodynamic energy conversion efficiencies. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/source/landsberg-tonge-1980
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.