recipe bioconductor-missmethyl

Analysing Illumina HumanMethylation BeadChip Data

Homepage:

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

License:

GPL-2

Recipe:

/bioconductor-missmethyl/meta.yaml

Links:

biotools: missmethyl

Normalisation, testing for differential variability and differential methylation and gene set testing for data from Illumina's Infinium HumanMethylation arrays. The normalisation procedure is subset-quantile within-array normalisation (SWAN), which allows Infinium I and II type probes on a single array to be normalised together. The test for differential variability is based on an empirical Bayes version of Levene's test. Differential methylation testing is performed using RUV, which can adjust for systematic errors of unknown origin in high-dimensional data by using negative control probes. Gene ontology analysis is performed by taking into account the number of probes per gene on the array, as well as taking into account multi-gene associated probes.

package bioconductor-missmethyl

(downloads) docker_bioconductor-missmethyl

Versions:
1.44.0-01.40.0-01.32.0-01.26.0-01.24.0-11.24.0-01.22.0-01.20.0-01.18.0-1

1.44.0-01.40.0-01.32.0-01.26.0-01.24.0-11.24.0-01.22.0-01.20.0-01.18.0-11.16.0-01.14.0-01.12.0-0

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

  • on bioconductor-biobase >=2.70.0,<2.71.0

  • on bioconductor-biocgenerics >=0.56.0,<0.57.0

  • on bioconductor-genomeinfodb >=1.46.0,<1.47.0

  • on bioconductor-genomicranges >=1.62.0,<1.63.0

  • on bioconductor-go.db >=3.22.0,<3.23.0

  • on bioconductor-illuminahumanmethylation450kanno.ilmn12.hg19 >=0.6.0,<0.7.0

  • on bioconductor-illuminahumanmethylation450kmanifest >=0.4.0,<0.5.0

  • on bioconductor-illuminahumanmethylationepicanno.ilm10b4.hg19 >=0.6.0,<0.7.0

  • on bioconductor-illuminahumanmethylationepicmanifest >=0.3.0,<0.4.0

  • on bioconductor-illuminahumanmethylationepicv2anno.20a1.hg38 >=1.0.0,<1.1.0

  • on bioconductor-illuminahumanmethylationepicv2manifest >=1.0.0,<1.1.0

  • on bioconductor-iranges >=2.44.0,<2.45.0

  • on bioconductor-limma >=3.66.0,<3.67.0

  • on bioconductor-methylumi >=2.56.0,<2.57.0

  • on bioconductor-minfi >=1.56.0,<1.57.0

  • on bioconductor-org.hs.eg.db >=3.22.0,<3.23.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-biasedurn

  • on r-ruv

  • on r-statmod

  • on r-stringr

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

to add into an existing workspace instead, run:

pixi add bioconductor-missmethyl

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

Alternatively, to install into a new environment, run:

conda create -n envname bioconductor-missmethyl

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

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