From 0d64d5cba473d7ec5e90a7f4628d35f0ff2682ce Mon Sep 17 00:00:00 2001 From: Zebedee Nicholls Date: Wed, 13 May 2026 20:33:56 +1000 Subject: [PATCH] Add note on naming conventions --- .../understanding-the-naming-conventions.py | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/tutorials/understanding-the-naming-conventions.py b/docs/tutorials/understanding-the-naming-conventions.py index 724ed093..c120c24b 100644 --- a/docs/tutorials/understanding-the-naming-conventions.py +++ b/docs/tutorials/understanding-the-naming-conventions.py @@ -222,6 +222,20 @@ # although it serves the same purpose and has the same shape/behaviour). # This database stores the mapping between the naming conventions # used in different communites. +# +# At present, this covers the full set of emissions +# which are used by simple climate models. +# Whether these are supported by individual workflows +# (e.g. the AR6 workflow, see +# [here](../how-to-guides/how-to-run-the-ar6-workflowy)) +# or the global-only part of the CMIP7 ScenarioMIP workflow, see +# [here](../how-to-guides/how-to-run-the-cmip7-scenariomip-workflow)) +# is more complicated and nuanced. +# The pre-processors and harmonisers for these workflows +# will help guide what is actually supported via their internal validation. +# Once the infilling and simple climate model running stages are reached, +# then the full set of variables shown here +# is always supported (strictly speaking, required). # %% # The database in full