Physical Transformation AtlasPTA
Constraint · constraint:pec-water-splitting-dual-junction-ideal-limit

PEC water-splitting ideal limit, dual junction

The same ideal assumptions as the single-junction limit, for two absorbers in series: the global maximum over all gap pairs. A particular gap pair has a lower ceiling of its own (Cheng 2018's 1.78 / 1.26 eV tandem: 22.8 %), which lives on that architecture's pathway, never here.

Atlas record: 1 claim references this constraint — 1 established.

Explorerelations · sources · cite

η_STH ≤ 40.0 % for a dual-junction photoelectrochemical water-splitting device under AM1.5G in the ideal case (E_g 0.52 / 1.40 eV at the maximum); a third junction adds nothing (the ideal triple-junction maximum is 28.3 %)

1claims0enumerated routes0routes with complete-composition evidence0candidate routes not searched2cited sources

Relations

bounded by · 1
Photoelectrochemical effect—bounded by→PEC water-splitting ideal limit, dual junctionestablished
  • photoelectrochemical water splitting with two absorbers in series; a datum states the basis 'PEC water splitting, dual-junction absorber, AM1.5G'

Cited sources · 2

  1. [1]
    Katherine T. Fountaine, Hans Joachim Lewerenz, Harry A. Atwater. Efficiency limits for photoelectrochemical water-splitting (2016)
    Nature Communications 7, 13706 (open access) · doi:10.1038/ncomms13706 · record
  2. [2]
    Elena Rozzi et al.. Green Synthetic Fuels: Renewable Routes for the Conversion of Non-Fossil Feedstocks into Gaseous Fuels and Their End Uses (2020)
    Energies 13(2), 420 (open access review) · doi:10.3390/en13020420 · record

Cite this entity

Physical Transformation Atlas (2026). entity constraint:pec-water-splitting-dual-junction-ideal-limit: PEC water-splitting ideal limit, dual junction. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/e/constraint/pec-water-splitting-dual-junction-ideal-limit

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.