Observation of the spin Nernst effect

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.

• Temperature gradient → Spin Nernst effect → Spin current → Inverse spin Hall effect → Charge carriers → Electrical work5/5 established
• Chemical potential difference → Combustion → Temperature gradient → Spin Nernst effect → Spin current → Inverse spin Hall effect → Charge carriers → Electrical work7/7 established
• Electric potential difference → Peltier effect → Temperature gradient → Spin Nernst effect → Spin current → Inverse spin Hall effect → Charge carriers → Electrical work7/7 established
• Electric potential difference → Ettingshausen effect → Temperature gradient → Spin Nernst effect → Spin current → Inverse spin Hall effect → Charge carriers → Electrical work7/7 established
• Incident radiation flux → Photothermal absorption → Temperature gradient → Spin Nernst effect → Spin current → Inverse spin Hall effect → Charge carriers → Electrical work7/7 established
• Radiative imbalance with the sky → Radiative sky cooling → Temperature gradient → Spin Nernst effect → Spin current → Inverse spin Hall effect → Charge carriers → Electrical work7/7 established
• Nuclear binding-energy difference → Nuclear fission → Temperature gradient → Spin Nernst effect → Spin current → Inverse spin Hall effect → Charge carriers → Electrical work7/7 established
• Nuclear binding-energy difference → Nuclear fusion → Temperature gradient → Spin Nernst effect → Spin current → Inverse spin Hall effect → Charge carriers → Electrical work5/7 established

Claims citing this source · 2

Cite this source

Physical Transformation Atlas (2026). source source:meyer-2017-spin-nernst: Observation of the spin Nernst effect. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/source/meyer-2017-spin-nernst

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.