scPDAC
scPDAC maps and annotates single-cell RNA-seq data against pancreatic ductal adenocarcinoma (PDAC) reference atlases. It ships pretrained models for human and mouse and exposes two complementary workflows:
- 🧬 Atlas mapping — project a query dataset into a reference SCANVI latent
space, either with scArches surgery (
scpdac.tl.extend_atlas, tolerates new batches and returns an expanded atlas) or a fast embed-only label transfer (scpdac.tl.embed_and_predict) — all while retaining your original metadata. - 🏷️ Hierarchical annotation — label cells with a 3-model hierarchical MLP
classifier (
scpdac.tl.predict_labels) that first splits Malignant vs Non-Malignant and then assigns fine-grained cell types with a dedicated sub-classifier for each branch.
Both paths align your genes to the model's panel automatically and write the
predictions straight back into your AnnData.
Getting started
Please refer to the documentation. The atlas mapping and hierarchical classifier tutorials walk through both workflows end-to-end, the performance page reports held-out benchmarks and known limitations, and the API documentation lists every public function.
Installation
You need to have Python 3.11 or newer installed on your system. If you don't have Python installed, we recommend installing uv.
- Install the latest release of
scPDACfrom PyPI:
pip install scPDAC
Release notes
See the changelog.
Contact
For questions and help requests, or to report a bug, please open an issue.
Citation
If you use scPDAC in your research, please cite:
Lucarelli D, Parikh S, Jiménez S, et al. Cross-species single-cell atlases chart progression, therapy-driven remodelling and immune evasion in pancreatic cancer. bioRxiv (2026). doi:10.64898/2026.03.19.712924
@article{Lucarelli2026,
author = {Lucarelli, Daniele and Parikh, Shrey and Jim{\'e}nez, Sara and others},
title = {Cross-species single-cell atlases chart progression, therapy-driven remodelling and immune evasion in pancreatic cancer},
journal = {bioRxiv},
year = {2026},
doi = {10.64898/2026.03.19.712924},
publisher = {Cold Spring Harbor Laboratory},
url = {https://www.biorxiv.org/content/10.1101/2026.03.19.712924},
}
Metadata
Release files for scpdac 0.1.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 | |
|---|---|---|---|
| scpdac-0.1.1.tar.gz | 59.8 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scpdac-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 108.1 MB
Release files / scpdac-0.1.1.tar.gz
| Download URL | scpdac-0.1.1.tar.gz |
|---|---|
| Size | 59.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5b4d840fd04b35e5bf27fd6ef81d4a0aa6b141b149a2c546190a046203dd9da3
|
|
BLAKE2b-256 checksum How to use checksums |
3471a01a41411c078396bad17b67726a06613694fec5ef8b844afaf5724039c7
|
| 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 28, 2026.
Transparency logRelease files / scpdac-0.1.1-py3-none-any.whl
| Download URL | scpdac-0.1.1-py3-none-any.whl |
|---|---|
| Size | 48.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e8557eabb452c075730395cb93c95661777e9167fcce32e9e4c007da2afd1965
|
|
BLAKE2b-256 checksum How to use checksums |
c1c833917146829395ebb74d704455193ec4c683451eb37589ad0602daac79e0
|
| 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 28, 2026.
Transparency log