concordex 2.0.0
The goal of concordex is to identify spatial homogeneous regions (SHRs) as defined in the recent manuscript, “Identification of spatial homogenous regions in tissues with concordex”. Briefly, SHRs are are domains that are homogeneous with respect to cell type composition. concordex relies on the the k-nearest-neighbor (kNN) graph to representing similarities between cells and uses common clustering algorithms to identify SHRs.
Installation
concordex can be installed via pip
pip install concordex
.... and from Github
pip install git+https://github.com/pachterlab/concordex.git
Usage
After installing, concordex can be run as follows:
import scanpy as sc
from concordex.tools import calculate_concordex
ad = sc.datasets.pbmc68k_reduced()
# Compute concordex with discrete labels
calculate_concordex(ad, 'louvain', n_neighbors=10)
# Neighborhood consolidation information is stored in `adata.obsm`
ad.obsm['X_nbc'][:3]
# The column names are stored in `adata.uns`
ad.uns['nbc_params']['nbc_colnames']
Citation
If you’d like to use the concordex package in your research, please
cite our recent bioRxiv preprint:
Jackson, K.; Booeshaghi, A. S.; Gálvez-Merchán, Á.; Moses, L.; Chari, T.; Kim, A.; Pachter, L. Identification of spatial homogeneous regions in tissues with concordex. bioRxiv (Cold Spring Harbor Laboratory) 2023. https://doi.org/10.1101/2023.06.28.546949.
@article {Jackson2023.06.28.546949,
author = {Jackson, Kayla C. and Booeshaghi, A. Sina and G{'a}lvez-Merch{'a}n, {'A}ngel and Moses, Lambda and Chari, Tara and Kim, Alexandra and Pachter, Lior},
title = {Identification of spatial homogeneous regions in tissues with concordex},
year = {2024},
doi = {10.1101/2023.06.28.546949},
publisher = {Cold Spring Harbor Laboratory},
URL = {<https://www.biorxiv.org/content/early/2024/07/18/2023.06.28.546949>},
journal = {bioRxiv}
}
Maintainer
Metadata
Release files for concordex 2.0.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 | Provenance | Actions |
|---|---|---|---|---|
| concordex-2.0.0.tar.gz | 10.1 kB | Without provenance | Details for concordex-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| concordex-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for concordex-2.0.0-py3-none-any.whl |
Total release size: 19.8 kB
Release files / concordex-2.0.0.tar.gz
| Download URL | concordex-2.0.0.tar.gz |
|---|---|
| Size | 10.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d3d15dfb912de70a8505c072c28b0c9f87102c9ea64a12174c3ed24c249446d
|
|
BLAKE2b-256 checksum How to use checksums |
6a92a3929160b76ed5a3a14533fd7d169232d58565d34920cdd8f1ed3677b629
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Release files / concordex-2.0.0-py3-none-any.whl
| Download URL | concordex-2.0.0-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bd07da12725b49c04933bcf9df853f0479e9dfed097404e5330f5f43c420b3d3
|
|
BLAKE2b-256 checksum How to use checksums |
4d9fa7b7b4538199b1a5da902f50fdf49b8225908b01f1cc515cb8a2a14ec938
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Security for concordex 2.0.0
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.