ACACIA S2S Toolkit (acacia-s2s-toolkit)
Disclaimer: This package is provided for research purposes only. It is not intended for use in any operational or production context. It is not an officially supported ECMWF software product.
Overview
acacia-s2s-toolkit is a Python library that supports downloading and post-processing of dynamical sub-seasonal forecast data from the ECMWF Data Store
It builds on xarray for efficient NetCDF-based data handling.
Software Maturity
| Attribute | Status |
|---|---|
| Maturity | |
| Support level | Best effort — no guaranteed response time |
| Operational use | Not suitable for operational use |
Installation
To install the acacia-s2s-toolkit on Linux, run the following command:
python3 -m pip install acacia_s2s_toolkit
For guidance on installing Python 3 or pip, refer to the official documentation.
Dependencies
The AI-WQ-package requires the following dependencies:
- numpy (version 1.23 or higher)
- xarray (version 2024.09.0 or higher)
- dask (version 2024.9.0)
- pandas (version 2.2.3 or higher)
- scipy (version 1.14.1 or higher)
- netCDF4 (version 1.7.2 or higher)
- requests (versions 2.32.2 or higher)
- matplotlib (versions 3.8 or higher)
- cartopy (versions 0.22 or higher)
If these dependencies conflict with your current working environment, consider installing the package in a new virtual environment.
Additionally, to enable automatic download of the appropriate lookup table, you will also need to install the ECMWF sites-toolkit package:
python3 -m pip install sites-toolkit -i https://get.ecmwf.int/repository/pypi-all/simple
Upgrading the Package
To upgrade to the latest version, run:
python3 -m pip install --upgrade acacia_s2s_toolkit
This project is being actively developed. New updates may be released periodically with detailed annoucements given on the ECMWF-hosted forum.
License
This project is licensed under the Apache License 2.0. See the LICENSE file for the full text.
In applying this licence, ECMWF does not waive the privileges and immunities granted to it by virtue of its status as an intergovernmental organisation, nor does it submit to any jurisdiction.
Support
This package is not officially supported by ECMWF.
For general ECMWF-related enquiries, please use the ECMWF Service Desk.
Documentation
Full documentation is available on ReadTheDocs:
Metadata
Release files for acacia-s2s-toolkit 2.50
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| acacia_s2s_toolkit-2.50.tar.gz | 2.0 MB | Without provenance | Details for acacia_s2s_toolkit-2.50.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| acacia_s2s_toolkit-2.50-py3-none-any.whl | Python 3 | none | any | Details for acacia_s2s_toolkit-2.50-py3-none-any.whl |
Total release size: 2.1 MB
Release files / acacia_s2s_toolkit-2.50.tar.gz
| Download URL | acacia_s2s_toolkit-2.50.tar.gz |
|---|---|
| Size | 2.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
85a7c77a93d9b649384b08be29e3ec6378fe4769f8fbc6be00b7e5ac99b3e3f9
|
|
BLAKE2b-256 checksum How to use checksums |
a8c91a81bac1082a453f3c68f7abc032283daf67867959742809c3e0bf23e394
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Release files / acacia_s2s_toolkit-2.50-py3-none-any.whl
| Download URL | acacia_s2s_toolkit-2.50-py3-none-any.whl |
|---|---|
| Size | 97.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5964b50ccd4e7cc774112a8df0a8ac6b0f4040a327eec83196a01ce95bbc4855
|
|
BLAKE2b-256 checksum How to use checksums |
6b6df533ea48820bc9d4ddecb55e9731f4e78905e01fc03c965979c3b76007df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Security for acacia-s2s-toolkit 2.50
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.