| albedo | Snow montreal-suburban Awaiting sign-off snow_albedo_min 0.18 · snow_albedo_max 0.85 |
|---|---|
| emissivity | Snow emissivity Awaiting sign-off narp_emissivity_snow 0.99 |
Fills the albedo slot. The record declares target snow, name Snow, place montreal-suburban, representativeness site, source jarvi2014 and method fitted, and carries snow_albedo_min and snow_albedo_max. Its stable path and origin retain legacy Helsinki migration text.
Fills the emissivity slot. The record declares target snow, name Snow emissivity, no place, representativeness generic, source jarvi2011 and method literature, and carries narp_emissivity_snow. Its stable path and origin retain legacy Helsinki migration text.
All four legacy OHM condition fields point to legacy ID 50240016. The stable record declares target ohm_coefficients, place montreal-suburban, representativeness site and source jarvi2014, and carries a1 0.25, a2 0.6 and a3 -30. Its path and origin retain legacy Helsinki migration text.
| Composite identity | curation required The composite's name reads No Snow and its legacy block sets every snow scalar it carries, RadMeltFactor, TempMeltFactor, tau_a, tau_f, PrecipLimAlb, SnowDensMin, SnowDensMax, tau_r, CRWMin, CRWMax and PrecipLimSnow, to -999. It nevertheless selects two components, and because it declares no parameters block of its own the assembled fragment is exactly what they supply: snow_albedo_min 0.18 and snow_albedo_max 0.85 referenced to jarvi2014, plus narp_emissivity_snow 0.99 referenced to jarvi2011. The albedo pair is described as montreal-suburban, site, while emissivity is generic and placeless. A no-snow default therefore publishes a site-derived albedo and a general emissivity and nothing else. Whether SUEWS still needs those fields populated when the snow module is off, which would make the selection right and the label misleading, or whether the uses block does not belong here, is not something these files settle. |
|---|---|
| Composite target | supported The composite declares target snow and both components declare target snow. Snow records carry no attaches_to field; in this database attaches_to appears only on the profile records under records/profiles/, so the slot check rests on the parameter names each component carries. The albedo slot takes the record holding snow_albedo_min and snow_albedo_max and the emissivity slot takes the record holding narp_emissivity_snow, so each slot receives a component declared for it. |
| Own parameter values | not applicable The composite declares no parameters block, so it overrides nothing. The -999 sentinels sit in its legacy block alone and do not reach the assembled fragment. |
| Composition rationale | not applicable The composite claims no composition rationale, and its source field reads unreferenced, which docs/FORMAT.md defines as marking legacy values that carried no citation. Its albedo component declares jarvi2014 and its emissivity component declares jarvi2011, so an unreferenced composite exports cited component values from both publications. |
| Place applicability | curation required The composite declares place generic, which db/places.yml holds as the bare entry Generic with no coordinates, country or Koppen class. Its albedo component declares montreal-suburban and its emissivity component declares no place, so one component matches the generic scope while the other remains site-specific. Its four legacy OHM condition fields also point to a triplet fitted at the Montreal Pr site. No snow record in the database declares a generic place, the only three being the two Helsinki records and records/snow/se-england--ward2016--albedo, so this cannot be closed by re-selection and turns on the decision recorded under name. |
| Representativeness | curation required The composite declares representativeness generic, the broadest class the format offers. Its emissivity component also declares generic, while its albedo component declares site and therefore stands in below the default's claimed scale. The OHM record referenced by all four legacy condition fields likewise declares site. No snow record classed generic exists, and the only one classed regional, records/snow/se-england--ward2016--albedo, carries albedo alone, so as with place the gap cannot be closed by re-selection. |
| Slot and season mapping | supported An assembly of two existing records into the albedo and emissivity slots, and assembled is the method a composition sidecar takes. Unlike the other two snow composites this one asserts no scalars of its own, so everything it contributes arrives through those two slots. |
| Completeness and uniqueness | supported It is the only no-snow default in the database. Its uses block is identical to those of archetypes/snow/helsinki--snow and archetypes/snow/se-england--not-used, and unlike them it asserts no parameters of its own, so under the modern schema it is not a full snow parameter set but the two component values alone, which is the point the name finding turns on. The one remaining snow record, records/snow/generic--kawai2009--thermal-layers, carries an empty parameters block with everything in legacy, so no slot is missing on its account. |
archetypes/snow/suews--no-snow is a generic, unreferenced entry whose legacy block disables snow by setting eleven scalars to -999, and it selects the same two components as the other two snow composites. Because it declares no parameters block of its own, what it assembles is those components and nothing more: the fragment exports snow_albedo_min 0.18, snow_albedo_max 0.85 and narp_emissivity_snow 0.99; the albedo is referenced to jarvi2014 and described as montreal-suburban, site, while the emissivity is referenced to jarvi2011 and described as generic, and the -999 sentinels never leave the legacy block. An entry named No Snow, placed generic and classed generic, therefore resolves under the modern schema to specific-place snow optical properties alone. Its four legacy OHM condition fields additionally point to the Montreal-site triplet under legacy ID 50240016, but that binding does not enter the modern fragment. Two things follow, neither of them settled by the files. The database holds no snow record with a generic place or a generic class, so the place and class gaps cannot be closed by choosing different components. And whether a configuration running with the snow module off still needs snow_albedo_min, snow_albedo_max and narp_emissivity_snow present is a question about SUEWS rather than about this database: if it does, the components are a reasonable stand-in and it is the label that misleads; if it does not, the uses block should not be here at all. A maintainer with the model's requirements to hand can settle all three findings in one decision.
RadMeltFactor | -999 |
TempMeltFactor | -999 |
tau_a | -999 |
tau_f | -999 |
PrecipLimAlb | -999 |
SnowDensMin | -999 |
SnowDensMax | -999 |
tau_r | -999 |
CRWMin | -999 |
CRWMax | -999 |
PrecipLimSnow | -999 |
OHMSummerWet | 50240016 |
OHMSummerDry | 50240016 |
OHMWinterWet | 50240016 |
OHMWinterDry | 50240016 |
OHMThresh_SW | 10 |
OHMThresh_WD | 0.9 |
Paste under snow in a SUEWS YAML configuration; every value carries its citation.
snow_albedo_min:
value: 0.18
ref:
ID: jarvi2014
DOI: 10.5194/gmd-7-1691-2014
desc: montreal-suburban, site, neighborhood
snow_albedo_max:
value: 0.85
ref:
ID: jarvi2014
DOI: 10.5194/gmd-7-1691-2014
desc: montreal-suburban, site, neighborhood
narp_emissivity_snow:
value: 0.99
ref:
ID: jarvi2011
DOI: 10.1016/j.jhydrol.2011.10.001
desc: generic
snow · docs