Optional. Component families capture scientific lineage by grouping versions of a single-domain code base (e.g. NEMO, ARPEGE-Climat, SURFEX). A family ID can be referenced by model components at Stage 3.


Generated files

This page is auto-generated during the build from live registry data. Three files are produced for each record type:

  • Component_Families.md — this page, embedded in the MkDocs site layout
  • Component_Families_data.json — processed similarity matrices, dendrogram tree, and key schema
  • Component_Families_raw.json — raw JSON-LD records as fetched from the cmipld registry (depth 2)

14 registered entries Endpoint: model_family