Package Recipe 'bioconductor-ipath'

recipe bioconductor-ipath

iPath pipeline for detecting perturbed pathways at individual level

Homepage:: https://bioconductor.org/packages/3.20/bioc/html/iPath.html
License:: GPL-2
Recipe:: /bioconductor-ipath/meta.yaml

iPath is the Bioconductor package used for calculating personalized pathway score and test the association with survival outcomes. Abundant single-gene biomarkers have been identified and used in the clinics. However, hundreds of oncogenes or tumor-suppressor genes are involved during the process of tumorigenesis. We believe individual-level expression patterns of pre-defined pathways or gene sets are better biomarkers than single genes. In this study, we devised a computational method named iPath to identify prognostic biomarker pathways, one sample at a time. To test its utility, we conducted a pan-cancer analysis across 14 cancer types from The Cancer Genome Atlas and demonstrated that iPath is capable of identifying highly predictive biomarkers for clinical outcomes, including overall survival, tumor subtypes, and tumor stage classifications. We found that pathway-based biomarkers are more robust and effective than single genes.

package bioconductor-ipath¶

Versions:

1.16.0-0, 1.12.0-0, 1.8.0-0, 1.6.1-0, 1.4.0-1, 1.4.0-0, 1.0.0-2, 1.0.0-1, 1.0.0-0

Depends:

on bioconductor-biocparallel >=1.44.0,<1.45.0
on bioconductor-biocparallel >=1.44.0,<1.45.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-ggplot2
on r-ggpubr
on r-matrixstats
on r-mclust
on r-rcpp >=1.0.5
on r-rcpparmadillo
on r-survival
on r-survminer

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

to add into an existing workspace instead, run:

pixi add bioconductor-ipath

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

Alternatively, to install into a new environment, run:

conda create -n envname bioconductor-ipath

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

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

[![install with bioconda](https://img.shields.io/badge/install%20with-bioconda-brightgreen.svg?style=flat)](http://bioconda.github.io/recipes/bioconductor-ipath/README.html)