- recipe bioconductor-cn.mops
cn.mops - Mixture of Poissons for CNV detection in NGS data
- Homepage:
https://bioconductor.org/packages/3.20/bioc/html/cn.mops.html
- License:
LGPL (>= 2.0)
- Recipe:
- Links:
biotools: cn.mops
cn.mops (Copy Number estimation by a Mixture Of PoissonS) is a data processing pipeline for copy number variations and aberrations (CNVs and CNAs) from next generation sequencing (NGS) data. The package supplies functions to convert BAM files into read count matrices or genomic ranges objects, which are the input objects for cn.mops. cn.mops models the depths of coverage across samples at each genomic position. Therefore, it does not suffer from read count biases along chromosomes. Using a Bayesian approach, cn.mops decomposes read variations across samples into integer copy numbers and noise by its mixture components and Poisson distributions, respectively. cn.mops guarantees a low FDR because wrong detections are indicated by high noise and filtered out. cn.mops is very fast and written in C++.
- package bioconductor-cn.mops¶
-
- Versions:
1.56.0-0,1.52.0-1,1.52.0-0,1.48.0-0,1.46.0-0,1.44.0-1,1.44.0-0,1.40.0-2,1.40.0-1,1.56.0-0,1.52.0-1,1.52.0-0,1.48.0-0,1.46.0-0,1.44.0-1,1.44.0-0,1.40.0-2,1.40.0-1,1.40.0-0,1.38.0-0,1.36.0-1,1.36.0-0,1.34.0-0,1.32.0-0,1.30.0-1,1.28.0-0,1.26.0-0,1.24.0-0,1.22.0-0,1.18.0-1,1.18.0-0,1.16.2-0- Depends:
on bioconductor-biobase
>=2.70.0,<2.71.0on bioconductor-biobase
>=2.70.0,<2.71.0a0on bioconductor-biocgenerics
>=0.56.0,<0.57.0on bioconductor-biocgenerics
>=0.56.0,<0.57.0a0on bioconductor-genomicranges
>=1.62.0,<1.63.0on bioconductor-genomicranges
>=1.62.1,<1.63.0a0on bioconductor-iranges
>=2.44.0,<2.45.0on bioconductor-iranges
>=2.44.0,<2.45.0a0on bioconductor-rsamtools
>=2.26.0,<2.27.0on bioconductor-rsamtools
>=2.26.0,<2.27.0a0on bioconductor-s4vectors
>=0.48.0,<0.49.0on bioconductor-s4vectors
>=0.48.0,<0.49.0a0on bioconductor-seqinfo
>=1.0.0,<1.1.0on bioconductor-seqinfo
>=1.0.0,<1.1.0a0on libblas
>=3.9.0,<4.0a0on libgcc
>=14on liblapack
>=3.9.0,<4.0a0on liblzma
>=5.8.2,<6.0a0on libstdcxx
>=14on libzlib
>=1.3.1,<2.0a0on r-base
>=4.5,<4.6.0a0
- 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-cn.mops
to add into an existing workspace instead, run:
pixi add bioconductor-cn.mops
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-cn.mops
Alternatively, to install into a new environment, run:
conda create -n envname bioconductor-cn.mops
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-cn.mops:<tag>
(see bioconductor-cn.mops/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 badge with the following MarkDown:
[](http://bioconda.github.io/recipes/bioconductor-cn.mops/README.html)