The Battle of the Water Futures 🚰
Designing the next generation of urban water systems
The Battle of the Water Futures is competition hosted at the 4th International Joint Conference on Water Distribution Systems Analysis and Computing and Control in the Water Industry (WDSA/CCWI 2026), taking place in Paphos, Cyprus, from May 18-21, 2026. The objective is to design and operate a water distribution system over a long-term horizon under deep uncertainty, with interventions applied in stages.
Read the Full Details 🔎
The most up-to-date information, the full index, and all competition details are hosted on our official website and the Zenodo repository.
➡️ Visit the official competition website ⬅️
➡️ Visit the official competition website ⬅️
➡️ Read the problem description on (arXiv) ⬅️
Do you have questions?
Check out our discussion page on GitHub or, if you can't find an answer, send us an email to battlewaterfutures@kwrwater.nl.
This competition is organized by the Water-Futures team. Explore our projects on GitHub and learn more about our team and work on our website.
Water-Futures has received funding from the European Research Council (ERC) under the European Union’s Horizon 2020 research and innovation program (Grant Agreement No. 951424).
Metadata
Release files for water-futures-battle 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 | Provenance | Actions |
|---|---|---|---|---|
| water_futures_battle-1.1.0.tar.gz | 129.3 kB | Without provenance | Details for water_futures_battle-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| water_futures_battle-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for water_futures_battle-1.1.0-py3-none-any.whl |
Total release size: 295.7 kB
Release files / water_futures_battle-1.1.0.tar.gz
| Download URL | water_futures_battle-1.1.0.tar.gz |
|---|---|
| Size | 129.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b7d3366aa6fc9d1c44882ce070a341acb6f18f81c9c631b08e597bef654edee8
|
|
BLAKE2b-256 checksum How to use checksums |
f024651338479695dfd08fed71426a43e735a083b88ace793a68c9a5338326a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.2 {"installer":{"name":"uv","version":"0.11.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / water_futures_battle-1.1.0-py3-none-any.whl
| Download URL | water_futures_battle-1.1.0-py3-none-any.whl |
|---|---|
| Size | 166.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
247b8abd14e8e31a8eb4a533e4fbe963da1e765da2bfd106fb0222be62b096c1
|
|
BLAKE2b-256 checksum How to use checksums |
ccee78b3aee971888c71f455366f9bb5b30ca4025d9e5e0772e1a0eed6dfd049
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.2 {"installer":{"name":"uv","version":"0.11.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for water-futures-battle 1.1.0
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.