recipe bioconductor-deeppincs

Protein Interactions and Networks with Compounds based on Sequences using Deep Learning

Homepage:

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

License:

Artistic-2.0

Recipe:

/bioconductor-deeppincs/meta.yaml

The identification of novel compound-protein interaction (CPI) is important in drug discovery. Revealing unknown compound-protein interactions is useful to design a new drug for a target protein by screening candidate compounds. The accurate CPI prediction assists in effective drug discovery process. To identify potential CPI effectively, prediction methods based on machine learning and deep learning have been developed. Data for sequences are provided as discrete symbolic data. In the data, compounds are represented as SMILES (simplified molecular-input line-entry system) strings and proteins are sequences in which the characters are amino acids. The outcome is defined as a variable that indicates how strong two molecules interact with each other or whether there is an interaction between them. In this package, a deep-learning based model that takes only sequence information of both compounds and proteins as input and the outcome as output is used to predict CPI. The model is implemented by using compound and protein encoders with useful features. The CPI model also supports other modeling tasks, including protein-protein interaction (PPI), chemical-chemical interaction (CCI), or single compounds and proteins. Although the model is designed for proteins, DNA and RNA can be used if they are represented as sequences.

package bioconductor-deeppincs

(downloads) docker_bioconductor-deeppincs

Versions:

1.18.0-01.14.0-01.10.0-01.8.0-01.6.0-01.2.0-01.0.0-0

Depends:
  • on bioconductor-ttgsea >=1.18.0,<1.19.0

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

  • on r-catencoders

  • on r-keras

  • on r-matlab

  • on r-prroc

  • on r-purrr

  • on r-rcdk

  • on r-reticulate

  • on r-stringdist

  • on r-tensorflow

  • on r-tokenizers

  • on r-webchem

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

to add into an existing workspace instead, run:

pixi add bioconductor-deeppincs

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

Alternatively, to install into a new environment, run:

conda create -n envname bioconductor-deeppincs

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

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