Physical Transformation AtlasPTA
Claim · claim:thermoacoustic-produces-travelling-sound

Thermoacoustic effect —produces→ Acoustic wave

The atlas records this claim as established: the thermoacoustic effect produces an acoustic wave under the conditions below.

establishedledger acoustic → acousticrecord reviewed 2026-09-21

Exploreconditions · evidence · matrix context · uses · cite

2cited sources32enumerated routes using it0routes with composition evidence0recorded pathways

Conditions

  • travelling-wave thermoacoustic regime with a non-zero time-averaged acoustic power flux; pressure and particle velocity have the phase relation required for directed acoustic power (a looped tube or a travelling-wave regenerator), unlike the standing wave of a straight resonator
regime: gas

Evidence · 2

  1. [1]
    T. Yazaki et al.. Traveling Wave Thermoacoustic Engine in a Looped Tube (1998)
    Physical Review Letters 81, 3128–3131 · doi:10.1103/PhysRevLett.81.3128 · record
  2. [2]
    S. Backhaus, G. W. Swift. A thermoacoustic-Stirling heat engine: Detailed study (2000)
    Journal of the Acoustical Society of America 107, 3148–3166 · doi:10.1121/1.429343 · record

Related matrix context

This claim does not itself create a matrix cell. The context below belongs to Thermoacoustic effect, 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

other enumerated routes · 32 (first 24 shown)

all 32 routes are in /api/paths.json filtered by claims ∋ claim:thermoacoustic-produces-travelling-sound

Cite this claim

Physical Transformation Atlas (2026). claim claim:thermoacoustic-produces-travelling-sound: Thermoacoustic effect —produces→ Acoustic wave. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/claim/thermoacoustic-produces-travelling-sound

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.