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.
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.yamlper 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.yamlextraction in PR-A4 (#1489) and leave the STAC schema/extension part for a later PR once #1484 unblocks.