Package Recipe 'bioconductor-chromstar'

recipe bioconductor-chromstar

Combinatorial and Differential Chromatin State Analysis for ChIP-Seq Data

Homepage:: https://bioconductor.org/packages/3.18/bioc/html/chromstaR.html
License:: Artistic-2.0
Recipe:: /bioconductor-chromstar/meta.yaml
Links:: biotools: chromstar, doi: 10.1101/038612

This package implements functions for combinatorial and differential analysis of ChIP-seq data. It includes uni- and multivariate peak-calling, export to genome browser viewable files, and functions for enrichment analyses.

package bioconductor-chromstar¶

Versions:

1.28.0-0, 1.26.0-0, 1.24.0-1, 1.24.0-0, 1.20.2-1, 1.20.2-0, 1.19.0-0, 1.18.0-0, 1.16.0-2,

1.28.0-0, 1.26.0-0, 1.24.0-1, 1.24.0-0, 1.20.2-1, 1.20.2-0, 1.19.0-0, 1.18.0-0, 1.16.0-2, 1.16.0-1, 1.16.0-0, 1.14.1-0, 1.12.0-1, 1.10.0-1, 1.8.1-0, 1.8.0-0, 1.6.2-0, 1.4.0-0

Depends:

on bioconductor-bamsignals >=1.34.0,<1.35.0
on bioconductor-bamsignals >=1.34.0,<1.35.0a0
on bioconductor-biocgenerics >=0.48.0,<0.49.0
on bioconductor-biocgenerics >=0.48.1,<0.49.0a0
on bioconductor-chromstardata >=1.28.0,<1.29.0
on bioconductor-chromstardata >=1.28.0,<1.29.0a0
on bioconductor-genomeinfodb >=1.38.0,<1.39.0
on bioconductor-genomeinfodb >=1.38.1,<1.39.0a0
on bioconductor-genomicalignments >=1.38.0,<1.39.0
on bioconductor-genomicalignments >=1.38.0,<1.39.0a0
on bioconductor-genomicranges >=1.54.0,<1.55.0
on bioconductor-genomicranges >=1.54.1,<1.55.0a0
on bioconductor-iranges >=2.36.0,<2.37.0
on bioconductor-iranges >=2.36.0,<2.37.0a0
on bioconductor-rsamtools >=2.18.0,<2.19.0
on bioconductor-rsamtools >=2.18.0,<2.19.0a0
on bioconductor-s4vectors >=0.40.0,<0.41.0
on bioconductor-s4vectors >=0.40.2,<0.41.0a0
on libblas >=3.9.0,<4.0a0
on libgcc-ng >=12
on liblapack >=3.9.0,<4.0a0
on libstdcxx-ng >=12
on r-base >=4.3,<4.4.0a0
on r-doparallel
on r-foreach
on r-ggplot2
on r-mvtnorm
on r-reshape2

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

to add into an existing workspace instead, run:

pixi add bioconductor-chromstar

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

Alternatively, to install into a new environment, run:

conda create -n envname bioconductor-chromstar

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

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