Veriflow
A reproducible verification pipeline for evaluating model outputs and forecasts.
Warning: Veriflow is currently in the a minor-version stage (0.x.x). Breaking changes may occur in minor releases while the public API continues to mature. A first major release is planned for 2027. Interested in contributing? See our contributing guide.
- 📥 Fetching data
- 🧮 Computing scores
- 📝 Writing results
Key features
- ✅ Full control over the verification pipeline via configuration
- ✅ Native integration with Delft-FEWS
- ✅ Native integration with local and remote (S3) Zarr
- ✅ Builds on scores for computation of scores. This package has extensive functionality, and it's documentation is world-class.
- ✅ Extensible with your own (private) datasources, scores and datasinks
- ✅ Optimized internal datamodel for efficient computation
Installation
Install from PyPI:
pip install veriflow
Or using uv:
uv pip install veriflow
See CONTRIBUTING.md for development setup.
Running a verification pipeline with veriflow
The below example shows you the minimal code to run a verification pipeline.
from veriflow import run_pipeline
from pathlib import Path
# Create your config and point to the file
path_to_config = Path("./config.yml")
# Run your verification pipeline in just one line of code
dt: xr.DataTree = run_pipeline((path_to_config, "yaml"))
If it's your wish to further analyze the input data and verification results in an interactive Python session, assign the returned xr.DataTree from run_pipeline to a Python variable as in the code block above. For each each configured verification_pair*, the datatree contains input and output data for each verification pair.
This allows for easy post-hoc analysis, visualization and further connection to external applications such as dashboards. See our API documentation for a detailed overview of the datatree structure.
*a verification pair defines two data arrays: a reference data array and a evaluation data array. An example verification pair could be a combination of observed data and simulated forecast data for a given physical variable.
👥 Who Is This For?
This project is aimed at anyone who's interested in assessing model and forecast quality in an easy and reproducible way, like:
- operational forecasters
- model developers
- researchers and data-scientists
Why this package?
Verification pipelines are complex: metrics require specialized computation, data volumes may exceed memory, and sources/destinations can vary widely. This package simplifies verification by handling the entire pipeline via a single configuration file. It's reliable (tested and versioned), transparent (fully documented), reproducible, and flexible—extensible with custom datasources, scores, and datasinks. Any pipeline created is immediately transferable to other users and systems.
So wether you're working on model development or operational forecasting: this tool can help you build robust and reproducible verification pipelines.
Technical features
Metadata
Release files for veriflow 0.4.2
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 |
|---|---|---|---|---|
| veriflow-0.4.2.tar.gz | 109.9 kB | With provenance | Details for veriflow-0.4.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| veriflow-0.4.2-py3-none-any.whl | Python 3 | none | any | Details for veriflow-0.4.2-py3-none-any.whl |
Total release size: 208.7 kB
Release files / veriflow-0.4.2.tar.gz
| Download URL | veriflow-0.4.2.tar.gz |
|---|---|
| Size | 109.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7465810ed4a512074996b78e42d7e7ba41174b0b3fa012f58452ea36889a6f20
|
|
BLAKE2b-256 checksum How to use checksums |
eee8ee3d5b33534fed8098981b3b8016a2073d8b7d7caa3ae85e7c0520b20d44
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 12, 2026.
Transparency logRelease files / veriflow-0.4.2-py3-none-any.whl
| Download URL | veriflow-0.4.2-py3-none-any.whl |
|---|---|
| Size | 98.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2315b0314905836a132a48f589ce2f147cb4476fe06f1fae2282cd70a0a4cd8d
|
|
BLAKE2b-256 checksum How to use checksums |
26132c077f7c5ff7d1461f91091773b0a1b5ddaa502fbf4a040a069a6c428bdf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 12, 2026.
Transparency logSecurity for veriflow 0.4.2
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for veriflow-0.4.2.tar.gz
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 Nov 12, 2026.
Transparency logA 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.