Bulk fluid flow —drives→ Magnetohydrodynamic generation
The atlas records this claim as established: a bulk fluid flow drives magnetohydrodynamic generation under the conditions below.
Exploreconditions · evidence · matrix context · uses · cite
Conditions
- an electrically conducting fluid — seeded combustion plasma or liquid metal — crossing a strong magnetic field between electrodes
Evidence · 3
- [1]R. J. Rosa. Physical principles of magnetohydrodynamic power generation (1961)
- [2]L. D. Landau, E. M. Lifshitz, L. P. Pitaevskii. Electrodynamics of Continuous Media (Course of Theoretical Physics, Vol. 8, 2nd ed.) (1984)
- [3]NASA Lewis Research Center, Electromagnetic Propulsion Division. Lewis Tech Preview: Research Nonequilibrium MHD Power Generator Facility
Matrix cells this relation feeds
D = disequilibrium row · C = coupling family column. A cell reads the state of the atlas for that pair.
Uses of this claim
- Combustion MHD generatorprototype · 7 steps
- Bulk fluid flow → Magnetohydrodynamic generation → Charge carriers → Electrical work3/3 established · extends a recorded pathway
- Gravitational potential difference → Gravitational descent of fluid → Bulk fluid flow → Magnetohydrodynamic generation → Charge carriers → Electrical work5/5 established · candidate
- Gravitational potential difference → Tidal flow → Bulk fluid flow → Magnetohydrodynamic generation → Charge carriers → Electrical work5/5 established · candidate
- Nuclear binding-energy difference → Nuclear fission → Hot gas → Gas-dynamic expansion → Bulk fluid flow → Magnetohydrodynamic generation → Charge carriers → Electrical work7/7 established · extends a recorded pathway
Cite this claim
Physical Transformation Atlas (2026). claim claim:flow-drives-mhd: Bulk fluid flow —drives→ Magnetohydrodynamic generation. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/claim/flow-drives-mhd
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.