File size: 8,632 Bytes
c2767f4
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
---
frameworks:
- ""
language:
- en
license: mit
tags:
- OneScience
- protein-ligand molecular docking
- generative
---
<p align="center">
  <strong>
    <span style="font-size: 30px;">DiffDock</span>
  </strong>
</p>

# Model Overview

DiffDock is a diffusion model for protein-ligand molecular docking proposed by Corso et al. It supports single-complex molecular docking, batch molecular docking, evaluation, and related workflows.

# Model Description

DiffDock formulates docking as a generative modeling problem. Given a protein receptor and a small-molecule ligand, it jointly models the ligand's translational, rotational, and torsional degrees of freedom through diffusion processes on SO(3)/SE(3), and generates candidate binding conformations.

Weights and datasets are not available at the moment. They will be uploaded to ModelScope soon, and command-line downloads will be supported later.

# Use Cases

| Use case | Description |
| :---: | :---: |
| Score model training | Takes processed PDBBind or MOAD data as input and outputs a DiffDock score model checkpoint |
| Single-complex molecular docking | Takes a protein PDB file and a ligand SMILES/SDF/MOL2 input, and outputs candidate ligand binding conformations in SDF format |
| Batch molecular docking | Takes a CSV file containing proteins, ligands, and complex names, and outputs sampled conformations in batches |
| Confidence rerank | Uses an additional confidence model to rank sampled conformations |
| Dataset evaluation | Computes metrics such as RMSD for sampling results on a validation or test set, with optional GNINA integration |

# Usage

## 1. Using OneCode

You can try intelligent one-click AI4S programming through the OneCode online environment:

