Package Recipe 'bioconductor-biovizbase'

recipe bioconductor-biovizbase

Basic graphic utilities for visualization of genomic data.

Homepage:: https://bioconductor.org/packages/3.20/bioc/html/biovizBase.html
License:: Artistic-2.0
Recipe:: /bioconductor-biovizbase/meta.yaml
Links:: biotools: biovizbase, doi: 10.1038/nmeth.3252

The biovizBase package is designed to provide a set of utilities, color schemes and conventions for genomic data. It serves as the base for various high-level packages for biological data visualization. This saves development effort and encourages consistency.

package bioconductor-biovizbase¶

Versions:

1.58.0-0, 1.54.0-1, 1.54.0-0, 1.50.0-1, 1.50.0-0, 1.48.0-0, 1.46.0-1, 1.46.0-0, 1.42.0-2,

1.58.0-0, 1.54.0-1, 1.54.0-0, 1.50.0-1, 1.50.0-0, 1.48.0-0, 1.46.0-1, 1.46.0-0, 1.42.0-2, 1.42.0-1, 1.42.0-0, 1.40.0-0, 1.38.0-1, 1.38.0-0, 1.36.0-0, 1.34.0-0, 1.32.0-1, 1.30.1-0, 1.30.0-0, 1.28.2-0, 1.26.0-0, 1.24.0-0, 1.20.0-0, 1.18.0-1, 1.18.0-0

Depends:

on bioconductor-annotationdbi >=1.72.0,<1.73.0
on bioconductor-annotationdbi >=1.72.0,<1.73.0a0
on bioconductor-annotationfilter >=1.34.0,<1.35.0
on bioconductor-annotationfilter >=1.34.0,<1.35.0a0
on bioconductor-biocgenerics >=0.56.0,<0.57.0
on bioconductor-biocgenerics >=0.56.0,<0.57.0a0
on bioconductor-biostrings >=2.78.0,<2.79.0
on bioconductor-biostrings >=2.78.0,<2.79.0a0
on bioconductor-ensembldb >=2.34.0,<2.35.0
on bioconductor-ensembldb >=2.34.0,<2.35.0a0
on bioconductor-genomeinfodb >=1.46.0,<1.47.0
on bioconductor-genomeinfodb >=1.46.2,<1.47.0a0
on bioconductor-genomicalignments >=1.46.0,<1.47.0
on bioconductor-genomicalignments >=1.46.0,<1.47.0a0
on bioconductor-genomicfeatures >=1.62.0,<1.63.0
on bioconductor-genomicfeatures >=1.62.0,<1.63.0a0
on bioconductor-genomicranges >=1.62.0,<1.63.0
on bioconductor-genomicranges >=1.62.1,<1.63.0a0
on bioconductor-iranges >=2.44.0,<2.45.0
on bioconductor-iranges >=2.44.0,<2.45.0a0
on bioconductor-rsamtools >=2.26.0,<2.27.0
on bioconductor-rsamtools >=2.26.0,<2.27.0a0
on bioconductor-s4vectors >=0.48.0,<0.49.0
on bioconductor-s4vectors >=0.48.0,<0.49.0a0
on bioconductor-seqinfo >=1.0.0,<1.1.0
on bioconductor-seqinfo >=1.0.0,<1.1.0a0
on bioconductor-summarizedexperiment >=1.40.0,<1.41.0
on bioconductor-summarizedexperiment >=1.40.0,<1.41.0a0
on bioconductor-variantannotation >=1.56.0,<1.57.0
on bioconductor-variantannotation >=1.56.0,<1.57.0a0
on libblas >=3.9.0,<4.0a0
on libgcc >=14
on liblapack >=3.9.0,<4.0a0
on liblzma >=5.8.2,<6.0a0
on libzlib >=1.3.1,<2.0a0
on r-base >=4.5,<4.6.0a0
on r-dichromat
on r-hmisc
on r-rcolorbrewer
on r-rlang
on r-scales

Additional platforms:

linux-aarch64, osx-arm64

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-biovizbase

to add into an existing workspace instead, run:

pixi add bioconductor-biovizbase

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-biovizbase

Alternatively, to install into a new environment, run:

conda create -n envname bioconductor-biovizbase

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

(see bioconductor-biovizbase/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¶

Link to this page¶

Render an 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-biovizbase/README.html)