Pyroelectricity: from ancient curiosity to modern imaging tool

Atlas context

Derived from the citing claims only: the families, matrix cells and routes those claims take part in.

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

• Pyroelectric harvestercomposition evidence recorded
• Changing magnetic flux → Magnetocaloric effect → Temporal temperature change → Pyroelectric effect → Separated surface charge → Electrical work5/5 established
• Mechanical stress or strain → Elastocaloric effect → Temporal temperature change → Pyroelectric effect → Separated surface charge → Electrical work5/5 established
• Changing electric field → Electrocaloric effect → Temporal temperature change → Pyroelectric effect → Separated surface charge → Electrical work5/5 established
• Temperature gradient → Thermal expansion → Mechanical stress or strain → Elastocaloric effect → Temporal temperature change → Pyroelectric effect → Separated surface charge → Electrical work7/7 established
• Pressure gradient → Elastic deformation → Mechanical stress or strain → Elastocaloric effect → Temporal temperature change → Pyroelectric effect → Separated surface charge → Electrical work7/7 established
• Mechanical vibration → Resonant vibration → Mechanical stress or strain → Elastocaloric effect → Temporal temperature change → Pyroelectric effect → Separated surface charge → Electrical work7/7 established
• Mechanical vibration → Elastic deformation → Mechanical stress or strain → Elastocaloric effect → Temporal temperature change → Pyroelectric effect → Separated surface charge → Electrical work7/7 established

Claims citing this source · 3

Cite this source

Physical Transformation Atlas (2026). source source:lang-2005: Pyroelectricity: from ancient curiosity to modern imaging tool. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/source/lang-2005

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.