Skip to content

Commit 88c15af

Browse files
committed
Add new core packages blog post
Signed-off-by: Lukas Heumos <lukas.heumos@posteo.net>
1 parent ce3a978 commit 88c15af

File tree

1 file changed

+74
-0
lines changed

1 file changed

+74
-0
lines changed

content/blog/2025-core-expansion.md

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
+++
2+
title = "New scverse Core Packages"
3+
date = 2025-07-15T00:00:05+01:00
4+
description = "scverse expands with new core packages."
5+
author = "Lukas Heumos"
6+
draft = false
7+
+++
8+
9+
# Four new core packages in scverse
10+
11+
We're happy to announce that four new packages have joined the scverse core ecosystem: [SnapATAC2](https://github.com/scverse/snapatac2), [rapids-singlecell](https://github.com/scverse/rapids_singlecell), [pertpy](https://github.com/scverse/pertpy), and [decoupler](https://github.com/scverse/decoupler).
12+
This broadens the scope of scverse beyond our so far supported modalities and brings in new functionality for epigenomics, perturbation screens, GPU acceleration, and functional inference.
13+
Each package is already built on top of our scverse core data structures and integrates with the broader scverse tooling.
14+
Single-cell analysis is evolving rapidly, with new experimental modalities and larger datasets becoming the norm.
15+
To keep up with this, we’re expanding scverse to support more domains, more data types, and more scalable computing backends.
16+
By bringing these mature, well-maintained tools into the core, we aim to provide a consistent and interoperable foundation across all stages of single-cell analysis.
17+
This helps you build richer workflows and helps developers avoid reinventing common infrastructure.
18+
19+
We're also welcoming the following lead maintainers to the scverse core team:
20+
- **Kai Zhang** for **snapatac2**
21+
- **Pau Badia i Mompel** for **decoupler**
22+
23+
## SnapATAC2
24+
25+
[SnapATAC2](https://github.com/scverse/snapatac2) enables fast, scalable analysis of single-cell ATAC-seq and related epigenomic data.
26+
Built in Rust with a Python front end, it handles millions of cells efficiently.
27+
The package offers preprocessing, dimensionality reduction, clustering, and visualization methods.
28+
All outputs are stored in AnnData and integrate seamlessly with scanpy and other scverse frameworks.
29+
30+
## rapids-singlecell
31+
32+
[rapids-singlecell](https://github.com/scverse/rapids_singlecell) accelerates single-cell workflows using NVIDIA’s RAPIDS libraries.
33+
Key steps like PCA, neighborhood graph construction, and clustering run on GPU via cuML and cuGraph.
34+
Functions follow AnnData conventions and can directly replace scanpy or sklearn-based code.
35+
This enables practical analysis of massive datasets that would be too slow on CPU.
36+
37+
For more details, we refer to a recent blog post by NVIDIA: [Driving Toward Billion-Cell Analysis and Biological Breakthroughs with RAPIDS-singlecell](https://developer.nvidia.com/blog/driving-toward-billion-cell-analysis-and-biological-breakthroughs-with-rapids-singlecell)
38+
39+
## pertpy
40+
41+
[pertpy](https://github.com/scverse/pertpy) focuses on single-cell perturbation screens, including CRISPR and compound treatments.
42+
It supports differential analysis, signature scoring, and dose-response modeling.
43+
Metadata handling and visualization are tailored for perturbation-specific use cases.
44+
Built on AnnData and scverse libraries, pertpy fits smoothly into existing pipelines.
45+
46+
## decoupler
47+
48+
[decoupler](https://github.com/scverse/decoupler) enables inference biological activity from omics data using prior knowledge resources.
49+
Compatible with transcriptomics and proteomics, it links data to transcription factors, pathways, or kinases.
50+
It includes multiple inference methods such as enrichment scoring and linear models.
51+
Designed for both bulk and single-cell, decoupler works directly with our scverse core data structures.
52+
53+
## What this means
54+
55+
We're continuing to support a modular but coherent ecosystem where high-quality tools can interoperate.
56+
These additions bring coverage of new data types and analysis goals while staying within the same technical foundations.
57+
All packages use our scverse core data structures, follow shared conventions, and benefit from a growing set of shared infrastructure and community practices.
58+
We aim to keep development decentralized and open while improving alignment across projects.
59+
60+
## Get involved
61+
62+
If you're building something new, we'd love to have your work be a part of the [scverse ecosystem](https://github.com/scverse/ecosystem-packages).
63+
If you're our tools, please share feedback or ideas via the respective issue trackers.
64+
The best places to start are [scverse.org](https://scverse.org), [github.com/scverse](https://github.com/scverse), and our [scverse zulip chat](https://scverse.zulipchat.com/).
65+
We're always looking for more contributors to our packages but especially also for community related work.
66+
Please reach out!
67+
68+
## Thank you
69+
70+
We’re grateful to the maintainers of these packages for their work and commitment to open, reusable tools.
71+
Their contributions help make the scverse ecosystem more useful, inclusive, and sustainable.
72+
We’re also thankful to the community for using, testing, and contributing to these tools — your feedback drives everything we do.
73+
74+
*— The scverse core team*

0 commit comments

Comments
 (0)