Names follow the SUEWS YAML specification; click one for its definition in the configuration reference.
rho_cp_anohm | 1000000 |
k_anohm | 1.2 |
ch_anohm | 4 |
Where: SUEWS_Veg.txt, code 661 EvergreenTreeA London row
First repository table located with the exact 1000000/1.2/4 tuple; it labels the complete configuration row EveTr and London but supplies no parameter citation.
Where: SUEWS_Veg.txt, sibling code 700 EvergreenTreeB London row
Reuses the same AnOHM tuple but selects OHM code family 201 rather than the row 661 family 200, establishing a separate full-row configuration identity rather than separate parameter evidence.
Where: InputFiles_SUEWS_v2017a_SiteInfo.xlsm, SUEWS_Veg sheet, code 661 row
The generator workbook committed with the text table stores 100000/1.2/4 for code 661, so it does not document how the released text value 1000000 was produced.
Where: Table 1(a), input-parameter sensitivity distributions, p. 2880
Publishes generic means of 2.0 MJ m-3 K-1, 1.2 W m-1 K-1 and 4, not the exact stored tuple.
Where: Table 3, UK-Ldn calibration, p. 2883
Publishes the bulk London calibration 2.4 MJ m-3 K-1, 2.8 W m-1 K-1 and 4.3, not a separate evergreen-tree tuple of 1.0 MJ m-3 K-1, 1.2 W m-1 K-1 and 4.
| Name | supported EvergreenTreeA preserves the migrated name of the first SUEWS evergreen-tree configuration. |
|---|---|
| Target | supported The three AnOHM fields are stored on the EvergreenTreeA surface row and therefore belong to land_cover.evetr. |
| Values | supported The v2017a text table stores 1000000, 1.2 and 4 exactly. The earlier AnOHM table and the generator workbook committed with v2017a both store 100000 instead, while Sun et al. publish different generic and London values. The current tuple is therefore supported only as the released text-table assumption, not as a scientific determination. issue #206 |
| Source | supported Unreferenced is correct. Author adjudication in issue 492 confirms that the tuple was deliberately assumed and that Järvi et al. have no AnOHM parameter-provenance role. The release table documents compilation lineage while Sun et al. validate AnOHM without publishing this exact tuple. issue #206 |
| Place | supported Generic is the active evidence place because no publication determines this tuple at a study location. Author adjudication in issue 492 confirms that London is only the application label retained in the stable path and origin. issue #206 |
| Representativeness | supported Generic scope records the deliberately assumed land-cover default; city would falsely present the tuple as a London observational or fitted result. |
| Applicable Scale | supported Author adjudication in issue 492 confirms that the tuple applies to the evergreen-tree land-cover class rather than a whole-neighbourhood bulk calibration. |
| Method | supported Author adjudication in issue 492 confirms that the tuple was deliberately assumed, not derived or calibrated; the companion workbook disagreement also rules out treating the text row as a transparent calculation. |
| Identity | supported Author adjudication in issue 492 confirms that rows 661 and 700 are intentionally separate complete configurations with different OHM code families while reusing the same AnOHM subset. The stable path and legacy ID preserve row 661 without claiming a second scientific determination. |
The exact 1000000/1.2/4 tuple first appears in the SUEWS v2017a text table as a London EveTr configuration, but its companion generator workbook retains 100000/1.2/4. Author adjudication in issue 492 confirms that the tuple is a deliberately assumed generic land-cover default, London is only its application label, and the two EveTr rows are meaningful complete configurations. The v2017a table is compilation evidence, Sun et al. provide validation, and Järvi et al. have no AnOHM parameter-provenance role.
Paste under land_cover.evetr in a SUEWS YAML configuration; every value carries its citation.
rho_cp_anohm:
value: 1000000
ref:
ID: unreferenced
DOI: null
desc: generic, generic, land_cover
k_anohm:
value: 1.2
ref:
ID: unreferenced
DOI: null
desc: generic, generic, land_cover
ch_anohm:
value: 4
ref:
ID: unreferenced
DOI: null
desc: generic, generic, land_cover
Raises a prefilled sign-off issue. CI accepts it only when the issue author is in the verifier registry and the evidence revision is still current.
Review procedureland_cover.evetr · docs