- recipe bioconductor-inpower
An R package for computing the number of susceptibility SNPs
- Homepage:
https://bioconductor.org/packages/3.20/bioc/html/INPower.html
- License:
GPL-2 + file LICENSE
- Recipe:
- Links:
biotools: inpower, doi: 10.1038/nmeth.3252
An R package for computing the number of susceptibility SNPs and power of future studies
- package bioconductor-inpower¶
-
- Versions:
1.46.0-0,1.42.0-0,1.38.0-0,1.36.0-0,1.34.0-0,1.30.0-0,1.28.0-0,1.26.0-1,1.26.0-0,1.46.0-0,1.42.0-0,1.38.0-0,1.36.0-0,1.34.0-0,1.30.0-0,1.28.0-0,1.26.0-1,1.26.0-0,1.24.0-0,1.22.0-0,1.20.0-1,1.20.0-0,1.18.0-0,1.16.0-0,1.14.0-0- Depends:
on r-base
>=4.5,<4.6.0a0on r-mvtnorm
- 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-inpower
to add into an existing workspace instead, run:
pixi add bioconductor-inpower
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-inpower
Alternatively, to install into a new environment, run:
conda create -n envname bioconductor-inpower
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-inpower:<tag>
(see bioconductor-inpower/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:
[](http://bioconda.github.io/recipes/bioconductor-inpower/README.html)