Package Recipe 'bioconductor-epistack'

recipe bioconductor-epistack

Heatmaps of Stack Profiles from Epigenetic Signals

Homepage:: https://bioconductor.org/packages/3.20/bioc/html/epistack.html
License:: MIT + file LICENSE
Recipe:: /bioconductor-epistack/meta.yaml

The epistack package main objective is the visualizations of stacks of genomic tracks (such as, but not restricted to, ChIP-seq, ATAC-seq, DNA methyation or genomic conservation data) centered at genomic regions of interest. epistack needs three different inputs: 1) a genomic score objects, such as ChIP-seq coverage or DNA methylation values, provided as a `GRanges` (easily obtained from `bigwig` or `bam` files). 2) a list of feature of interest, such as peaks or transcription start sites, provided as a `GRanges` (easily obtained from `gtf` or `bed` files). 3) a score to sort the features, such as peak height or gene expression value.

package bioconductor-epistack¶

Versions:

1.16.0-0, 1.12.0-0, 1.8.0-0, 1.6.0-0, 1.4.0-0, 1.0.0-0

Depends:

on bioconductor-biocgenerics >=0.56.0,<0.57.0
on bioconductor-genomicranges >=1.62.0,<1.63.0
on bioconductor-iranges >=2.44.0,<2.45.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-plotrix

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

to add into an existing workspace instead, run:

pixi add bioconductor-epistack

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

Alternatively, to install into a new environment, run:

conda create -n envname bioconductor-epistack

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

(see bioconductor-epistack/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-epistack/README.html)