ESMValTool

COMPUTING-BLOG
climate-models earth-system-models python

Tips

Notes to understand ESMValTool

This post have just notes about ESMValTool a little bit technical that I kept to understand it, and analyze how I could help/collaborate with the project.

Understading the code

Design principles

After navigate in the code, and try to add few things, here are few remarks about how the code was created:

  • Programed in Python (although add modules in R, NCL or Julia is possible for specific part of the workflow)
  • It follows the Object Oriented Programming style
  • The core of the code relies on Iris Cubes, a library from Met-Office.
  • The configuration files are YAML files (.yml) so easy to read and visually understand.

Programmed in Python

By inspecting the core ESMValCore here is the very schematic intial workflow of the code once you execute an example

> esmvalcode myrecipe.yml

The actual calculations begin after run-the-recipe that is recipe.run() as run is a method of recipe. The other preliminary steps are just preparing the scenario. I have indicated that read-config-file, that actually creates an object named cfg, is loading the cmor-table (that is another object part of the cfg object). This step is relevant as much of the initial steps are related with ensure that the datasets used follows the CMOR and CF conventions (something also hightligthed by Iris Cube phylosophy)

Recipe class

class Recipe:
    """Recipe object."""

    info_keys = ('project', 'dataset', 'exp', 'ensemble', 'version')
    """List of keys to be used to compose the alias, ordered by priority."""

    def __init__(self,
                 raw_recipe,
                 config_user,
                 initialize_tasks=True,
                 recipe_file=None):
        """Parse a recipe file into an object."""
        self._cfg = deepcopy(config_user)
        self._cfg['write_ncl_interface'] = self._need_ncl(
            raw_recipe['diagnostics'])
        self._filename = os.path.basename(recipe_file)
        self._preprocessors = raw_recipe.get('preprocessors', {})
        if 'default' not in self._preprocessors:
            self._preprocessors['default'] = {}
        self.diagnostics = self._initialize_diagnostics(
            raw_recipe['diagnostics'], raw_recipe.get('datasets', []))
        self.entity = self._initalize_provenance(
            raw_recipe.get('documentation', {}))
        self.tasks = self.initialize_tasks() if initialize_tasks else None
        

The recipe file is then an object created from the YAML file that define it and the config-user.yml file. And then by a set of methods:

  • self.diagnostics
  • self.entity
  • self.tasks

and they are executed in this order above.