D-SCRIPT
D-SCRIPT is a deep learning method for predicting a physical interaction between two proteins given just their sequences. It generalizes well to new species and is robust to limitations in training data size. Its design reflects the intuition that for two proteins to physically interact, a subset of amino acids from each protein should be in contact with the other. The intermediate stages of D-SCRIPT directly implement this intuition, with the penultimate stage in D-SCRIPT being a rough estimate of the inter-protein contact map of the protein dimer. This structurally-motivated design enhances the interpretability of the results and, since structure is more conserved evolutionarily than sequence, improves generalizability across species.
You can now make predictions with D-SCRIPT via the interface on HuggingFace!
Installation
pip install dscript
Usage
Protein sequences need to first be embedded using the Bepler+Berger protein language model; this requires a .fasta file as input. Everything before the first space will be used as the key.
dscript embed --seqs [sequences] --outfile [embedding file]
Candidate pairs should be in tab-separated (.tsv) format with no header, and columns for [protein key 1], [protein key 2]. Optionally, a third column with [label] can be provided, so predictions can be made using training or test data files (but the label will not affect the predictions only the first two columns will be read).
While pre-trained model files can be downloaded directly, we recommend instead passing the name of a pre-trained model that will be automatically downloaded from HuggingFace. Available models include:
- samsl/dscript_human_v1
- samsl/topsy_turvy_human_v1 (recommended)
- samsl/tt3d_human_v1
dscript predict --pairs [input data] --embeddings [embedding file] --model [model file] --outfile [predictions file]
References
- The original D-SCRIPT model is described in the paper “Sequence-based prediction of protein-protein interactions: a structure-aware interpretable deep learning model”.
- We have updated D-SCRIPT to incorporate network information (Topsy Turvy) and structure information (TT3D)
- Documentation
Metadata
Release files for dscript 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dscript-0.3.1.tar.gz | 57.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dscript-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 128.6 kB
Release files / dscript-0.3.1.tar.gz
| Download URL | dscript-0.3.1.tar.gz |
|---|---|
| Size | 57.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c8617b2fe742b69916b000559917f777546c4e0e9b0ab17023382e6c65ddc050
|
|
BLAKE2b-256 checksum How to use checksums |
f624afa8df98e20639d2e1e087882b2610fd03cd15c6869f4798bb662eab8494
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 12, 2025.
Transparency logRelease files / dscript-0.3.1-py3-none-any.whl
| Download URL | dscript-0.3.1-py3-none-any.whl |
|---|---|
| Size | 71.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c1182f68da2af165dffeae3da062745d8bfd88a19a10cb011f9fdcdd1a2b320b
|
|
BLAKE2b-256 checksum How to use checksums |
00f85238d770333a49f1f7b953517e8e97d51dd8735d6d50ccfa8e8da0047ffa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 12, 2025.
Transparency log