recipe bioconductor-batchelor

Single-Cell Batch Correction Methods

Homepage:

https://bioconductor.org/packages/3.20/bioc/html/batchelor.html

License:

GPL-3

Recipe:

/bioconductor-batchelor/meta.yaml

Links:

biotools: batchelor

Implements a variety of methods for batch correction of single-cell (RNA sequencing) data. This includes methods based on detecting mutually nearest neighbors, as well as several efficient variants of linear regression of the log-expression values. Functions are also provided to perform global rescaling to remove differences in depth between batches, and to perform a principal components analysis that is robust to differences in the numbers of cells across batches.

package bioconductor-batchelor

(downloads) docker_bioconductor-batchelor

Versions:
1.26.0-01.22.0-01.18.0-11.18.0-01.16.0-01.14.0-11.14.0-01.10.0-21.10.0-1

1.26.0-01.22.0-01.18.0-11.18.0-01.16.0-01.14.0-11.14.0-01.10.0-21.10.0-11.10.0-01.8.0-01.6.2-01.6.0-01.4.0-01.2.1-01.0.1-0

Depends:
  • on bioconductor-beachmat >=2.26.0,<2.27.0

  • on bioconductor-beachmat >=2.26.0,<2.27.0a0

  • 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-biocsingular >=1.26.0,<1.27.0

  • on bioconductor-biocsingular >=1.26.1,<1.27.0a0

  • on bioconductor-delayedarray >=0.36.0,<0.37.0

  • on bioconductor-delayedarray >=0.36.0,<0.37.0a0

  • on bioconductor-delayedmatrixstats >=1.32.0,<1.33.0

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

  • on bioconductor-residualmatrix >=1.20.0,<1.21.0

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

  • on bioconductor-s4vectors >=0.48.0,<0.49.0

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

  • on bioconductor-scaledmatrix >=1.18.0,<1.19.0

  • on bioconductor-scaledmatrix >=1.18.0,<1.19.0a0

  • on bioconductor-scuttle >=1.20.0,<1.21.0

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

  • on bioconductor-singlecellexperiment >=1.32.0,<1.33.0

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

  • on bioconductor-sparsearray >=1.10.0,<1.11.0

  • on bioconductor-sparsearray >=1.10.8,<1.11.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-igraph

  • on r-matrix

  • on r-rcpp

Additional platforms:
linux-aarch64

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-batchelor

to add into an existing workspace instead, run:

pixi add bioconductor-batchelor

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-batchelor

Alternatively, to install into a new environment, run:

conda create -n envname bioconductor-batchelor

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-batchelor:<tag>

(see bioconductor-batchelor/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