:orphan: .. only available via index, not via toctree .. title:: Package Recipe 'bioconductor-aldex2' .. highlight: bash bioconductor-aldex2 =================== .. conda:recipe:: bioconductor-aldex2 :replaces_section_title: :noindex: Analysis Of Differential Abundance Taking Sample and Scale Variation Into Account :homepage: https://bioconductor.org/packages/3.20/bioc/html/ALDEx2.html :license: GPL (>=3) :recipe: /`bioconductor-aldex2 `_/`meta.yaml `_ :links: biotools: :biotools:`aldex2` A differential abundance analysis for the comparison of two or more conditions. Useful for analyzing data from standard RNA\-seq or meta\-RNA\-seq assays as well as selected and unselected values from in\-vitro sequence selections. Uses a Dirichlet\-multinomial model to infer abundance from counts\, optimized for three or more experimental replicates. The method infers biological and sampling variation to calculate the expected false discovery rate\, given the variation\, based on a Wilcoxon Rank Sum test and Welch\'s t\-test \(via aldex.ttest\)\, a Kruskal\-Wallis test \(via aldex.kw\)\, a generalized linear model \(via aldex.glm\)\, or a correlation test \(via aldex.corr\). All tests report predicted p\-values and posterior Benjamini\-Hochberg corrected p\-values. ALDEx2 also calculates expected standardized effect sizes for paired or unpaired study designs. ALDEx2 can now be used to estimate the effect of scale on the results and report on the scale\-dependent robustness of results. .. conda:package:: bioconductor-aldex2 |downloads_bioconductor-aldex2| |docker_bioconductor-aldex2| :versions: .. raw:: html
1.42.0-01.38.0-01.34.0-01.32.0-01.30.0-01.26.0-01.24.0-01.22.0-11.22.0-0 ``1.42.0-0``,  ``1.38.0-0``,  ``1.34.0-0``,  ``1.32.0-0``,  ``1.30.0-0``,  ``1.26.0-0``,  ``1.24.0-0``,  ``1.22.0-1``,  ``1.22.0-0``,  ``1.20.0-0``,  ``1.18.0-0``,  ``1.16.0-1``,  ``1.14.1-0``,  ``1.14.0-0``,  ``1.12.0-0``,  ``1.10.0-0``,  ``1.8.0-0`` .. raw:: html
:depends on bioconductor-biocparallel: ``>=1.44.0,<1.45.0`` :depends on bioconductor-genomicranges: ``>=1.62.0,<1.63.0`` :depends on bioconductor-iranges: ``>=2.44.0,<2.45.0`` :depends on bioconductor-multtest: ``>=2.66.0,<2.67.0`` :depends on bioconductor-s4vectors: ``>=0.48.0,<0.49.0`` :depends on bioconductor-summarizedexperiment: ``>=1.40.0,<1.41.0`` :depends on r-base: ``>=4.5,<4.6.0a0`` :depends on r-directlabels: :depends on r-lattice: :depends on r-latticeextra: :depends on r-rfast: :depends on r-zcompositions: :additional platforms: 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-aldex2 to add into an existing workspace instead, run:: pixi add bioconductor-aldex2 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-aldex2 Alternatively, to install into a new environment, run:: conda create -n envname bioconductor-aldex2 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-aldex2: (see `bioconductor-aldex2/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-aldex2| image:: https://img.shields.io/conda/dn/bioconda/bioconductor-aldex2.svg?style=flat :target: https://anaconda.org/bioconda/bioconductor-aldex2 :alt: (downloads) .. |docker_bioconductor-aldex2| image:: https://quay.io/repository/biocontainers/bioconductor-aldex2/status :target: https://quay.io/repository/biocontainers/bioconductor-aldex2 .. _`bioconductor-aldex2/tags`: https://quay.io/repository/biocontainers/bioconductor-aldex2?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-aldex2/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-aldex2/README.html