recipe bioconductor-deeptarget

Deep characterization of cancer drugs

Homepage:

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

License:

GPL-2

Recipe:

/bioconductor-deeptarget/meta.yaml

This package predicts a drug’s primary target(s) or secondary target(s) by integrating large-scale genetic and drug screens from the Cancer Dependency Map project run by the Broad Institute. It further investigates whether the drug specifically targets the wild-type or mutated target forms. To show how to use this package in practice, we provided sample data along with step-by-step example.

package bioconductor-deeptarget

(downloads) docker_bioconductor-deeptarget

Versions:

1.4.0-01.0.0-0

Depends:
  • on bioconductor-biocparallel >=1.44.0,<1.45.0

  • on bioconductor-depmap >=1.24.0,<1.25.0

  • on bioconductor-fgsea >=1.36.0,<1.37.0

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

  • on r-dplyr

  • on r-ggplot2

  • on r-ggpubr

  • on r-proc

  • on r-readr

  • 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-deeptarget

to add into an existing workspace instead, run:

pixi add bioconductor-deeptarget

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

Alternatively, to install into a new environment, run:

conda create -n envname bioconductor-deeptarget

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

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