Changelog#

Versions follow Semantic Versioning (<major>.<minor>.<patch>).

Backward incompatible (breaking) changes will only be introduced in major versions with advance notice in the Deprecations section of releases.

climate-ref 0.7.0 (2025-10-01)#

Breaking Changes#

• Use the directory structure template from the obs4MIPs specification to define the instance_id. (#383)
• Used logical or instead of logical and to combine multiple facet filters.

This means that the selected input datasets will include items that match any of the specified FacetFilters, rather than only those that match all of them. This change was made to improve the usability of the option to use multiple facet filters, allowing users to be more specific with their filtering criteria. (#414) - Changed all constraints so they return a filtered dataframe instead of a boolean.

This allows using the constraints in multi-model diagnostics. (#416)

Features#

• Add a timerange constraint to ensure the required data is available. (#399)
• Add a human readable representation for climate_ref_core.datasets.ExecutionDatasetCollection. (#401)
• Allow execution outputs to have dimensions. These dimensions allow the outputs to be filtered in the same manner as the metric values (#434)
• Adds filter options to the ref executions list-groups command. This allows users to filter by facet, provider and diagnostic, as well as whether the latest executions was successful or if the exection group was has been marked as dirty (#438)
• Added a ref executions delete-groups command for removing unneeded results from the database. This will delete the execution group and any executions and outputs associated with the group. (#441)

Improvements#

• Updated the sample data to v0.7.3. (#402)
• PMP version updated to v3.9.2 (#404)
• Specified the "table_id" for all ESMValTool diagnostics to improve data selection. (#407)
• Added a groupby operation to the RequireFacets constraint to reduce failed runs because of missing data. (#408)
• Adds extra ESMValTool dimensions to the output series (#410)
• The dataset ingestion process now supports updating datasets if new files become available (#412)
• Added series output for ESMValTool diagnostics. (#413)
• Gracefully handles empty directories when ingesting. The default behaviour is now to skip any invalid datasets as that is a sane default when ingesting many datasets. (#419)
• Include obs4MIPs and thetao in the ESGF download script and turn into a CLI tool. This script was renamed to fetch-esgf.py to fetch-esgf.py as it now includes more than just CMIP6 data. (#420)
• Improved support for concatenating historical and future experiments in the ESMValTool recipe (#431)
• Log the ESMValTool recipe and configuration for easier debugging (#432)
• Adds output dimensions to ILAMB outputs. This adds additional dimensions and attributes to the series values (#435)
• Replaced instance_id by individual facets in group_by of ESMValTool diagnostics. (#439)

Bug Fixes#

• Resolves missing index and index names for series (#410)
• Added missing column to the PMP dataset model (#418)
• Removes the ERA-5 ta data Obs4REF in preference for Obs4MIPs (#421)
• Avoid selecting the areacella variable when filling the recipe for cloud scatterplots. (#427)
• Fixes to the ocean heat content IOMB diagnostic (#433)

Trivial/Internal Changes#

• #440

climate-ref 0.6.6 (2025-09-10)#

Features#

• Added a diagnostic to create scatterplots of two cloud-relevant variables. (#261)
• Added support for serialising series metric values from an execution. These series metric values are also ingested into the database for later retrieval.

Currently, only the ESMValTool example diagnostic supports this feature, but this will be extended to other diagnostics in the future. (#374) - Added regional historical changes diagnostics. (#380) - Shifts ILAMB executions to be per experiment/model/ensemble/grid as opposed to all models for a given experiment. Also dumps out series information into the database for all time traces found in the output files. (#391) - Made it possible to run PMP diagnostics without having conda installed. (#392) - Added climate drivers for fire diagnostic. (#393) - Added a sub-command to ref executions that allows you to flag an execution as dirty. (#396)

Improvements#

• Use a self-hosted CI runner for the integration tests. The GitHub runner do not have enough disk space to store the required datasets, and these data are downloaded over the internet on each run. (#365)
• Updated the sample data to v0.7.1. (#385)
• Adds additional indexes for some slow queries in the API (#395)
• Better error message when a user tries to use the HPCExecutor on Windows (#397)

Bug Fixes#

• Fix bug in writing ESMValTool recipes that loses order of preprocessing steps. This bug was introduced in #378 and included in the v0.6.5 release. (#384)

climate-ref 0.6.5 (2025-08-25)#

Features#

• Add support for NCI PBS Scheduler to the HPCExecutor (#358)
• Added sea ice sensitivity diagnostic. (#378)
• Added data required for regional historical changes diagnostics. (#379)

Improvements#

• Added a dataset ingestor for CMIP6 data that only uses the DRS information present in the filename. This greatly speeds up the process of ingesting a large number of files, as it does not require reading the file contents to extract the DRS information.

This method can be opted into by specifying cmip6_parser: "drs" in the REF configuration file. The default parser remains the complete parser, which reads the file contents to all the required metadata, but this will change in a future PR. (#366)

Improved Documentation#

• Address documentation review from the Model Benchmarking Task Team (#371)

climate-ref 0.6.4 (2025-08-04)#

Deprecations#

• The --package option of the ref celery start-worker command has been deprecated and scheduled for removal. This functionality is now handled by the --provider option which uses entry points declared in the provider packages. (#367)

Features#

• Use entrypoints to register provider plugins. (#360)
• Support celery workers to consume tasks for multiple providers (#367)

Improvements#

• Add additional dimensions to the example metric for testing purposes. (#372)
• Added a basic script to the CMIP6 data targetted by the current set of diagnostics for the Assessment Fast Track. (#373)

climate-ref 0.6.3 (2025-07-17)#

Improvements#

• Use a new URL for serving the reference data. This should now support older versions of TLS which may help some users. (#364)

climate-ref 0.6.2 (2025-07-09)#

Improvements#

• Implemented the parsl retry function (#341)
• Allow arbitrary environment variables to be used in paths in the configuration file. (#349)
• No longer automatically try to create the conda environment for a provider when running diagnostics. (#354)
• Use provider conda environments from the configured location when running tests. (#357)
• Remove the dependency on ruamel.yaml in climate-ref-core (#361)
• Clarify that we don't technically support Windows at the moment, but it is possible to use WSL or a VM. (#362)

Improved Documentation#

• Add documentation for the CLI tool (#343)

climate-ref 0.6.1 (2025-05-28)#

Features#

• Implemented a HPCExecutor. It could let users run REF under HPC workflows by submitting batch jobs and compute diagnostics on the computer nodes. Only the slurm scheduler is supported now. (#305)

Bug Fixes#

• Remove keys with their value None from the output JSON for CMEC validation of PMP extratropical variability modes (#337)

Improved Documentation#

• Add Getting Started section for ingesting and solving (#342)

climate-ref 0.6.0 (2025-05-27)#

Breaking Changes#

• Updated the group by dimensions for the PMP diagnostics. This will cause duplicate runs to appear if an existing database is used. We recommend starting with a new database if using the next release. (#321)

Features#

• Implemented PMP ENSO metrics (#273)
• Added ESMValTool ENSO diagnostics. (#320)
• Add the creation of verbose debug logs. These logs will be created in the $REF_CONFIGURATION/log directory (or overriden via the config.paths.log setting). (#323)
• Data catalogs now only contain the latest version of a dataset. This will trigger new executions when a new version of a dataset is ingested.

Some additional datasets have been added to the obs4REF dataset registry. These datasets should be fetched and reingested. (#330) - Added a comparison of burntFractionAll to the ILAMB list of diagnostics (#332) - Adds --diagnostic and --provider arguments to the ref solve command. This allows users to subset a specific diagnostic or provider that they wish to run. Multiple --diagnostic or --provider arguments can be used to specify multiple diagnostics or providers. The diagnostic or provider slug must contain one of the filter values to be included in the calculations. (#338)

Improvements#

• Raise the ilamb3 version to 2025.5.20 and add remaining ILAMB/IOMB metrics. (#317)
• Adds Ocean Heat Content and snow cover datasets to the ilamb/iomb registry (#318)
• Updated the ESMValTool version to include updated recipes and diagnostics. (#325)
• Add obs4MIPs ERA-5 ta sample data as obs4REF. (#334)
• Enable more variables for the annual cycle diagnostics via PMP. (#335)
• Verify the checksum of downloaded datasets by default (#336)

Bug Fixes#

• Depth selects properly in mrsos, added regression data (#331)

climate-ref 0.5.5 (2025-05-21)#

Improvements#

• Added additional dimensions to the ILAMB and ESMValTool metric values. This includes additional information about the execution group that will be useful to end-users. (#308)
• Move the ILAMB datasets to S3 (#309)
• Clean ECS diagnostic (remove unused keys in ESMValTool recipes and avoid "cmip6" in diagnostic name) (#310)
• Clean TCR diagnostic (remove unused keys in ESMValTool recipes and avoid "cmip6" in diagnostic name) (#311)

Improved Documentation#

• Updated documentation to include more information about concepts within the REF. (#312)

climate-ref 0.5.4 (2025-05-19)#

Bug Fixes#

• Add additional dependencies to the climate-ref-core so that it is self-contained (#307)

climate-ref 0.5.3 (2025-05-19)#

Features#

• Diagnostic's have been split into two phases, executing which generates any outputs and then building a result object from the outputs. This split makes it easier to make modifications to how the results are translated into the CMEC outputs. (#303)

Improvements#

• Added automatic backup of SQLite database files before running migrations. Backups are stored in a backups directory adjacent to the database file and are named with timestamps. The number of backups to retain can be configured via the db.max_backups setting in the database configuration, with a default of 5 backups. (#301)
• Update to v0.6.0 of the sample data. (#302)
• Add a smoke test for the Celery deployment (#304)
• Add tests that the pypi releases are installable (#306)

Improved Documentation#

• Added page describing the required reference datasets (#298)

climate-ref 0.5.2 (2025-05-15)#

Bug Fixes#

• Fix missing dependency in migrations (#297)

Improved Documentation#

• Added documentation for configuration options (#296)

climate-ref 0.5.1 (2025-05-14)#

Features#

• Added an ESMValTool metric to compute climatologies and zonal mean profiles of cloud radiative effects. (#241)
• Add additional dimensions to the metrics produced by PMP. Added climate_ref_core.pycmec.metric.CMECMetric.prepend_dimensions (#275)
• Ensure that selectors are always alphabetically sorted (#276)
• Add data model for supporting series of metric values. This allows diagnostic providers to supply a collection of climate_ref_core.metric_values.SeriesMetricValue extracted from an execution. (#278)
• The default executor (climate_ref.executor.LocalExecutor) uses a process pool to enable parallelism. An alternative climate_ref.executor.SynchronousExecutor is available for debugging purposes, which runs tasks synchronously in the main thread. (#286)

Improvements#

• Bumps the ilamb3 version to now contain all analysis modules and reformats its CMEC output bundle. (#262)
• Adds the ability to capture the output of an execution for regression testing. (#274)
• Update to v0.5.1 of the sample data. (#279)
• Update to v0.5.2 of the sample data. (#282)
• Add a CITATION.cff to the repository to make it easier to cite. (#283)
• Added the Assessment Fast Track-related services to the docker-compose stack alongside improved documentation for how to use the REF via docker containers. (#287)
• Added support for ingesting multiple directories at once. This is useful for ingesting large datasets that are split into multiple directories or via glob patterns. An example of this is importing the monthly and fx datasets from an archive of CMIP6 data:

bash ref datasets ingest --source-type cmip6 path_to_archive/CMIP6/*/*/*/*/*/*mon path_to_archive/CMIP6/*/*/*/*/*/fx (#291) - Update the default log level to INFO from WARNING. Added the -q option to decrease the log level to WARNING. (#292)

Bug Fixes#

• Resolves an issue that was blocking some PMP executions from completing. Any additional dimensions are now logged and ignored rather than causing the execution to fail. (#274)
• Sets the environment variable FI_PROVIDER=tcp to use the TCP provider for libfabric (part of MPICH). The defaults were causing MPICH errors on some systems (namely macOS). This also removes the PMP provider's direct dependency on the source of pcmdi_metric. (#281)
• Support the use of empty metric bundles (#284)
• Reworked the lifetimes of the database transactions during the solve process. This is a fix for out of process executors where the transaction was not being committed until the end of a solve. (#288)
• Requery an Execution from the database when handling the result from the LocalExecutor. This ensures that the execution isn't stale and that the result is still valid. (#293)

climate-ref 0.5.0 (2025-05-03)#

Breaking Changes#

• Renamed packages to start with climate_ref_ and removed metrics from the package name to avoid confusion. This changes the root name of the PyPi packages from cmip_ref to climate-ref and will require updating your requirements.txt, pyproject.toml, setup.py, or other dependency management files to list climate-ref instead of cmip_ref. (#270)
• Clarified the difference between a diagnostic and a metric. This caused significant refactoring of names of classes and functions throughout the codebase, as well as renaming of database tables.

This removes any previous database migrations and replaces them with a new clean migration. If you have an existing database, you will need to delete it and re-create it. (#271)

cmip_ref 0.4.1 (2025-05-02)#

Breaking Changes#

• Removed unnecessary prefixes in the metric slugs. This will cause duplicate results to be generated so we recommend starting with a clean REF installation. (#263)

Features#

• Added PMP's annual cycle metrics (#221)
• Add a facets attribute to a metric. This attribute is used to define the facets of the values that the metric produces. (#255)
• Added a diagnostic to calculate climate variables at global warming levels. (#257)
• Support multiple sets of data requirements (#266)

Bug Fixes#

• Retry downloads if they fail (#267)
• PMP annual cycle output JSON tranformed to be more comply with CMEC (#268)

Improved Documentation#

• Add deprecation notices to PyPi package README's (#269)

cmip_ref 0.4.0 (2025-04-29)#

Breaking Changes#

• Removed climate_ref.solver.MetricSolver.solve_metric_executions in preference for a standalone function climate_ref.solver.solve_metric_executions with identical functionality. (#229)
• Updated the algorithm to generate the unique identifier for a Metric Execution Group. This will cause duplicate entries in the database if the old identifier was used. We recommend removing your existing database and starting fresh. (#233)
• Removed the implicit treatment of the deepest dimension. The change will cause a validation error if the deepest dimension in the RESULTS is a dictionary. (#246)
• Ensure that the order of the source dataset types in the MetricExecutionGroup dataset key are stable (#248)

Deprecations#

• Removes support for Python 3.10. The minimum and default supported Python version is now 3.11. (#226)

Features#

• Add the basic framework for enforcing a controlled vocabulary for the results in a CMEC metrics bundle. This is still in the prototype stage and is not yet integrated into post-metric execution processing. (#183)
• Scalar values from the metrics are now stored in the database if they pass validation. The controlled vocabulary for these metrics is still under development. (#185)
• Added Zero Emission Commitment (ZEC) metric to the ESMValTool metrics package. (#204)
• Added Transient Climate Response to Cumulative CO2 Emissions (TCRE) metric to the ESMValTool metrics package. (#208)
• Add ref datasets fetch-obs4ref-data CLI command to fetch datasets that are in the process of being published to obs4MIPs and are appropriately licensed for use within the REF. The CLI command fetches the datasets and writes them to a local directory. These datasets can then be ingested into the REF as obs4MIPs datasets. (#219)
• Enabled metric providers to register registries of datasets for download. This unifies the fetching of datasets across the REF via the ref datasets fetch-data CLI command. Added registries for the datasets that haven't been published to obs4MIPs yet (obs4REF) as well as PMP annual cycle datasets. (#227)
• Capture log output for each execution and display via ref executions inspect. (#232)
• Added the option to install development versions of metrics packages. (#236)
• Added seasonal cycle and time series of sea ice area metrics. (#239)
• The unique group identifiers for a MetricExecutionGroup are now tracked in the database. These values are used for presentation. (#248)
• Added a new dataset source type to track PMP climatology data (#253)

Improvements#

• Refactored MetricSolver.solve_metric_executions to be a standalone function for easier testing. Also added some additional integration tests for the Extratropical Modes of Variability metric from PMP. (#229)
• The configuration paths are now all resolved to absolute paths (#230)
• Verified support for PostgreSQL database backends (#231)
• Updated the ESMValTool metric and output bundles. (#235)
• Update to v0.5.0 of the sample data (#264)

Bug Fixes#

• Relax some of the requirements for the availability of metadata in CMIP6 datasets. (#245)
• Added a missing migration and tests to ensure that the migration are up to date. (#247)
• Fixed how the path to ESMValTool outputs was determined, and added support for outputs in nested directories. (#250)
• Marked failing tests as xfail as a temporary solution. (#259)
• Fetch ESMValTool reference data in the integration test suite (#265)

Improved Documentation#

• Now following SPEC-0000 for dependency support windows. Support for Python versions will be dropped after 3 years and support for key scientific libraries will be dropped after 2 years. (#226)
• Migrate from the use of ‘AR7 Fast Track’ to ‘Assessment Fast Track’ in response to the CMIP Panel decision to change the name of the CMIP7 fast track. (#251)

Trivial/Internal Changes#

• #220

cmip_ref 0.3.1 (2025-03-28)#

Trivial/Internal Changes#

• #218

cmip_ref 0.3.0 (2025-03-28)#

Breaking Changes#

• We changed the ref Command Line Interface to make the distinction between execution groups and individual executions clear. A metric execution is the evaluation of a specific metric for a specific set of input datasets. We group together all executions for the same set of input datasets which are re-run because the metric or the input datasets were updated or because a metric execution failed. For showing results, it is more useful to think in terms of execution groups. In particular, the ref executions list command was re-named to ref executions list-groups. (#165)

Features#

• Support ingesting obs4MIPs datasets into the REF (#113)
• Add extratropical modes of variability analysis using PMP (#115)
• Added management of conda environments for metrics package providers.

Several new commands are available for working with providers: - ref providers list - List the available providers - ref providers create-env - Create conda environments for providers

(#117) - Added CMECMetric.create_template method to create an empty CMEC metric bundle. (#123) - Outputs from a metric execution and their associated metadata are now tracked in the database. This includes HTML, plots and data outputs.

Metric providers can register outputs via the CMEC output bundle. These outputs are then ingested into the database if the execution was successful. (#125) - Build and publish container images to Github Container Registry (#156) - Enable more variability modes for PMP modes of variability metrics (#173) - Add a --timeout option to the solve cli command. This enables the user to set a maximum time for the solver to run. (#186)

Improvements#

• Cleanup of ilamb3 interface code, enabling IOMB comparisons. (#124)
• Migrate the PMP provider to use a REF-managed conda environment.

For non-MacOS users, this should be created automatically. MacOS users will need to create the environment using the following command:

bash MAMBA_PLATFORM=osx-64 uv run ref providers create-env --provider pmp (#127) - Fixed issue with mypy not being run across the celery package (#128) - Added the fetch-ref-data make command to download reference data while it's not in obs4mips, yet. (#155) - Improvements: - Drop the metric plugin version number in the environment name because the environment may not change between releases - Avoid calling micromamba update as this may not work for everyone - Print out the location of environments even when they are not installed - Do not mention conda as a requirement on the Hackathon page

(#160) - Add activity and institute to ESMValTool recipes to allow running with models and experiments that are not in the CMIP6 controlled vocabulary. (#166) - Add an integration test for the CMIP7 AFT metric providers. This will be run nightly as part of the Climate-REF CI pipeline. (#187) - Improved the error message when running ref datasets list with the --column argument. If a column is specified that is not available, the error message now only mentions the invalid column name(s) and shows a list of available columns. (#203) - Do not list duplicate entries in dataframes shown from the command line. (#210)

Bug Fixes#

• Remove example metric for ILAMB (#121)
• Removed the "SCHEMA" attribute from the CMEC metric bundle as it is not part of the EMDS specification and unused. (#123)
• Fixed the validation error when 'attributes' value is a dict (#133)
• Fixed PMP's modes of variablity PDO metrics driver to use obs4MIP-complying reference dataset. Also update PMP's version to 3.9, which include turning off direct usage of conda as a part of the driver (to capture provenance info) (#154)
• Enforce the use of relative paths when copying files after an execution. This resolves an issue where files were not being copied to the correct location causing failures in PMP. (#170)
• If no obs4mips-compliant reference dataset is found in specified directory, give a meaningful error message. (#174)
• Fixed the behaviour of FacetFilter with keep=False so all facets need to match before excluding a file. (#209)

Improved Documentation#

• Renamed CMIP-REF to Climate-REF (#119)
• Add a landing page for hackathon attendees (#120)
• Fix the incorrect capitalisation of GitHub organisation (#122)
• Updated the getting started documentation. (#126)
• Update the roadmap to reflect progress as of 2025/03/10 (#134)
• Clarified language and other small fixes in the documentation. (#178)

Trivial/Internal Changes#

• #161, #182, #184, #207

cmip_ref 0.2.0 (2025-03-01)#

Breaking Changes#

• Refactor climate_ref.env module to climate_ref_core.env (#60)
• Removed climate_ref.executor.ExecutorManager in preference to loading an executor using a fully qualified package name.

This allows the user to specify a custom executor as configuration without needing any change to the REF codebase. (#77) - Renamed the $.paths.tmp in the configuration to $.paths.scratch to better reflect its purpose. This requires a change to the configuration file if you have a custom configuration. (#89) - The REF now uses absolute paths throughout the application.

This removes the need for a config.paths.data directory and the config.paths.allow_out_of_tree_datasets configuration option. This will enable more flexibility about where input datasets are ingested from. Using absolute paths everywhere does add a requirement that datasets are available via the same paths for all nodes/container that may run the REF. (#100) - An Executor now supports only the asynchronous processing of tasks. A result is now not returned from the run_metric method, but instead optionally updated in the database.

The run_metric method also now requires a provider argument to be passed in. (#104)

Features#

• Adds a cmip-ref-celery package to the REF that provides a Celery task queue.

Celery is a distributed task queue that allows you to run tasks asynchronously. This package will be used as a test bed for running the REF in a distributed environment, as it can be deployed locally using docker containers. (#60) - Add metric_providers and executor sections to the configuration which loads the metric provider and executor using a fully qualified package name. (#77) - Implemented Pydantic data models to validate and serialize CMEC metric and output bundles. (#84) - Add the climate_ref_celery CLI commands to the ref CLI tool. These commands should be available when the climate_ref_celery package is installed. The commands should be available in the ref CLI tool as ref celery .... (#86) - Add fetch-sample-data to the CLI under the datasets command.

bash ref datasets fetch-sample-data --version v0.3.0 --force-cleanup (#96) - Add a Celery-based executor to enable asynchronous processing of tasks. (#104) - Add ref executions list and ref executions inspect CLI commands for interacting with metric executions. (#108)

Improvements#

• Move ILAMB/IOMB reference data initialization to a registry-dependent script. (#83)
• ILAMB gpp metrics added with full html output and plots. (#88)
• Saner error messages for configuration errors (#89)
• Centralised the declaration of environment variable overrides of configuration values.

Renamed the REF_OUTPUT_ROOT environment variable to REF_RESULTS_ROOT to better reflect its purpose. It was previously unused. (#92) - Sample data is now copied to the test/test-data/sample-data instead of symlinked.

This makes it easier to use the sample data with remote executors as the data is now self-contained without any links to other parts of the file system. (#96) - Integrated the pycmec validation models into ref core and metric packages (#99) - Added ILAMB relationship analysis to the current metrics and flexibility to define new metrics in ILAMB via a yaml file. (#101) - Sped up the test suite execution (#103)

Improved Documentation#

• Added an excerpt from the architecture design document (#87)
• Adds a roadmap to the documentation (#98)

Trivial/Internal Changes#

• #97, #102, #116, #118

cmip_ref 0.1.6 (2025-02-03)#

Features#

• Added Equilibrium Climate Sensitivity (ECS) to the ESMValTool metrics package. (#51)
• Added Transient Climate Response (TCS) to the ESMValTool metrics package. (#62)
• Added the possibility to request datasets with complete and overlapping timeranges. (#64)
• Added a constraint for selecting supplementary variables, e.g. cell measures or ancillary variables. (#65)
• Added a sample metric to the ilamb metrics package. (#66)
• Added a sample metric to the PMP metrics package. (#72)
• • Added the standard ILAMB bias analysis as a metric. (#74)

Bug Fixes#

• • Added overlooked code to fully integrate ilamb into ref. (#73)
• Correct the expected configuration name to ref.toml as per the documentation. (#82)

Improved Documentation#

• Update the package name in the changelog.

This will simplify the release process by fixing the extraction of changelog entries. (#61)

Trivial/Internal Changes#

• #68

cmip_ref 0.1.5 (2025-01-13)#

Trivial/Internal Changes#

• #56

cmip_ref 0.1.4 (2025-01-13)#

Breaking Changes#

• Adds an ingest CLI command to ingest a new set of data into the database.

This breaks a previous migration as alembic's render_as_batch attribute should have been set to support targeting sqlite. (#14) - Renames ref ingest to ref datasets ingest (#30) - Prepend package names with cmip_ to avoid conflicting with an existing PyPI package.

This is a breaking change because it changes the package name and all imports. All package names will now begin with cmip_ref. (#53)

Features#

• Migrate to use UV workspaces to support multiple packages in the same repository. Adds a climate-ref-example package that will be used to demonstrate the integration of a metric package into the REF. (#2)
• Adds the placeholder concept of Executor's which are responsible for running metrics in different environments. (#4)
• Adds the concept of MetricProvider's and Metrics to the core. These represent the functionality that metric providers must implement in order to be part of the REF. The implementation is still a work in progress and will be expanding in follow-up PRs. (#5)
• Add a collection of ESGF data that is required for test suite.

Package developers should run make fetch-test-data to download the required data for the test suite. (#6) - Adds the ref package with a basic CLI interface that will allow for users to interact with the database of jobs. (#8) - Add SqlAlchemy as an ORM for the database alongside alembic for managing database migrations. (#11) - Added a DataRequirement class to declare the requirements for a metric.

This provides the ability to:

• filter a data catalog
• group datasets together to be used in a metric calculation
• declare constraints on the data that is required for a metric calculation

(#15) - Add a placeholder iterative metric solving scheme (#16) - Extract a data catalog from the database to list the currently ingested datasets (#24) - Translated selected groups of datasets into MetricDatasets. Each MetricDataset contains all of the dataset's needed for a given execution of a metric.

Added a slug to the MetricDataset to uniquely identify the execution and make it easier to identify the execution in the logs. (#29) - Adds ref datasets list command to list ingested datasets (#30) - Add database structures to represent a metric execution. We record previous executions of a metric to minimise the number of times we need to run metrics. (#31) - Added option to skip any datasets that fail validation and to specify the number of cores to use when ingesting datasets. This behaviour can be opted in using the --skip-invalid and --n-jobs options respectively. (#36) - Track datasets that were used for different metric executions (#39) - Added an example ESMValTool metric. (#40) - Support the option for different assumptions about the root paths between executors and the ref CLI.

Where possible path fragments are stored in the database instead of complete paths. This allows the ability to move the data folders without needing to update the database. (#46)

Improvements#

• Add a bump, release and deploy flow for automating the release procedures (#20)
• Migrate test data into standalone Climate-REF/ref-sample-data repository.

The sample data will be downloaded by the test suite automatically into tests/test-data/sample-data, or manually by running make fetch-test-data. (#49)

Bug Fixes#

• Adds version field to the instance_id field for CMIP6 datasets (#35)
• Handle missing branch times. Fixes #38. (#42)
• Move alembic configuration and migrations to cmip_ref package so that they can be included in the distribution. (#54)

Improved Documentation#

• Deployed documentation to https://climate-ref.readthedocs.io/en/latest/ (#16)
• General documentation cleanup.

Added notebook describing the process of executing a notebook locally (#19) - Add Apache licence to the codebase (#21) - Improved developer documentation. (#47)

Trivial/Internal Changes#

• #41, #44, #48, #52, #55