Bulk fluid flow —drives→ Electrohydrodynamic generation

Conditions

• a dielectric fluid carrying injected charge is driven by the flow against an electric field to a collector electrode

Evidence · 2

1. [1]
   S. Fujimoto, T. Terado. Fundamental characteristics of liquid-filled electrohydrodynamic generator (1977)

   Journal of Electrostatics 2, 257-267 · doi:10.1016/0304-3886(77)90058-4 · crossref ✓ 2026-09-20 · record
2. [2]
   L. Hao et al.. Interfacial electro-hydrodynamics inspired micro/nano-fluidic energy conversion: from mechanism to applications (2025)

   Lab on a Chip 25, 4161-4220 · doi:10.1039/D5LC00321K · crossref ✓ 2026-09-20 · record

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

• Bulk fluid flow → Electrohydrodynamic generation → Fluid-borne space charge → Electrical work3/3 established · candidate
• Gravitational potential difference → Gravitational descent of fluid → Bulk fluid flow → Electrohydrodynamic generation → Fluid-borne space charge → Electrical work5/5 established · candidate
• Gravitational potential difference → Tidal flow → Bulk fluid flow → Electrohydrodynamic generation → Fluid-borne space charge → Electrical work5/5 established · candidate
• Chemical potential difference → Combustion → Hot gas → Gas-dynamic expansion → Bulk fluid flow → Electrohydrodynamic generation → Fluid-borne space charge → Electrical work7/7 established · extends a recorded pathway
• Nuclear binding-energy difference → Nuclear fission → Hot gas → Gas-dynamic expansion → Bulk fluid flow → Electrohydrodynamic generation → Fluid-borne space charge → Electrical work7/7 established · extends a recorded pathway

Cite this claim

Physical Transformation Atlas (2026). claim claim:flow-drives-ehd: Bulk fluid flow —drives→ Electrohydrodynamic generation. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/claim/flow-drives-ehd

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.