:orphan: .. only available via index, not via toctree .. title:: Package Recipe 'bioconductor-tcgabiolinks' .. highlight: bash bioconductor-tcgabiolinks ========================= .. conda:recipe:: bioconductor-tcgabiolinks :replaces_section_title: :noindex: TCGAbiolinks\: An R\/Bioconductor package for integrative analysis with GDC data :homepage: https://bioconductor.org/packages/3.20/bioc/html/TCGAbiolinks.html :license: GPL (>= 3) :recipe: /`bioconductor-tcgabiolinks `_/`meta.yaml `_ :links: biotools: :biotools:`tcgabiolinks`, doi: :doi:`10.1093/nar/gkv1507` The aim of TCGAbiolinks is \: i\) facilitate the GDC open\-access data retrieval\, ii\) prepare the data using the appropriate pre\-processing strategies\, iii\) provide the means to carry out different standard analyses and iv\) to easily reproduce earlier research results. In more detail\, the package provides multiple methods for analysis \(e.g.\, differential expression analysis\, identifying differentially methylated regions\) and methods for visualization \(e.g.\, survival plots\, volcano plots\, starburst plots\) in order to easily develop complete analysis pipelines. .. conda:package:: bioconductor-tcgabiolinks |downloads_bioconductor-tcgabiolinks| |docker_bioconductor-tcgabiolinks| :versions: .. raw:: html
2.38.0-02.34.0-02.30.0-02.28.3-02.25.3-02.22.1-02.20.0-02.18.0-12.18.0-0 ``2.38.0-0``,  ``2.34.0-0``,  ``2.30.0-0``,  ``2.28.3-0``,  ``2.25.3-0``,  ``2.22.1-0``,  ``2.20.0-0``,  ``2.18.0-1``,  ``2.18.0-0``,  ``2.16.0-0``,  ``2.14.0-0``,  ``2.12.3-0``,  ``2.10.0-0``,  ``2.8.4-0``,  ``2.6.11-0`` .. raw:: html
:depends on bioconductor-biomart: ``>=2.66.0,<2.67.0`` :depends on bioconductor-genomicranges: ``>=1.62.0,<1.63.0`` :depends on bioconductor-iranges: ``>=2.44.0,<2.45.0`` :depends on bioconductor-s4vectors: ``>=0.48.0,<0.49.0`` :depends on bioconductor-summarizedexperiment: ``>=1.40.0,<1.41.0`` :depends on bioconductor-tcgabiolinksgui.data: ``>=1.30.0,<1.31.0`` :depends on r-base: ``>=4.5,<4.6.0a0`` :depends on r-data.table: :depends on r-downloader: ``>=0.4`` :depends on r-dplyr: :depends on r-ggplot2: :depends on r-httr: ``>=1.2.1`` :depends on r-jsonlite: ``>=1.0.0`` :depends on r-knitr: :depends on r-plyr: :depends on r-purrr: :depends on r-r.utils: :depends on r-readr: :depends on r-rvest: ``>=0.3.0`` :depends on r-stringr: ``>=1.0.0`` :depends on r-tibble: :depends on r-tidyr: :depends on r-xml: ``>=3.98.0`` :depends on r-xml2: :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-tcgabiolinks to add into an existing workspace instead, run:: pixi add bioconductor-tcgabiolinks 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-tcgabiolinks Alternatively, to install into a new environment, run:: conda create -n envname bioconductor-tcgabiolinks 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-tcgabiolinks: (see `bioconductor-tcgabiolinks/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-tcgabiolinks| image:: https://img.shields.io/conda/dn/bioconda/bioconductor-tcgabiolinks.svg?style=flat :target: https://anaconda.org/bioconda/bioconductor-tcgabiolinks :alt: (downloads) .. |docker_bioconductor-tcgabiolinks| image:: https://quay.io/repository/biocontainers/bioconductor-tcgabiolinks/status :target: https://quay.io/repository/biocontainers/bioconductor-tcgabiolinks .. _`bioconductor-tcgabiolinks/tags`: https://quay.io/repository/biocontainers/bioconductor-tcgabiolinks?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-tcgabiolinks/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-tcgabiolinks/README.html