recipe bioconductor-svp

Predicting cell states and their variability in single-cell or spatial omics data

Homepage:

https://bioconductor.org/packages/3.22/bioc/html/SVP.html

License:

GPL-3

Recipe:

/bioconductor-svp/meta.yaml

SVP uses the distance between cells and cells, features and features, cells and features in the space of MCA to build nearest neighbor graph, then uses random walk with restart algorithm to calculate the activity score of gene sets (such as cell marker genes, kegg pathway, go ontology, gene modules, transcription factor or miRNA target sets, reactome pathway, …), which is then further weighted using the hypergeometric test results from the original expression matrix. To detect the spatially or single cell variable gene sets or (other features) and the spatial colocalization between the features accurately, SVP provides some global and local spatial autocorrelation method to identify the spatial variable features. SVP is developed based on SingleCellExperiment class, which can be interoperable with the existing computing ecosystem.

package bioconductor-svp

(downloads) docker_bioconductor-svp

Versions:

1.2.1-0

Depends:
  • on bioconductor-biocgenerics >=0.56.0,<0.57.0

  • on bioconductor-biocgenerics >=0.56.0,<0.57.0a0

  • on bioconductor-biocneighbors >=2.4.0,<2.5.0

  • on bioconductor-biocneighbors >=2.4.0,<2.5.0a0

  • on bioconductor-biocparallel >=1.44.0,<1.45.0

  • on bioconductor-biocparallel >=1.44.0,<1.45.0a0

  • on bioconductor-delayedmatrixstats >=1.32.0,<1.33.0

  • on bioconductor-delayedmatrixstats >=1.32.0,<1.33.0a0

  • on bioconductor-ggtree >=4.0.0,<4.1.0

  • on bioconductor-ggtree >=4.0.4,<4.1.0a0

  • on bioconductor-s4vectors >=0.48.0,<0.49.0

  • on bioconductor-s4vectors >=0.48.0,<0.49.0a0

  • on bioconductor-singlecellexperiment >=1.32.0,<1.33.0

  • on bioconductor-singlecellexperiment >=1.32.0,<1.33.0a0

  • on bioconductor-spatialexperiment >=1.20.0,<1.21.0

  • on bioconductor-spatialexperiment >=1.20.0,<1.21.0a0

  • on bioconductor-summarizedexperiment >=1.40.0,<1.41.0

  • on bioconductor-summarizedexperiment >=1.40.0,<1.41.0a0

  • on libblas >=3.9.0,<4.0a0

  • on libgcc >=14

  • on liblapack >=3.9.0,<4.0a0

  • on liblzma >=5.8.2,<6.0a0

  • on libstdcxx >=14

  • on libzlib >=1.3.1,<2.0a0

  • on r-base >=4.5,<4.6.0a0

  • on r-cli

  • on r-deldir

  • on r-dplyr

  • on r-dqrng

  • on r-fastmatch

  • on r-ggfun

  • on r-ggplot2

  • on r-ggstar

  • on r-matrix

  • on r-pracma

  • on r-rcpp

  • on r-rcpparmadillo >=14.0

  • on r-rcppeigen

  • on r-rcppparallel

  • on r-rlang

  • on r-withr

  • on tbb-devel >=2022.3.0,<2022.4.0a0

Additional platforms:

Installation

You need a conda-compatible package manager (currently either pixi, conda, or micromamba) and the Bioconda channel already activated (see Usage). Below, we show how to install with either pixi or conda (for micromamba and mamba, commands are essentially the same as with conda).

Pixi

With pixi installed and the Bioconda channel set up (see Usage), to install globally, run:

pixi global install bioconductor-svp

to add into an existing workspace instead, run:

pixi add bioconductor-svp

In the latter case, make sure to first add bioconda and conda-forge to the channels considered by the workspace:

pixi workspace channel add conda-forge
pixi workspace channel add bioconda

Conda

With conda installed and the Bioconda channel set up (see Usage), to install into an existing and activated environment, run:

conda install bioconductor-svp

Alternatively, to install into a new environment, run:

conda create -n envname bioconductor-svp

with envname being the name of the desired environment.

Container

Alternatively, every Bioconda package is available as a container image for usage with your preferred container runtime. For e.g. docker, run:

docker pull quay.io/biocontainers/bioconductor-svp:<tag>

(see bioconductor-svp/tags for valid values for <tag>).

Integrated deployment

Finally, note that many scientific workflow management systems directly integrate both conda and container based software deployment. Thus, workflow steps can be often directly annotated to use the package, leading to automatic deployment by the respective workflow management system, thereby improving reproducibility and transparency. Check the documentation of your workflow management system to find out about the integration.

Download stats