recipe bioconductor-podkat

Position-Dependent Kernel Association Test

Homepage:

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

License:

GPL (>= 2)

Recipe:

/bioconductor-podkat/meta.yaml

Links:

biotools: podkat, doi: 10.1038/nmeth.3252

This package provides an association test that is capable of dealing with very rare and even private variants. This is accomplished by a kernel-based approach that takes the positions of the variants into account. The test can be used for pre-processed matrix data, but also directly for variant data stored in VCF files. Association testing can be performed whole-genome, whole-exome, or restricted to pre-defined regions of interest. The test is complemented by tools for analyzing and visualizing the results.

package bioconductor-podkat

(downloads) docker_bioconductor-podkat

Versions:
1.42.0-11.42.0-01.38.0-01.34.0-01.32.0-01.30.0-11.30.0-01.26.0-21.26.0-1

1.42.0-11.42.0-01.38.0-01.34.0-01.32.0-01.30.0-11.30.0-01.26.0-21.26.0-11.26.0-01.24.0-01.22.0-11.22.0-01.20.0-01.18.0-01.16.0-11.14.0-11.14.0-01.12.0-01.10.0-01.8.0-0

Depends:
  • on bioconductor-biobase >=2.70.0,<2.71.0

  • on bioconductor-biobase >=2.70.0,<2.71.0a0

  • on bioconductor-biocgenerics >=0.56.0,<0.57.0

  • on bioconductor-biocgenerics >=0.56.0,<0.57.0a0

  • on bioconductor-biostrings >=2.78.0,<2.79.0

  • on bioconductor-biostrings >=2.78.0,<2.79.0a0

  • on bioconductor-bsgenome >=1.78.0,<1.79.0

  • on bioconductor-bsgenome >=1.78.0,<1.79.0a0

  • on bioconductor-genomicranges >=1.62.0,<1.63.0

  • on bioconductor-genomicranges >=1.62.1,<1.63.0a0

  • on bioconductor-iranges >=2.44.0,<2.45.0

  • on bioconductor-iranges >=2.44.0,<2.45.0a0

  • on bioconductor-rhtslib >=3.6.0,<3.7.0

  • on bioconductor-rhtslib >=3.6.0,<3.7.0a0

  • on bioconductor-rsamtools >=2.26.0,<2.27.0

  • on bioconductor-rsamtools >=2.26.0,<2.27.0a0

  • on bioconductor-seqinfo >=1.0.0,<1.1.0

  • on bioconductor-seqinfo >=1.0.0,<1.1.0a0

  • on libblas >=3.9.0,<4.0a0

  • on libgcc >=14

  • on liblapack >=3.9.0,<4.0a0

  • on liblzma >=5.8.2,<6.0a0

  • on libstdcxx >=14

  • on libzlib >=1.3.1,<2.0a0

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

  • on r-matrix

  • on r-rcpp >=0.11.1

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

to add into an existing workspace instead, run:

pixi add bioconductor-podkat

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

Alternatively, to install into a new environment, run:

conda create -n envname bioconductor-podkat

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

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