Skip to content

Unify source of variables required by both ESMValTool and CDDS #226

@chrisbillowsMO

Description

@chrisbillowsMO

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

In #18 we have hardcoded a series of values within the update_recipe function in update_recipe_file.py.

There is duplication between some of these values and the values used to created the CDDS request.json file in configure_standardise.

ESMVT Key CDDS Key Current Hardcoded value
"exp" "experiment_id" "amip"
"ensemble" "variant_label" r1i1p1f1
"project" "mip" "ESMVal"

Experiment and Ensemble to possibly eventually become user configurable, therefore may need to go into rose-suite.conf. This may also be worth considering as part of #191

Describe the solution you'd like
A clear and concise description of what you want to happen.

Find a good home for these poor, lonely vars and make them re-usability powerhouses!

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    configureAnything related to configurationenhancementNew feature or requestenvironmentAnything related to environmentsneeds refinementThis issue needs to be refinedrecipeAnything related to ESMValToolstandardiseAnything related to CDDS

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions