:orphan: .. only available via index, not via toctree .. title:: Package Recipe 'bioconductor-hilda' .. highlight: bash bioconductor-hilda ================== .. conda:recipe:: bioconductor-hilda :replaces_section_title: :noindex: Conducting statistical inference on comparing the mutational exposures of mutational signatures by using hierarchical latent Dirichlet allocation :homepage: https://bioconductor.org/packages/3.20/bioc/html/HiLDA.html :license: GPL-3 :recipe: /`bioconductor-hilda `_/`meta.yaml `_ A package built under the Bayesian framework of applying hierarchical latent Dirichlet allocation. It statistically tests whether the mutational exposures of mutational signatures \(Shiraishi\-model signatures\) are different between two groups. The package also provides inference and visualization. .. conda:package:: bioconductor-hilda |downloads_bioconductor-hilda| |docker_bioconductor-hilda| :versions: .. raw:: html
1.24.0-01.20.0-01.16.0-01.14.0-01.12.0-11.12.0-01.8.0-21.8.0-11.8.0-0 ``1.24.0-0``,  ``1.20.0-0``,  ``1.16.0-0``,  ``1.14.0-0``,  ``1.12.0-1``,  ``1.12.0-0``,  ``1.8.0-2``,  ``1.8.0-1``,  ``1.8.0-0``,  ``1.6.0-0``,  ``1.4.0-2``,  ``1.4.0-1``,  ``1.4.0-0``,  ``1.2.0-0``,  ``1.0.0-0`` .. raw:: html
:depends on bioconductor-biocgenerics: ``>=0.56.0,<0.57.0`` :depends on bioconductor-biocgenerics: ``>=0.56.0,<0.57.0a0`` :depends on bioconductor-biostrings: ``>=2.78.0,<2.79.0`` :depends on bioconductor-biostrings: ``>=2.78.0,<2.79.0a0`` :depends on bioconductor-bsgenome.hsapiens.ucsc.hg19: ``>=1.4.0,<1.5.0`` :depends on bioconductor-bsgenome.hsapiens.ucsc.hg19: ``>=1.4.3,<1.5.0a0`` :depends on bioconductor-genomicfeatures: ``>=1.62.0,<1.63.0`` :depends on bioconductor-genomicfeatures: ``>=1.62.0,<1.63.0a0`` :depends on bioconductor-genomicranges: ``>=1.62.0,<1.63.0`` :depends on bioconductor-genomicranges: ``>=1.62.1,<1.63.0a0`` :depends on bioconductor-s4vectors: ``>=0.48.0,<0.49.0`` :depends on bioconductor-s4vectors: ``>=0.48.0,<0.49.0a0`` :depends on bioconductor-txdb.hsapiens.ucsc.hg19.knowngene: ``>=3.22.0,<3.23.0`` :depends on bioconductor-txdb.hsapiens.ucsc.hg19.knowngene: ``>=3.22.1,<3.23.0a0`` :depends on bioconductor-xvector: ``>=0.50.0,<0.51.0`` :depends on bioconductor-xvector: ``>=0.50.0,<0.51.0a0`` :depends on libblas: ``>=3.9.0,<4.0a0`` :depends on libcxx: ``>=19`` :depends on liblapack: ``>=3.9.0,<4.0a0`` :depends on liblzma: ``>=5.8.2,<6.0a0`` :depends on libzlib: ``>=1.3.1,<2.0a0`` :depends on r-abind: :depends on r-base: ``>=4.5,<4.6.0a0`` :depends on r-cowplot: :depends on r-forcats: :depends on r-ggplot2: :depends on r-r2jags: :depends on r-rcpp: :depends on r-stringr: :depends on r-tidyr: :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-hilda to add into an existing workspace instead, run:: pixi add bioconductor-hilda 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-hilda Alternatively, to install into a new environment, run:: conda create -n envname bioconductor-hilda 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-hilda: (see `bioconductor-hilda/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-hilda| image:: https://img.shields.io/conda/dn/bioconda/bioconductor-hilda.svg?style=flat :target: https://anaconda.org/bioconda/bioconductor-hilda :alt: (downloads) .. |docker_bioconductor-hilda| image:: https://quay.io/repository/biocontainers/bioconductor-hilda/status :target: https://quay.io/repository/biocontainers/bioconductor-hilda .. _`bioconductor-hilda/tags`: https://quay.io/repository/biocontainers/bioconductor-hilda?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-hilda/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-hilda/README.html