Mechanical vibration → Mechanical work
Mechanical vibrationResonant vibrationMechanical motionMechanical work
Epistemic state of the route
- known constituent relations
- 3 / 3 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 relations, in order, with Electromagnetic vibration harvester · 2/3 relations shared
- route-level evidence
- 0 sources for the complete composition · 4 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.
No coupling family recorded for this route's phenomena.
Steps
- 01mechanical → mechanical · loss to thermal
- a cantilever or seismic mass with natural frequency near the excitation
solidrefs [1] [2] - 02mechanical → mechanicalrefs [3] [2]
- 03mechanical → mechanical · loss to thermalrefs [4]
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 · 4
- [1]S. Roundy, P. K. Wright, J. Rabaey. A study of low level vibrations as a power source for wireless sensor nodes (2003)
- [2]A. Erturk, D. J. Inman. Piezoelectric Energy Harvesting (2011)
- [3]S. P. Beeby, et al.. A micro electromagnetic generator for vibration energy harvesting (2007)
- [4]A. Bejan. Advanced Engineering Thermodynamics (4th ed.) (2016)
Cite this route
Physical Transformation Atlas (2026). route p-b97d20e3f5: Mechanical vibration → Resonant vibration → Mechanical motion → Mechanical work. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/path/b97d20e3f5
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.