:orphan: .. only available via index, not via toctree .. title:: Package Recipe 'bioconductor-cn.mops' .. highlight: bash bioconductor-cn.mops ==================== .. conda:recipe:: bioconductor-cn.mops :replaces_section_title: :noindex: cn.mops \- Mixture of Poissons for CNV detection in NGS data :homepage: https://bioconductor.org/packages/3.22/bioc/html/cn.mops.html :license: LGPL (>= 2.0) :recipe: /`bioconductor-cn.mops `_/`meta.yaml `_ :links: biotools: :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\+\+. .. conda:package:: bioconductor-cn.mops |downloads_bioconductor-cn.mops| |docker_bioconductor-cn.mops| :versions: .. raw:: html
1.56.0-01.52.0-11.52.0-01.48.0-01.46.0-01.44.0-11.44.0-01.40.0-21.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`` .. raw:: html
:depends on bioconductor-biobase: ``>=2.70.0,<2.71.0`` :depends on bioconductor-biobase: ``>=2.70.0,<2.71.0a0`` :depends on bioconductor-biocgenerics: ``>=0.56.0,<0.57.0`` :depends on bioconductor-biocgenerics: ``>=0.56.0,<0.57.0a0`` :depends on bioconductor-genomicranges: ``>=1.62.0,<1.63.0`` :depends on bioconductor-genomicranges: ``>=1.62.1,<1.63.0a0`` :depends on bioconductor-iranges: ``>=2.44.0,<2.45.0`` :depends on bioconductor-iranges: ``>=2.44.0,<2.45.0a0`` :depends on bioconductor-rsamtools: ``>=2.26.0,<2.27.0`` :depends on bioconductor-rsamtools: ``>=2.26.0,<2.27.0a0`` :depends on bioconductor-s4vectors: ``>=0.48.0,<0.49.0`` :depends on bioconductor-s4vectors: ``>=0.48.0,<0.49.0a0`` :depends on bioconductor-seqinfo: ``>=1.0.0,<1.1.0`` :depends on bioconductor-seqinfo: ``>=1.0.0,<1.1.0a0`` :depends on libblas: ``>=3.9.0,<4.0a0`` :depends on libgcc: ``>=14`` :depends on liblapack: ``>=3.9.0,<4.0a0`` :depends on liblzma: ``>=5.8.2,<6.0a0`` :depends on libstdcxx: ``>=14`` :depends on libzlib: ``>=1.3.1,<2.0a0`` :depends on r-base: ``>=4.5,<4.6.0a0`` :additional platforms: .. raw:: html linux-aarch64 Installation ------------ You need a conda-compatible package manager (currently either `pixi `__, `conda `__, or `micromamba `__) and the Bioconda channel already activated (see :ref:`bioconda_setup`). 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 :ref:`bioconda_setup`), 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 :ref:`bioconda_setup`), 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: (see `bioconductor-cn.mops/tags`_ for valid values for ````). 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. .. _conda: https://conda.io .. _pixi: https://pixi.sh .. |downloads_bioconductor-cn.mops| image:: https://img.shields.io/conda/dn/bioconda/bioconductor-cn.mops.svg?style=flat :target: https://anaconda.org/bioconda/bioconductor-cn.mops :alt: (downloads) .. |docker_bioconductor-cn.mops| image:: https://quay.io/repository/biocontainers/bioconductor-cn.mops/status :target: https://quay.io/repository/biocontainers/bioconductor-cn.mops .. _`bioconductor-cn.mops/tags`: https://quay.io/repository/biocontainers/bioconductor-cn.mops?tab=tags .. raw:: html Download stats ----------------- .. raw:: html :file: ../../templates/package_dashboard.html 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-cn.mops/README.html) .. |install-with-bioconda| image:: https://img.shields.io/badge/install%20with-bioconda-brightgreen.svg?style=flat :target: http://bioconda.github.io/recipes/bioconductor-cn.mops/README.html