Physical Transformation AtlasPTA
Claim · claim:dufour-onsager

Dufour effect —governed by→ Onsager–Casimir reciprocity

The atlas records this claim as established: the Dufour effect is governed by the onsager–Casimir reciprocity under the conditions below.

establishedrecord reviewed 2026-09-20

Exploreconditions · evidence · matrix context · cite

4cited sources0enumerated routes using it0routes with composition evidence0recorded pathways

Conditions

  • near equilibrium the properly defined heat–mass Onsager cross-coefficients are reciprocal when fluxes and conjugate forces use the same convention; this does not imply numerical equality of the convention-dependent Soret and Dufour coefficients

Evidence · 4

  1. [1]
    L. Onsager. Reciprocal relations in irreversible processes. I. (1931)
    Physical Review 37, 405 · doi:10.1103/PhysRev.37.405 · crossref ✓ 2026-09-19 · record
  2. [2]
    R. L. Rowley, F. H. Horne. The Dufour effect. II. Experimental confirmation of the Onsager heat–mass reciprocal relation for a binary liquid mixture (1978)
    The Journal of Chemical Physics 68, 325-326 · doi:10.1063/1.435458 · crossref ✓ 2026-09-20 · record
  3. [3]
    S. R. de Groot, P. Mazur. Non-Equilibrium Thermodynamics (1962)
    North-Holland · book, no DOI · record
  4. [4]
    A. Würger. Do thermal diffusion and Dufour coefficients satisfy Onsager's reciprocity relation? (2014)
    The European Physical Journal E 37, 96 · doi:10.1140/epje/i2014-14096-y · crossref ✓ 2026-09-20 · record

Related matrix context

This claim does not itself create a matrix cell. The context below belongs to Dufour effect, the phenomenon it is about.

D = disequilibrium row · C = coupling family column. A cell reads the state of the atlas for that pair.

Cite this claim

Physical Transformation Atlas (2026). claim claim:dufour-onsager: Dufour effect —governed by→ Onsager–Casimir reciprocity. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/claim/dufour-onsager

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.