recipe bioconductor-motifbreakr

A Package For Predicting The Disruptiveness Of Single Nucleotide Polymorphisms On Transcription Factor Binding Sites

Homepage:

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

License:

GPL-2

Recipe:

/bioconductor-motifbreakr/meta.yaml

Links:

biotools: motifbreakr

We introduce motifbreakR, which allows the biologist to judge in the first place whether the sequence surrounding the polymorphism is a good match, and in the second place how much information is gained or lost in one allele of the polymorphism relative to another. MotifbreakR is both flexible and extensible over previous offerings; giving a choice of algorithms for interrogation of genomes with motifs from public sources that users can choose from; these are 1) a weighted-sum probability matrix, 2) log-probabilities, and 3) weighted by relative entropy. MotifbreakR can predict effects for novel or previously described variants in public databases, making it suitable for tasks beyond the scope of its original design. Lastly, it can be used to interrogate any genome curated within Bioconductor (currently there are 32 species, a total of 109 versions).

package bioconductor-motifbreakr

(downloads) docker_bioconductor-motifbreakr

Versions:
2.24.0-02.16.0-02.13.7-02.12.0-02.8.0-02.6.0-02.4.0-12.4.0-02.2.0-0

2.24.0-02.16.0-02.13.7-02.12.0-02.8.0-02.6.0-02.4.0-12.4.0-02.2.0-02.0.0-01.14.0-11.12.0-01.10.0-01.8.0-01.6.0-01.4.0-0

Depends:
  • on bioconductor-biocfilecache >=3.0.0,<3.1.0

  • on bioconductor-biocgenerics >=0.56.0,<0.57.0

  • on bioconductor-biocparallel >=1.44.0,<1.45.0

  • on bioconductor-biomart >=2.66.0,<2.67.0

  • on bioconductor-biostrings >=2.78.0,<2.79.0

  • on bioconductor-bsgenome >=1.78.0,<1.79.0

  • on bioconductor-genomeinfodb >=1.46.0,<1.47.0

  • on bioconductor-genomicranges >=1.62.0,<1.63.0

  • on bioconductor-gviz >=1.54.0,<1.55.0

  • on bioconductor-iranges >=2.44.0,<2.45.0

  • on bioconductor-motifdb >=1.52.0,<1.53.0

  • on bioconductor-motifstack >=1.54.0,<1.55.0

  • on bioconductor-pwalign >=1.6.0,<1.7.0

  • on bioconductor-rtracklayer >=1.70.0,<1.71.0

  • on bioconductor-s4vectors >=0.48.0,<0.49.0

  • on bioconductor-summarizedexperiment >=1.40.0,<1.41.0

  • on bioconductor-variantannotation >=1.56.0,<1.57.0

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

  • on r-bsicons

  • on r-bslib

  • on r-dt

  • on r-matrixstats

  • on r-shiny

  • on r-stringr

  • on r-tfmpvalue

  • on r-vroom

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

to add into an existing workspace instead, run:

pixi add bioconductor-motifbreakr

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

Alternatively, to install into a new environment, run:

conda create -n envname bioconductor-motifbreakr

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

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