recipe bioconductor-consensus

Cross-platform consensus analysis of genomic measurements via interlaboratory testing method

Homepage:

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

License:

BSD_3_clause + file LICENSE

Recipe:

/bioconductor-consensus/meta.yaml

An implementation of the American Society for Testing and Materials (ASTM) Standard E691 for interlaboratory testing procedures, designed for cross-platform genomic measurements. Given three (3) or more genomic platforms or laboratory protocols, this package provides interlaboratory testing procedures giving per-locus comparisons for sensitivity and precision between platforms.

package bioconductor-consensus

(downloads) docker_bioconductor-consensus

Versions:
1.28.0-0,  1.24.0-0,  1.20.0-1,  1.20.0-0,  1.18.0-0,  1.16.0-0,  1.12.0-0,  1.10.0-0,  1.8.0-1, 

1.28.0-0,  1.24.0-0,  1.20.0-1,  1.20.0-0,  1.18.0-0,  1.16.0-0,  1.12.0-0,  1.10.0-0,  1.8.0-1,  1.8.0-0,  1.6.0-0,  1.4.0-0,  1.2.2-0,  1.2.0-0,  1.0.2-0

Depends:

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

  • on r-gplots

  • on r-matrixstats

  • on r-rcolorbrewer

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

to add into an existing workspace instead, run:

pixi add bioconductor-consensus

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

Alternatively, to install into a new environment, run:

conda create -n envname bioconductor-consensus

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

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

Link to this page

Render an install-with-bioconda badge with the following MarkDown:

[![install with bioconda](https://img.shields.io/badge/install%20with-bioconda-brightgreen.svg?style=flat)](http://bioconda.github.io/recipes/bioconductor-consensus/README.html)