Skip to content

Slot: Equation Inputs (equation_inputs)

Typed per-input references for a multi-input derived metric (Heat Index from T + RH; WBGT from T + RH + wind + radiation). Each entry names the input's role and points, by provenance_id, to the upstream sidecar carrying that input's full context — it is an index into the lineage, not an inline copy of it.

Option-B decomposition (see the EquationInput class): when the inputs originate from different products and diverge in resolution, day-boundary convention, or temporal aggregation, each input is a full upstream sidecar referenced here and listed as a step in provenance_chain, so the divergence stays explicit and checkable.

Conditionally-Core: optional for a single-input metric, mandatory the moment a metric has more than one input.

Tier: conditionally_core

Why this slot matters

Multi-input metrics can silently absorb mismatched inputs — e.g. a Heat Index built from a 1 km local-midnight daily-max temperature and a ~31 km UTC daily-mean humidity. Without per-input references that divergence is invisible and no checker can surface it.

In plain terms

Composite heat metrics are cooked from several ingredients — temperature, humidity, wind, sunshine. This is the ingredient list, where each entry points to that ingredient's own full paperwork instead of hiding it inside the final number.

URI: envar:slot/equation_inputs

Applicable Classes

Name Description Modifies Slot
DerivedHeatMetric Methodology slots specific to derived heat metrics (WBGT, Heat Index, UTCI, a... yes

Properties

Type and Range

Property Value
Range EquationInput
Domain Of DerivedHeatMetric

Cardinality and Requirements

Property Value
Multivalued Yes

Examples

Value
None
None

Comments

  • Cross-input consistency check (completeness checker, not structural LinkML validation): when more than one entry is present, dereference each input_provenance_id and WARN if the referenced inputs' day-boundary conventions, temporal aggregation windows, or native spatial resolutions differ. A divergence is allowed but must be recorded via the decomposed sidecars rather than absorbed silently into the output value.

Identifier and Mapping Information

Annotations

property value
tier conditionally_core
justification Multi-input metrics can silently absorb mismatched inputs — e.g. a Heat Index built from a 1 km local-midnight daily-max temperature and a ~31 km UTC daily-mean humidity. Without per-input references that divergence is invisible and no checker can surface it.
explanation Composite heat metrics are cooked from several ingredients — temperature, humidity, wind, sunshine. This is the ingredient list, where each entry points to that ingredient's own full paperwork instead of hiding it inside the final number.

Schema Source

Mappings

Mapping Type Mapped Value
self envar:equation_inputs
native envar:equation_inputs

LinkML Source

name: equation_inputs
annotations:
  tier:
    tag: tier
    value: conditionally_core
  justification:
    tag: justification
    value: Multi-input metrics can silently absorb mismatched inputs — e.g. a Heat
      Index built from a 1 km local-midnight daily-max temperature and a ~31 km UTC
      daily-mean humidity. Without per-input references that divergence is invisible
      and no checker can surface it.
  explanation:
    tag: explanation
    value: Composite heat metrics are cooked from several ingredients — temperature,
      humidity, wind, sunshine. This is the ingredient list, where each entry points
      to that ingredient's own full paperwork instead of hiding it inside the final
      number.
description: 'Typed per-input references for a multi-input derived metric (Heat Index
  from T + RH; WBGT from T + RH + wind + radiation). Each entry names the input''s
  role and points, by `provenance_id`, to the upstream sidecar carrying that input''s
  full context — it is an index into the lineage, not an inline copy of it.

  Option-B decomposition (see the `EquationInput` class): when the inputs originate
  from different products and diverge in resolution, day-boundary convention, or temporal
  aggregation, each input is a full upstream sidecar referenced here and listed as
  a step in `provenance_chain`, so the divergence stays explicit and checkable.

  Conditionally-Core: optional for a single-input metric, mandatory the moment a metric
  has more than one input.'
title: Equation Inputs
comments:
- 'Cross-input consistency check (completeness checker, not structural LinkML validation):
  when more than one entry is present, dereference each `input_provenance_id` and
  WARN if the referenced inputs'' day-boundary conventions, temporal aggregation windows,
  or native spatial resolutions differ. A divergence is allowed but must be recorded
  via the decomposed sidecars rather than absorbed silently into the output value.'
examples:
- description: one entry of the list — the air-temperature input of a Liljegren WBGT;
    a wind-speed entry from a divergent product (e.g. ~31 km ERA5) would sit alongside
    it as a second element
  object:
    input_role: air_temperature
    input_provenance_id: 01HFA7K8R3M6XP-daymet-tmax
    input_source_short_code: daymet_v4
- description: a second list entry from a divergent product (~31 km ERA5 vs 1 km Daymet),
    pointing at its own full upstream sidecar
  object:
    input_role: wind_speed
    input_provenance_id: 01HFA7K8R3M6XP-era5-wind
    input_source_short_code: era5
from_schema: https://w3id.org/linkml/microschemas/envar
rank: 1000
domain_of:
- DerivedHeatMetric
range: EquationInput
multivalued: true
inlined: true
inlined_as_list: true