Zoo-WES-Runner
This repository is a plugin for the ZOO-Project, which allows it submit jobs to a Workflow Execution Service (WES). This allows the ZOO-Project to submit jobs to run in a number of different environments.
This work is undertaken as part of the deployment of the EOEPCA on JASMIN.
It has been developed using the EOEPCA ADES connected to the TOIL workflow engine running workflows using singularity in a SLURM cluster. However, the TOIL WES server supports many other configurations, such as support for a number of batch systems (Grid Engine, Torque and LSF), cloud platforms, local execution on the server, etc. It should be possible to use this module with any configuration in which TOIL can run workflows, or indeed a different WES server other than TOIL. However, these configurations have not been tested.
This documentation is split into a number of parts:
- Configuring the TOIL server on a SLURM headnode.
- Configuring EOEPCA to use the TOIL server.
- Submitting jobs and debugging.
Metadata
Release files for zoo-wes-runner 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| zoo_wes_runner-0.2.1.tar.gz | 61.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zoo_wes_runner-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 70.5 kB
Release files / zoo_wes_runner-0.2.1.tar.gz
| Download URL | zoo_wes_runner-0.2.1.tar.gz |
|---|---|
| Size | 61.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
da654809c337c9900da5552ea04023d3474f89a3ad5f0ab97f979c40d483b47c
|
|
BLAKE2b-256 checksum How to use checksums |
9c94d009cf3292fbb2fc5b58d77f5da2f0cf15c1e96b42934f4340b114e4db59
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 27, 2026.
Transparency logRelease files / zoo_wes_runner-0.2.1-py3-none-any.whl
| Download URL | zoo_wes_runner-0.2.1-py3-none-any.whl |
|---|---|
| Size | 8.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a92a79b8674bb9b854e11cf527f0060d4c21387e8acc2a52d238c8dff56d33d6
|
|
BLAKE2b-256 checksum How to use checksums |
d5a1689af9627546b661fac1a7d78d620eb2cf5f4cf507f450394c7ab0b197cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 27, 2026.
Transparency log
