Skip to content

esm_catalog: capture control-simulation reference & branch-off lineage (D1) #1502

Description

@siligam

D1 asks for control-simulation reference and branch-off lineage (parent name/path, branch-off year, restart file used — see #1407). Currently not modeled at all in esm_catalog.

Good news: most of the data already exists in finished_config.yaml per component — ini_parent_exp_id, ini_parent_date, ini_parent_dir, restart_in_sources (confirmed against a real branched-off run on Albedo). No field exists yet for a broader "control simulation" reference though — would need a new runscript convention or an esm-tools schema addition, open question.

Planning to land the finished_config.yaml extraction in PR-A4 (#1489) and leave the STAC schema/extension part for a later PR once #1484 unblocks.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions