Physical Transformation AtlasPTA
Pathway · p-2f1e3f4c2f · extends a recorded pathway

Bulk fluid flow → Electrical work

Bulk fluid flowFlow-induced vibrationMechanical vibrationResonant vibrationMechanical motionElectromagnetic inductionCharge carriersElectrical work

Epistemic state of the route

known constituent relations
7 / 7 established or replicated · weakest constituent established
constituent maturity floor
K4 · experimentally observed
search for this exact route
Not assessed — complete composition not searched.
recorded-pathway overlap
shares its closing relations with Electromagnetic vibration harvester · 5/7 relations shared
route-level evidence
0 sources for the complete composition · 7 cited by the constituent steps
boundaries and interfaces
BOUNDARY compatible · no region transition

Explorematrix context · physics checks · steps · route evidence · constituent evidence · cite

Matrix context

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

D.10 × C.14 · Bulk fluid flow × Electromagnetic inductionfamily: Electromagnetic induction

Steps

  1. 01
    kinetic → mechanical · loss to thermal
    • a bluff or flexible body in the stream at a Reynolds number where vortex shedding locks to a structural mode
    bulk flow required
    refs [1]
  2. 02
    mechanical → mechanical
    refs [1]
  3. 03
    mechanical → mechanical · loss to thermal
    • a cantilever or seismic mass with natural frequency near the excitation
    solid
    refs [2] [3]
  4. 04
    mechanical → mechanical
    refs [4] [3]
  5. 05
    mechanical → electrical · loss to thermal
    • a magnet moving relative to a coil
    conductor required · magnetic field required
    refs [5] [4]
  6. 06
    electrical → electrical · loss to thermal
    refs [5] [6]
  7. 07
    Charge carriers —converts into→ Electrical workestablishedclaim record
    electrical → electrical · loss to thermal
    • carriers driven through an external load at the potential difference the source maintains
    refs [7]

Evidence for the complete composition · 0

No source on record for this exact composition. The sources below support the individual steps, not the route as a whole.

Evidence for the constituent relations · 7

  1. [1]
    H. B. Radousky, H. Liang. Energy harvesting: an integrated view of materials, devices and applications (2012)
    Nanotechnology 23, 502001 · doi:10.1088/0957-4484/23/50/502001 · crossref ✓ 2026-09-19 · record
  2. [2]
    S. Roundy, P. K. Wright, J. Rabaey. A study of low level vibrations as a power source for wireless sensor nodes (2003)
    Computer Communications 26, 1131–1144 · doi:10.1016/S0140-3664(02)00248-7 · crossref ✓ 2026-09-19 · record
  3. [3]
    A. Erturk, D. J. Inman. Piezoelectric Energy Harvesting (2011)
    Wiley · doi:10.1002/9781119991151 · crossref ✓ 2026-09-19 · record
  4. [4]
    S. P. Beeby, et al.. A micro electromagnetic generator for vibration energy harvesting (2007)
    Journal of Micromechanics and Microengineering 17, 1257 · doi:10.1088/0960-1317/17/7/007 · crossref ✓ 2026-09-19 · record
  5. [5]
    M. Faraday. Experimental researches in electricity (1832)
    Philosophical Transactions of the Royal Society 122, 125–162 · doi:10.1098/rstl.1832.0006 · crossref ✓ 2026-09-19 · record
  6. [6]
    L. D. Landau, E. M. Lifshitz, L. P. Pitaevskii. Electrodynamics of Continuous Media (Course of Theoretical Physics, Vol. 8, 2nd ed.) (1984)
    Pergamon · book, no DOI · record
  7. [7]
    N. W. Ashcroft, N. D. Mermin. Solid State Physics (1976)
    Holt, Rinehart and Winston · book, no DOI · record

Cite this route

Physical Transformation Atlas (2026). route p-2f1e3f4c2f: Bulk fluid flow → Flow-induced vibration → Mechanical vibration → Resonant vibration → Mechanical motion → Electromagnetic induction → Charge carriers → Electrical work. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/path/2f1e3f4c2f

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.