recipe bioconductor-omicsviewer

Interactive and explorative visualization of SummarizedExperssionSet or ExpressionSet using omicsViewer

Homepage:

https://bioconductor.org/packages/3.20/bioc/html/omicsViewer.html

License:

GPL-2

Recipe:

/bioconductor-omicsviewer/meta.yaml

omicsViewer visualizes ExpressionSet (or SummarizedExperiment) in an interactive way. The omicsViewer has a separate back- and front-end. In the back-end, users need to prepare an ExpressionSet that contains all the necessary information for the downstream data interpretation. Some extra requirements on the headers of phenotype data or feature data are imposed so that the provided information can be clearly recognized by the front-end, at the same time, keep a minimum modification on the existing ExpressionSet object. The pure dependency on R/Bioconductor guarantees maximum flexibility in the statistical analysis in the back-end. Once the ExpressionSet is prepared, it can be visualized using the front-end, implemented by shiny and plotly. Both features and samples could be selected from (data) tables or graphs (scatter plot/heatmap). Different types of analyses, such as enrichment analysis (using Bioconductor package fgsea or fisher's exact test) and STRING network analysis, will be performed on the fly and the results are visualized simultaneously. When a subset of samples and a phenotype variable is selected, a significance test on means (t-test or ranked based test; when phenotype variable is quantitative) or test of independence (chi-square or fisher’s exact test; when phenotype data is categorical) will be performed to test the association between the phenotype of interest with the selected samples. Additionally, other analyses can be easily added as extra shiny modules. Therefore, omicsViewer will greatly facilitate data exploration, many different hypotheses can be explored in a short time without the need for knowledge of R. In addition, the resulting data could be easily shared using a shiny server. Otherwise, a standalone version of omicsViewer together with designated omics data could be easily created by integrating it with portable R, which can be shared with collaborators or submitted as supplementary data together with a manuscript.

package bioconductor-omicsviewer

(downloads) docker_bioconductor-omicsviewer

Versions:

1.14.0-01.10.0-01.2.0-0

Depends:
  • on bioconductor-biobase >=2.70.0,<2.71.0

  • on bioconductor-fgsea >=1.36.0,<1.37.0

  • on bioconductor-s4vectors >=0.48.0,<0.49.0

  • on bioconductor-summarizedexperiment >=1.40.0,<1.41.0

  • on r-base >=4.5,<4.6.0a0

  • on r-beeswarm

  • on r-curl

  • on r-drc

  • on r-dt

  • on r-fastmatch

  • on r-flatxml

  • on r-ggplot2

  • on r-ggseqlogo

  • on r-htmlwidgets

  • on r-httr

  • on r-matrix

  • on r-matrixstats

  • on r-networkd3

  • on r-openxlsx

  • on r-plotly

  • on r-psych

  • on r-rcolorbrewer

  • on r-reshape2

  • on r-rocr

  • on r-rsqlite

  • on r-shiny

  • on r-shinybusy

  • on r-shinycssloaders

  • on r-shinyjs

  • on r-shinythemes

  • on r-shinywidgets

  • on r-stringr

  • on r-survival

  • on r-survminer

Additional platforms:

Installation

You need a conda-compatible package manager (currently either pixi, conda, or micromamba) and the Bioconda channel already activated (see Usage). 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 Usage), to install globally, run:

pixi global install bioconductor-omicsviewer

to add into an existing workspace instead, run:

pixi add bioconductor-omicsviewer

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 Usage), to install into an existing and activated environment, run:

conda install bioconductor-omicsviewer

Alternatively, to install into a new environment, run:

conda create -n envname bioconductor-omicsviewer

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-omicsviewer:<tag>

(see bioconductor-omicsviewer/tags for valid values for <tag>).

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.

Download stats