Physical Transformation AtlasPTA
Claim · claim:ferrofluid-convection-couples-induction

Thermomagnetic convection —couples to→ Electromagnetic induction

The atlas records this claim as demonstrated: the thermomagnetic convection couples directly into electromagnetic induction under the conditions below.

demonstratedK6 · working transducerledger kinetic → electrical · loss to thermalrecord reviewed 2026-09-20

Exploreconditions · evidence · matrix context · uses · cite

1cited sources8enumerated routes using it1routes with composition evidence1recorded pathways

Conditions

  • magnetised ferrofluid advects through a closed loop wound with induction coils, so the flux linked by each coil changes as magnetised packets pass
  • a permanent-magnet bias field keeps the fluid magnetised where it moves past the coils
regime: liquid · magnetic field required · temperature gradient required

Evidence · 1

  1. [1]
    A. Chiolerio et al.. Waste heat to power conversion by means of thermomagnetic hydrodynamic energy harvester (2020)
    Applied Energy 277, 115591 · doi:10.1016/j.apenergy.2020.115591 · record

Related matrix context

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

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

Uses of this claim

recorded pathways · 1
other enumerated routes · 7

Notes

One lab-scale prototype (Chiolerio et al. 2020): a toroidal loop with poloidal or mixed poloidal/toroidal windings, water carrier with ferrofluid packets, up to 10.4 μW per kelvin. One paper is demonstrated, not established.

Cite this claim

Physical Transformation Atlas (2026). claim claim:ferrofluid-convection-couples-induction: Thermomagnetic convection —couples to→ Electromagnetic induction. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/claim/ferrofluid-convection-couples-induction

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.