recipe bioconductor-smite

Significance-based Modules Integrating the Transcriptome and Epigenome

Homepage:

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

License:

GPL (>=2)

Recipe:

/bioconductor-smite/meta.yaml

Links:

biotools: smite, doi: 10.1186/s12859-017-1477-3

This package builds on the Epimods framework which facilitates finding weighted subnetworks ("modules") on Illumina Infinium 27k arrays using the SpinGlass algorithm, as implemented in the iGraph package. We have created a class of gene centric annotations associated with p-values and effect sizes and scores from any researchers prior statistical results to find functional modules.

package bioconductor-smite

(downloads) docker_bioconductor-smite

Versions:
1.38.0-01.34.0-01.30.0-01.28.0-01.26.0-01.22.0-01.20.0-01.18.0-11.18.0-0

1.38.0-01.34.0-01.30.0-01.28.0-01.26.0-01.22.0-01.20.0-01.18.0-11.18.0-01.16.0-01.14.0-11.12.0-11.10.0-01.8.0-01.6.0-0

Depends:
  • on bioconductor-annotationdbi >=1.72.0,<1.73.0

  • on bioconductor-biobase >=2.70.0,<2.71.0

  • on bioconductor-bionet >=1.70.0,<1.71.0

  • on bioconductor-genelendatabase >=1.46.0,<1.47.0

  • on bioconductor-genomicranges >=1.62.0,<1.63.0

  • on bioconductor-goseq >=1.62.0,<1.63.0

  • on bioconductor-iranges >=2.44.0,<2.45.0

  • on bioconductor-keggrest >=1.50.0,<1.51.0

  • on bioconductor-org.hs.eg.db >=3.22.0,<3.23.0

  • on bioconductor-reactome.db >=1.95.0,<1.96.0

  • on bioconductor-s4vectors >=0.48.0,<0.49.0

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

  • on r-ggplot2

  • on r-hmisc

  • on r-igraph

  • on r-plyr

  • on r-scales

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

to add into an existing workspace instead, run:

pixi add bioconductor-smite

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

Alternatively, to install into a new environment, run:

conda create -n envname bioconductor-smite

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

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