Metalcyte
Single-cell RNA-seq analysis of atlas-sized datasets on an Apple silicon laptop.
Metalcyte runs the standard single-cell RNA-seq analysis, from raw counts to clusters and marker genes, on a Mac with an Apple M-series chip. You call it from Python, and it stores its results in an AnnData object, the standard data format for single-cell data in Python. The calculations run in Rust, a compiled programming language, and use all parts of the chip:
- all CPU cores at once,
- the chip's matrix unit, which multiplies matrices quickly, through Apple's Accelerate maths library,
- the graphics processor (GPU), through small programs written for Apple's Metal interface.
On Apple silicon the CPU and the GPU share one pool of memory, so Metalcyte does not copy the data between them. Metalcyte can also analyse datasets that are too large to fit in the computer's memory. It reads the count matrix from disk in blocks, keeping only one block in memory at a time.
The complete survey of human embryonic development, 4 062 980 cells by 45 676 genes. Metalcyte took it from raw counts to clusters in 9 minutes on a laptop with 18 GB of memory.
Main results
- Fast. A bone-marrow atlas of 117 308 cells goes from counts to marker genes in 12 s.
- Low memory use. A million cells fit within 18 GB of memory. The 4 million cells above used about 9 GB at most.
- Low energy use. The analysis of those 117 308 cells uses 168 J of energy.
- Tested. Each algorithm has a test that checks its numerical output against a reference result and states the tolerance.
- Standard data format. Results are stored in the usual places of the AnnData object, so other Python tools for single-cell data can read them.
Features
Preprocessing. Quality-control metrics, filtering of cells and genes, normalisation to the same total count per cell, log and square-root transforms, selection of highly variable genes (Seurat and Cell Ranger methods), scaling, and principal component analysis (PCA) on the GPU.
Datasets larger than memory. Quality control, normalisation, selection of variable genes, scaling and PCA work on an h5ad file on disk. Metalcyte reads the file four times from start to end and never loads the whole matrix.
Batch correction and integration. Removal of unwanted variation, such as differences in total counts per cell
(regress_out), ComBat, and Harmony integration, all running on every CPU core.
Neighbour graphs. For each cell, Metalcyte finds its most similar cells. Up to 200 000 cells it compares every pair of cells on the GPU (exact search). Above that size it uses NN-descent, a faster method that finds almost all of the true neighbours (approximate search). It picks the method from the number of cells.
Embeddings. Two-dimensional maps of the cells for plotting: UMAP, computed on several cores in parallel, and t-SNE, with a fast approximation on the GPU for large datasets (FIt-SNE). Also diffusion maps, force-directed layouts and PAGA.
Clustering and trajectories. Leiden and Louvain clustering of the neighbour graph, diffusion pseudotime, and dendrograms of clusters.
Marker genes. Wilcoxon rank-sum, t-test and logistic-regression tests for genes that distinguish clusters. A Wilcoxon test that reads the counts from disk, for datasets larger than memory. Overlap between marker lists, and scoring of gene sets and cell-cycle phase.
Spatial and clustering metrics. Moran's I, Geary's C, modularity and confusion matrices.
Plotting. Scatter plots of embeddings. The GPU draws the points, so a plot of millions of cells takes about a second.
The full reference is in docs/API.md.
Installation
On a Mac with Apple silicon (macOS 13 or later) and Python 3.11 to 3.13:
pip install metalcyte
pip install "metalcyte[plot]" # with matplotlib for plotting
The package comes ready to run, so you do not need Rust or Xcode. To build it yourself from the source code, see docs/INSTALL.md.
Quick start
import anndata as ad
import metalcyte as mc
adata = ad.read_h5ad("counts.h5ad") # raw counts, cells by genes
mc.pp.filter_cells(adata, min_genes=200)
mc.pp.filter_genes(adata, min_cells=3)
mc.pp.normalize_total(adata, target_sum=1e4)
mc.pp.log1p(adata)
mc.pp.highly_variable_genes(adata, n_top_genes=2000)
adata = adata[:, adata.var["highly_variable"].to_numpy()].copy()
mc.pp.scale(adata, max_value=10)
mc.pp.pca(adata, n_comps=50)
mc.pp.neighbors(adata, n_neighbors=15)
mc.tl.umap(adata, parallel=True)
mc.tl.leiden(adata)
mc.tl.rank_genes_groups(adata, "leiden", method="wilcoxon")
mc.pl.umap(adata, color="leiden")
If the dataset is larger than memory, give Metalcyte the path of the counts file on disk:
adata = mc.pp.preprocess_backed("atlas_counts.h5ad", n_top_genes=2000, n_comps=50)
mc.pp.neighbors(adata)
mc.tl.umap(adata, parallel=True)
mc.tl.leiden(adata)
A step-by-step tutorial is in docs/tutorials/pbmc3k_clustering.ipynb.
Benchmarks
All timings come from an Apple M3 Pro laptop with 18 GB of memory. The methods are described in docs/PERFORMANCE.md.
| Dataset | Cells | Time | Memory |
|---|---|---|---|
| Bone marrow, counts to marker genes | 117 308 | 12 s | |
| Human embryo, counts to clusters | 1 001 288 | 103 s | under 1.5 GB per step |
| Human embryo, full survey, counts to clusters | 4 062 980 | 538 s | about 9 GB at peak |
| Energy | Cells | Time | Energy |
|---|---|---|---|
| Bone marrow, counts to marker genes | 117 308 | 13 s | 168 J |
| Human embryo, full survey, counts to clusters | 4 062 980 | 557 s | 6.2 kJ |
Energy is the extra power drawn by the chip during the run, measured every 100 ms with the power monitor of macOS, with the idle power subtracted.
Documentation
- Installation
- API reference
- Performance and methodology
- Validation
- How it works and architecture
- Changelog
Citation
If you use Metalcyte in your research, please cite it as described in CITATION.cff. A manuscript is in preparation.
Contributing
Bug reports and feature requests are welcome in the issue tracker. See CONTRIBUTING.md for the development setup.
License
Metalcyte is released under the MIT License.
Metadata
Release files for metalcyte 0.3.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 | |
|---|---|---|---|
| metalcyte-0.3.0.tar.gz | 396.3 kB | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| metalcyte-0.3.0-cp313-cp313-macosx_11_0_arm64.whl | CPython 3.13 | CPython 3.13 | macOS 11.0+ ARM64 | Details |
| metalcyte-0.3.0-cp312-cp312-macosx_11_0_arm64.whl | CPython 3.12 | CPython 3.12 | macOS 11.0+ ARM64 | Details |
| metalcyte-0.3.0-cp311-cp311-macosx_11_0_arm64.whl | CPython 3.11 | CPython 3.11 | macOS 11.0+ ARM64 | Details |
Total release size: 5.8 MB
Release files / metalcyte-0.3.0.tar.gz
| Download URL | metalcyte-0.3.0.tar.gz |
|---|---|
| Size | 396.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6e9d1d95d7e963313b8fc71b42889fc358e010d9c484364c76b96455ca53c89f
|
|
BLAKE2b-256 checksum How to use checksums |
75f40934b860e186b22009ddb817071ea6b6447cd64dbe27682e91d5211623bc
|
| 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 Oct 7, 2026.
Transparency logRelease files / metalcyte-0.3.0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | metalcyte-0.3.0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
54218bc75bcd8840ab2f175ec544debd3eda84e4ddde14a608ef71172aa0170d
|
|
BLAKE2b-256 checksum How to use checksums |
371e72b853ffbf2322470c5cb325489234f691ff715b15d88e3afbdc62dafcab
|
| 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 Oct 7, 2026.
Transparency logRelease files / metalcyte-0.3.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | metalcyte-0.3.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
60c234b1ae41c28814cb1249a0247a08f9e5c7ee29974b77cb0e9cae53576707
|
|
BLAKE2b-256 checksum How to use checksums |
bacbb8438c930f408e50b82a8665b9c865c15f89f71b72dff7653d56d4b45c66
|
| 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 Oct 7, 2026.
Transparency logRelease files / metalcyte-0.3.0-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | metalcyte-0.3.0-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
ff8bf5a22339fb85c5c543b58a7bec4ac9a33e111aa728476fb771b8ec58ba86
|
|
BLAKE2b-256 checksum How to use checksums |
6f8edb1fb4f4341c51c261bd5f90ac2da578f995353f8af160bcbb6b51a7a9ef
|
| 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 Oct 7, 2026.
Transparency log