Permeate gap thermo-osmotic system for simultaneous freshwater production, energy storage, and power generation
Atlas use: this paper is cited as evidence by 2 claims and 0 named pathways. Not yet checked against Crossref.
Full text read (an author-shared copy located through Google Scholar). A 32 cm² permeate-gap module (PTFE, hot feed to 70 °C, cold side 20 °C) pressurises its own permeate without a pump; in layout 1 the permeate rises through a vertical pipe to an elevated tank and the stream released from the tank propelled a small hydro-turbine generator that lit a 2 W-rated bulb — the authors' 'thermal-potential-mechanical energy conversion'. The laboratory head was limited to about 1.5 m; sealed-permeate pressurisation reached a liquid entry pressure of 222 kPa (PTFE with non-woven support); water flux fell 54.25 % from 0 to 200 kPa permeate pressure. No shaft or electrical output figure is reported for the bulb demonstration; the 72-hour fluctuating-source run used a virtual hydro-turbine (0.0065 L h⁻¹), and the 156.75 kW, 0.113 W m⁻² and 1.04 % exergy figures belong to the modelled 150 kW solar case study. For the atlas this is a longer-chain demonstration of the TOEC route: gravitational storage (head conversion) sits between the thermo-osmotic flow and the turbine.
Exploreatlas context · claims citing it · cite
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.
Claims citing this source · 2
Cite this source
Physical Transformation Atlas (2026). source source:xiao-2024-permeate-gap-thermo-osmotic: Permeate gap thermo-osmotic system for simultaneous freshwater production, energy storage, and power generation. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/source/xiao-2024-permeate-gap-thermo-osmotic
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.