Names follow the SUEWS YAML specification; click one for its definition in the configuration reference.
a1 | 0.238 |
a2 | 0.427 |
a3 | -16.7 |
Where: Section 4.3, Storage heat flux, p. 4556
The article says all surface coefficients follow the previous Beijing SUEWS study; it does not publish or derive the code-799 tuple.
Where: ModelRuns/Input/SUEWS_OHMCoefficients.txt, code 799
Where: ModelRuns/Input/SUEWS_NonVeg.txt, code 160 maps all OHM seasons to code 799
Where: ModelRuns/Input/SUEWS_SiteSelect.txt, Beijing building surface uses code 160
The final model archive contains 0.238, 0.427, -16.7 as code 799 and traces it to the building surface used in the Beijing runs.
Preserves the same code-799 tuple as a generic legacy identity. The pinned v2017a input table directly supports that tuple, while its historical averaging calculation remains undocumented.
| Name | supported Original roof average is the archived label of code 799 selected by the Beijing building configuration; it identifies reused configuration lineage rather than an independent Beijing fit. issue #66 |
|---|---|
| Target | supported |
| Values | supported |
| Source | supported Unreferenced is correct for the exact tuple because Zheng et al. apply and archive code 799 but do not derive it; source_legacy_ref 90240067 preserves the migration link to the application paper without presenting it as the parameter publication. issue #66 |
| Place | supported Beijing is the model-application location of this retained code-799 selection, not a claim that the coefficients were independently determined in Beijing. issue #66 |
| Representativeness | supported City describes the reach of the archived Beijing model application; it does not describe empirical evidence reach for the generic code-799 configuration or its undocumented derivation. issue #66 |
| Applicable Scale | unresolved Zheng et al. establish later Beijing use of code 799 but not whether the tuple originally describes a roof facet or a building land-cover class. The original code-799 publication/table or an author statement defining its fitted unit is required. issue #46 |
| Method | supported Assumed records the Beijing configuration choice to reuse code 799. It deliberately does not claim to reconstruct the undocumented calculation that originally produced the generic tuple. issue #66 |
| Identity | supported The archive selects code 799 for the Beijing building surface, while the generic record preserves the underlying reusable code identity. Keeping both stable paths distinguishes application lineage from the generic configuration provenance without claiming two parameter determinations. issue #66 |
The Zheng archive proves that code 799 was selected for the Beijing building surface but does not make Zheng et al. the parameter source. This record is therefore retained as an explicit Beijing application identity with source unreferenced and method assumed; source_legacy_ref 90240067 preserves the application-paper link. The related generic record now cites the pinned v2017a table that directly stores the tuple and marks its undocumented averaging method as assumed. No value, stable path, origin or legacy ID is changed.
Paste under ohm_coefficients in a SUEWS YAML configuration; every value carries its citation.
a1:
value: 0.238
ref:
ID: unreferenced
DOI: null
desc: beijing, city
a2:
value: 0.427
ref:
ID: unreferenced
DOI: null
desc: beijing, city
a3:
value: -16.7
ref:
ID: unreferenced
DOI: null
desc: beijing, city
ohm_coefficients · docs