ahcore
ahcore is the AI for Oncology core toolkit for computational-pathology pipelines: the reusable building
blocks that sit between whole-slide images and a training run. It is a pure-Python library, meant to be
composed inside a larger pipeline rather than run on its own.
This repository is automatically synced from the AI for Oncology monorepo.
What ahcore offers
ahcore is a toolkit of composable building blocks for whole-slide-image deep learning, not an end-to-end
application. A consumer pipeline assembles these pieces and owns the experiment logic. It decides how data
is split, whether to cross-validate, and how runs are orchestrated. ahcore provides the parts.
- A data catalog. A SQLAlchemy-backed manifest of patients, slides, masks, labels, and named splits,
queried through a
DataManager.ahcorestores and serves splits (e.g. fit/validate/test membership, or membership supplied in memory). How you draw them is up to you. - Views and adapters. Lazy per-slide and per-tile accessors over the catalog, plus an adapter seam
(
view → AdapterBundle) that turns them into named, model-ready tensors. Ships adapters for foundation-model tile features, patient labels, bulk RNA expression, and image+mask pairs. Adapters are the main extension point. - Feature extraction and caching. Run a packaged foundation-model encoder over a slide's tiles and persist the per-slide features to HDF5, keyed deterministically. This is a distinct precompute step: at training time the feature adapters read from that cache, they do not extract on the fly (doing so would be too slow for a realistic training run).
- Datamodules and models. PyTorch Lightning datamodules that assemble batches from adapters (single- or multi-modal), plus model heads: attention-based MIL (ABMIL), mean-pool MIL (MeanMIL), encoders, a concatenation fusion head, and segmentation wrappers.
- Task and training scaffolding. A
Taskprotocol (choose inputs and targets, compute loss and metrics) and a thinMultiModalLightningModulethat runs training/validation/test by delegating to the task. You supply the concrete tasks. - Slide-sized raster I/O. Stream model outputs (segmentation masks, attention or probability maps) tile-by-tile into a chunked Zarr store, then read arbitrary regions back like a slide, to stitch, overlay, or export to a pyramidal TIFF.
- Transforms and augmentations. Tile transforms (including polygon-to-mask) and feature-space augmentations.
ahcore ships no end-to-end command-line application; it is a library.
Installation
pip install ahcore
Requires Python ≥ 3.11. The training stack (PyTorch Lightning) is a core dependency. ahcore is a
training-scaffolding library, not an optional add-on.
Manifests that read slides with OpenSlide (reader OPENSLIDE) need dlup's OpenSlide backend:
pip install "ahcore[openslide]"
Development
ahcore is developed in the AI for Oncology monorepo and synced to this repository. To work on it here,
standalone:
pip install -e ".[dev]"
pytest
Inside the monorepo it is built and tested with Bazel (bazelisk test //aifo/ahcore/tests/...).
License
Apache 2.0 — see LICENSE.
Metadata
Release files for ahcore 0.2.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 | |
|---|---|---|---|
| ahcore-0.2.0.tar.gz | 114.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ahcore-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 249.8 kB
Release files / ahcore-0.2.0.tar.gz
| Download URL | ahcore-0.2.0.tar.gz |
|---|---|
| Size | 114.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5a3c2449cf581cd9f4e90b04542a4072c2df29b490c1d596cc3d683153e3acf3
|
|
BLAKE2b-256 checksum How to use checksums |
6028e7e7aba5a892542b25eb84b9e4bb3aed41325061816045da1f447778a602
|
| 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 16, 2026.
Transparency logRelease files / ahcore-0.2.0-py3-none-any.whl
| Download URL | ahcore-0.2.0-py3-none-any.whl |
|---|---|
| Size | 135.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cda294da0b5e4df77405472f0498da341cb75f9dc818c5a0cfef0d6fae03fc41
|
|
BLAKE2b-256 checksum How to use checksums |
dd88ab9b0457723daad94ee550a4557ad502ee8670a4e958781765671e7577fc
|
| 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 16, 2026.
Transparency log