AQUA
The Application for QUality Assessment (AQUA) is a model evaluation framework designed for running diagnostics on high-resolution climate models, specifically for Climate DT climate simulations being part of Destination Earth activity. The package provides a flexible and efficient python3 framework to process and analyze large volumes of climate data. With its modular design, AQUA offers seamless integration of core functions and a wide range of diagnostic tools that can be run in parallel. AQUA offers:
- Efficient handling of large datasets from high-resolution climate models;
- Support for various data formats, such as NetCDF, GRIB, Zarr or FDB;
- Robust and fast regridding functionality based on CDO;
- Averaging and aggregation tools for temporal and spatial analyses;
- Modular design for easy integration of new diagnostics.
Installation
AQUA requires python>=3.11,<3.15. Recommended installation should be done through a package manager for conda-forge (e.g. Miniforge).
Create conda/mamba environment and install packages
git clone git@github.com:DestinE-Climate-DT/AQUA.git
cd AQUA
mamba env create -f environment.yml
mamba activate aqua
This installation will provide both the AQUA framework and the AQUA diagnostics.
Use of AQUA container
An alternative deployment making use of containers is available. Please refer to the Container chapter in the AQUA Documentation.
Documentation
Full AQUA Documentation is available on ReadTheDocs.
Examples
Please look at the notebook folder to explore AQUA functionalities.
Command lines tools
Please look at the cli folder to have access to the AQUA command line tools.
Contributing guide
Please refer to the Guidelines for Contributors if you want to join AQUA team!
License
AQUA is distributed as open source software under Apache 2.0 License. The copyright owner is the European Union, represented by the European Commission. The development of AQUA has been funded by the European Union through Contract DE_340_CSC - Destination Earth Programme Climate Adaptation Digital Twin (Climate DT). Further info can be found at https://destine.ecmwf.int/ and https://destination-earth.eu/
Metadata
Release files for aqua-core 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| aqua_core-1.1.0.tar.gz | 331.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aqua_core-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 659.7 kB
Release files / aqua_core-1.1.0.tar.gz
| Download URL | aqua_core-1.1.0.tar.gz |
|---|---|
| Size | 331.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db76d9cc57d543466345bcf8faad8702adad62daca8e07f61967a243371be223
|
|
BLAKE2b-256 checksum How to use checksums |
031dbe0fb7d11752b2d628b2280f7c140156657ceee01a09989637a9302f6125
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 4, 2026.
Transparency logRelease files / aqua_core-1.1.0-py3-none-any.whl
| Download URL | aqua_core-1.1.0-py3-none-any.whl |
|---|---|
| Size | 328.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
452684c331b63ac654cbd3b90f3bddd7b1708a99eccaa6f90f716109d35c644b
|
|
BLAKE2b-256 checksum How to use checksums |
fe85c6c6f00456abf6cd5ada7f38ebebfbcdbb2a5f118d34303ac8c87f439e0c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 4, 2026.
Transparency log