[Try intelligent one-click AI4S programming](https://web-2069360198568017922-iaaj.ksai.scnet.cn:58043/home)

## 2. Manual Installation and Usage

**Hardware Requirements**

- Running on a GPU or DCU is recommended.
- CPU can be used for connectivity checks, but it is relatively slow.
- DCU users need to install DTK in advance. DTK 25.04.2 or later is recommended, or the OneScience-recommended version that matches the current cluster.

**Software Requirements**

Common DiffDock dependencies include PyTorch, PyTorch Geometric, RDKit, OpenBabel, e3nn, torch-scatter, torch-cluster, NumPy, SciPy, tqdm, PyYAML, and others. GNINA energy minimization during dataset evaluation requires installing `gnina` separately.

**Environment Checks**

- NVIDIA GPU:

```bash
nvidia-smi
```

- Hygon DCU:

```bash
hy-smi
```

## Quick Start

### 1. Install the Runtime Environment

```bash
conda create -n onescience311 python=3.11 -y
conda activate onescience311
pip install onescience[bio] -i http://mirrors.onescience.ai:3141/pypi/simple/  --trusted-host mirrors.onescience.ai
```

If the following code cannot find required libraries at runtime, activate CUDA as shown below.

```bash
source ${ROCM_PATH}/cuda/env.sh
export LD_LIBRARY_PATH="$CONDA_PREFIX/lib:$LD_LIBRARY_PATH"
export LD_LIBRARY_PATH="$CONDA_PREFIX/lib/python3.11/site-packages/fastpt/torch/lib:$LD_LIBRARY_PATH"
```

### 2. Download the Model Package and Database

```bash
# If the model ID on the ModelScope page uses different capitalization, use the actual published name.
modelscope download --model OneScience/diffdock --local_dir ./diffdock
cd diffdock
```

### Training Weights and Datasets

Weights and datasets are not available at the moment. They will be uploaded to ModelScope soon, and command-line downloads will be supported later.

### 3. Check Files in the Package

The current package does not include pretrained weights. The command below should only show source code, configuration files, and example input files:

```bash
find . -maxdepth 3 -type f
```

If sampling or evaluation is required, first obtain a checkpoint through training, or place external DiffDock score/confidence weights in a local directory. Make sure the weight directory contains `model_parameters.yml`.

### 4. Score Model Training

Before training, update the data paths in `configs/training.yml` to local paths. Common fields include:

- `data.pdbbind_dir`: processed PDBBind data directory.
- `data.moad_dir`: processed MOAD data directory.
- `data.split_train`: list of training-set complexes.
- `data.split_val`: list of validation-set complexes.
- `runtime.log_dir`: training output directory.

Start training:

```bash
cd scripts
bash train.sh
```

After training succeeds, the output directory usually contains:

- `model_parameters.yml`: model architecture and training parameters.
- `best_model.pt`: weights with the best validation loss.
- `best_ema_model.pt`: EMA weights.
- `best_inference_epoch_model.pt` or `best_ema_inference_epoch_model.pt`: weights saved when inference validation is enabled.
- `last_model.pt`: training state from the final epoch.

### 5. Molecular Docking Sampling

Sampling requires a trained score model directory, for example:

```text
outputs/train/diffdock_cg_example/
β”œβ”€β”€ model_parameters.yml
└── best_model.pt
```

Update the key fields in `configs/sampling.yml` to the actual paths:

- `model.model_dir`: score model directory.
- `model.ckpt`: score checkpoint file name.
- `confidence.confidence_model_dir`: confidence model directory; set it to `null` when rerank is not used.
- `input.protein_path`: protein PDB path. You can use `data/6o5u_protein_processed.pdb`.
- `input.ligand_description`: SMILES string or ligand SDF/MOL2 path. You can use `data/6o5u_ligand.sdf`.
- `runtime.out_dir`: sampling output directory.

Start single-complex sampling:

```bash
cd scripts
bash infer.sh
```

### 6. CSV Batch Sampling

Set `input.protein_ligand_csv` in `configs/sampling.yml` to the CSV path, and set the single-complex fields to `null` as needed. The CSV is recommended to contain the following columns:

```text
complex_name,protein_path,ligand_description,protein_sequence
```

Here, `ligand_description` can be either a SMILES string or an SDF/MOL2 file path.

### 7. Dataset Evaluation

Before evaluation, update the dataset, model, and output directories in `configs/evaluate.yml` to actual paths:

```bash
python -m scripts.evaluate --config configs/evaluate.yml
```

If `gnina.gnina_minimize=true` is enabled, first make sure the following command can be run directly in the current environment:

```bash
gnina --help
```

### 8. Confidence Model Training

The confidence training entry point is provided by the installed OneScience package. This ModelScope package does not duplicate that module. After completing score model training, run the following in the OneScience environment:

```bash
python -m onescience.confidence.diffdock.confidence_train \
    --original_model_dir outputs/train/diffdock_cg_example \
    --data_dir /path/to/PDBBind_processed \
    --split_train /path/to/splits/timesplit_no_lig_overlap_train \
    --split_val /path/to/splits/timesplit_no_lig_overlap_val
```

# Data Preparation

DiffDock training usually requires preprocessed PDBBind or MOAD data. It is recommended to organize the data under a unified root directory, for example:

```text
${ONESCIENCE_DATASETS_DIR}/diffdock/
β”œβ”€β”€ PDBBind_processed/
β”œβ”€β”€ MOAD_processed/
└── splits/
    β”œβ”€β”€ timesplit_no_lig_overlap_train
    β”œβ”€β”€ timesplit_no_lig_overlap_val
    └── timesplit_test
```

Split files should be plain text files, with one complex name per line. Each name must correspond to a subdirectory name in the data directory.

# Official OneScience Information

| Platform | OneScience main repository | Skills repository |
| --- | --- | --- |
| Gitee | https://gitee.com/onescience-ai/onescience | https://gitee.com/onescience-ai/oneskills |
| GitHub | https://github.com/onescience-ai/OneScience | https://github.com/onescience-ai/oneskills |

# Citation and License

- The original DiffDock code is licensed under the MIT License. This repository retains source attribution and is organized for OneScience ModelScope automated runtime scenarios.
- If you use DiffDock results in research, we recommend citing the original DiffDock and DiffDock-L papers, as well as relevant OneScience project information. Depending on the actual task, also add citations for datasets or tools such as PDBBind, MOAD, RDKit, OpenBabel, and GNINA.

```bibtex
@inproceedings{corso2023diffdock,
  title={DiffDock: Diffusion Steps, Twists, and Turns for Molecular Docking},
  author={Corso, Gabriele and St{\"a}rk, Hannes and Jing, Bowen and Barzilay, Regina and Jaakkola, Tommi},
  booktitle={International Conference on Learning Representations},
  year={2023}
}
```