An interactive explorer for single-cell lineage tracing.
CELLxLINEAGE is a fork of CELLxGENE extended to support TreeData objects and lineage tree visualization alongside the standard UMAP embedding.
Installation
You need to have Python 3.10 or newer installed on your system. If you don't have Python installed, we recommend installing Mambaforge.
Install the latest release of cellxlineage from PyPI:
pip install cellxlineage
Usage
# Launch with a TreeData file
cellxlineage launch data.h5td
CELLxGENE documentation
CELLxLINEAGE inherits all standard CELLxGENE Annotate features. For documentation on exploration, filtering, differential expression, and annotations, see the CELLxGENE Annotate documentation.
Hosting
CELLxLINEAGE can be hosted for a small group (≈10 concurrent users) to explore
one shared dataset. Add --ephemeral-annotations:
cellxlineage launch data.h5td --host 0.0.0.0 --port 5005 --ephemeral-annotations
In this mode:
- No "user generated data directory" prompt. Custom annotations and gene sets are kept in memory, per browser session, and never written to disk.
- Annotations reset on reload and are isolated between users — reloading the page or a new visitor starts from a clean slate. Differential expression is already per-session and resets the same way.
Notes:
- Run as a single process — the in-memory annotations and lineage caches live
in that process, so multiple workers would not share them. The built-in
threaded server is fine for a small trusted group; to harden it, put it behind a
reverse proxy (e.g. nginx) and, if you want a production WSGI server, run
gunicorn with
--workers 1 --threads N. - Do not pass
--backedin this mode (rejected at startup): concurrent reads on a single shared file handle are unsafe. The default in-memory data load is what you want. - A heavy differential-expression or ancestral-linkage request briefly occupies the process; at this scale that is acceptable.
Contact
For questions and bug reports please use the issue tracker.
License
MIT — see LICENSE. Portions copyright Chan Zuckerberg Initiative; lineage extensions copyright William Colgan.
Metadata
Release files for cellxlineage 0.3.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 | |
|---|---|---|---|
| cellxlineage-0.3.1.tar.gz | 3.7 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cellxlineage-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.4 MB
Release files / cellxlineage-0.3.1.tar.gz
| Download URL | cellxlineage-0.3.1.tar.gz |
|---|---|
| Size | 3.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
34fecc56f1c5b2ad52c8f88bdf6ae3a184f209a0fdf557fb988c2fb650eedd15
|
|
BLAKE2b-256 checksum How to use checksums |
8ce1fbb6f0e6f936d9e8c0544b426da5b90996e2ae568ba8e0ac2343abf3dc39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 29, 2026.
Transparency logRelease files / cellxlineage-0.3.1-py3-none-any.whl
| Download URL | cellxlineage-0.3.1-py3-none-any.whl |
|---|---|
| Size | 3.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
19060f73fcb7dbb49f87c78a76ff3648a15276a18517f8a9374c69dde2344595
|
|
BLAKE2b-256 checksum How to use checksums |
b491cb03a7a5af1c3976efcf98f34cd6526f05895e2e97dabd4a4db8d71d4781
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 29, 2026.
Transparency log