Bin2cell
Visium HD captures gene expression data at a subcellular 2um resolution. It should be possible to use this data to reconstruct cells more accurately than just using the next resolution up (8um), especially if additionally using the available high resolution morphology images.
Bin2cell proposes 2um bin to cell groupings based on segmentation, which can be done on the morphology image and/or a visualisation of the gene expression. The package also corrects for a novel technical effect in the data stemming from variable bin dimensions. The end result is an object with cells, created from grouped 2um bins assigned to the same object after segmentation, carrying spatial information and sharper morphology images for visualisation. More details in the demo notebook.
Installation
pip install bin2cell
For b2c.stardist() to work, StarDist needs to be installed. Bin2cell comes with a dependency group to handle this:
pip install bin2cell[stardist]
Additionally, TensorFlow needs to be installed for StarDist to perform segmentation. The CPU version (installed via pip install tensorflow) should suffice for the scale of work performed here.
Usage and Documentation
Please refer to the demo notebook. Function docstrings are available on ReadTheDocs. An additional notebook comparing destriped and non-destriped expression data can be accessed here.
The repository also has notebooks comparing bin2cell output to standard 8um SpaceRanger output:
- Mouse brain bin2cell and downstream analysis
- Human colorectal cancer bin2cell and downstream analysis
Using bin2cell output from R
Write out your objects as .h5ads and use schard to read them.
Citation
Please cite our paper.
@article{polanski2024bin2cell,
title={Bin2cell reconstructs cells from high resolution Visium HD data},
author={Pola{\'n}ski, Krzysztof and Bartolom{\'e}-Casado, Raquel and Sarropoulos, Ioannis and Xu, Chuan and England, Nick and Jahnsen, Frode L and Teichmann, Sarah A and Yayon, Nadav},
journal={Bioinformatics},
volume={40},
number={9},
pages={btae546},
year={2024},
publisher={Oxford University Press}
}
Metadata
Release files for bin2cell 0.3.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bin2cell-0.3.5.tar.gz | 46.7 kB | Without provenance | Details for bin2cell-0.3.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bin2cell-0.3.5-py3-none-any.whl | Python 3 | none | any | Details for bin2cell-0.3.5-py3-none-any.whl |
Total release size: 94.0 kB
Release files / bin2cell-0.3.5.tar.gz
| Download URL | bin2cell-0.3.5.tar.gz |
|---|---|
| Size | 46.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4fcce16b385a41d81719d205c3e17dce74787c89c2d75d25bc9384c17bacafde
|
|
BLAKE2b-256 checksum How to use checksums |
8b9fdb2574b1e4dc50f2da4378340a7c55913282b9a00fb09e913285dc287e26
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.34.2
|
Release files / bin2cell-0.3.5-py3-none-any.whl
| Download URL | bin2cell-0.3.5-py3-none-any.whl |
|---|---|
| Size | 47.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c810dac55121579d3cdf975002db58b33df6729587e535b52be8cde189008f10
|
|
BLAKE2b-256 checksum How to use checksums |
83b95188869f8f58fc60071ddb82fbe04d4f09e863d70711890e8933789568f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.34.2
|
Security for bin2cell 0.3.5
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.