:orphan: .. only available via index, not via toctree .. title:: Package Recipe 'bioconductor-mnem' .. highlight: bash bioconductor-mnem ================= .. conda:recipe:: bioconductor-mnem :replaces_section_title: :noindex: Mixture Nested Effects Models :homepage: https://bioconductor.org/packages/3.20/bioc/html/mnem.html :license: GPL-3 :recipe: /`bioconductor-mnem `_/`meta.yaml `_ :links: biotools: :biotools:`mnem` Mixture Nested Effects Models \(mnem\) is an extension of Nested Effects Models and allows for the analysis of single cell perturbation data provided by methods like Perturb\-Seq \(Dixit et al.\, 2016\) or Crop\-Seq \(Datlinger et al.\, 2017\). In those experiments each of many cells is perturbed by a knock\-down of a specific gene\, i.e. several cells are perturbed by a knock\-down of gene A\, several by a knock\-down of gene B\, ... and so forth. The observed read\-out has to be multi\-trait and in the case of the Perturb\-\/Crop\-Seq gene are expression profiles for each cell. mnem uses a mixture model to simultaneously cluster the cell population into k clusters and and infer k networks causally linking the perturbed genes for each cluster. The mixture components are inferred via an expectation maximization algorithm. .. conda:package:: bioconductor-mnem |downloads_bioconductor-mnem| |docker_bioconductor-mnem| :versions: .. raw:: html
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-0``,  ``1.22.0-0``,  ``1.18.0-1``,  ``1.18.0-0``,  ``1.16.0-0``,  ``1.14.0-1``,  ``1.14.0-0``,  ``1.10.0-2``,  ``1.10.0-1``,  ``1.10.0-0``,  ``1.8.0-0``,  ``1.6.5-0``,  ``1.6.1-0``,  ``1.4.0-0`` .. raw:: html
:depends on bioconductor-graph: ``>=1.88.0,<1.89.0`` :depends on bioconductor-graph: ``>=1.88.1,<1.89.0a0`` :depends on bioconductor-linnorm: ``>=2.34.0,<2.35.0`` :depends on bioconductor-linnorm: ``>=2.34.0,<2.35.0a0`` :depends on bioconductor-rgraphviz: ``>=2.54.0,<2.55.0`` :depends on bioconductor-rgraphviz: ``>=2.54.0,<2.55.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`` :depends on r-cluster: :depends on r-data.table: :depends on r-e1071: :depends on r-flexclust: :depends on r-ggplot2: :depends on r-lattice: :depends on r-matrixstats: :depends on r-naturalsort: :depends on r-rcpp: :depends on r-rcppeigen: :depends on r-snowfall: :depends on r-tsne: :depends on r-wesanderson: :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-mnem to add into an existing workspace instead, run:: pixi add bioconductor-mnem 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-mnem Alternatively, to install into a new environment, run:: conda create -n envname bioconductor-mnem 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-mnem: (see `bioconductor-mnem/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-mnem| image:: https://img.shields.io/conda/dn/bioconda/bioconductor-mnem.svg?style=flat :target: https://anaconda.org/bioconda/bioconductor-mnem :alt: (downloads) .. |docker_bioconductor-mnem| image:: https://quay.io/repository/biocontainers/bioconductor-mnem/status :target: https://quay.io/repository/biocontainers/bioconductor-mnem .. _`bioconductor-mnem/tags`: https://quay.io/repository/biocontainers/bioconductor-mnem?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-mnem/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-mnem/README.html