README.md 7.68 KB
Newer Older
mashun1's avatar
mashun1 committed
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
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
# JSON file format for AlphaFold Server jobs

You can
[download an example JSON file here](https://github.com/google-deepmind/alphafold/blob/main/server/example.json);
here we describe the contents of this example JSON file.

This JSON file consists of a list of dictionaries (even in the case of a single
dictionary, a single-element list must be used), with each dictionary containing
a job description. Therefore, you can specify multiple jobs in one JSON file.

Each job description contains a job name, a list of PRNG seeds (which can be an
empty list for automated random seed assignment), and a list of entities
(molecules) to be modeled.

AlphaFold Server JSON files are especially useful for automation of repetitive
modeling jobs (e.g. to screen interactions of one protein with a small number of
others). The easiest way to construct an initial JSON file is to run a modeling
job via AlphaFold Server GUI and use it as a template. AlphaFold Server will
produce a zip file containing modeling results. Inside the zip file you will
find a JSON file named `<job_name>_job_request.json` containing the job inputs.
These files offer a convenient starting point for generating new jobs as they
are easily editable in standard text editors or in programming environments like
Google Colab notebooks.

Note that comments are not allowed in JSON files.

## Job name, seeds and sequences

*   `name` is a string with the job name. This is how the job will appear as in
    the job history table.
*   `modelSeeds` is a list of strings of uint32 seed values (e.g.
    `["1593933729", "4273"]`). Seeds are used to run the modeling. We recommend
    providing an empty list, in which case a single random seed will be used.
    This is the recommended option.
*   `sequences` is a list of dictionaries that carry descriptions of the
    entities (molecules) for modeling.

```json
{
  "name": "Test Fold Job Number One",
  "modelSeeds": [],
  "sequences": [...]
}
```

## Entity types

Valid entity types mirror those available in the AlphaFold Server web interface:

*   `proteinChain` – used for proteins
*   `dnaSequence` – used for DNA (single strand)
*   `rnaSequence` – used for RNA (single strand)
*   `ligand` – used for allowed ligands
*   `ion` – used for allowed ions

### Protein chains

`sequence` is a string containing protein sequence; the same limitations as in
the UI are in place, e.g. only letters corresponding to amino acids are allowed,
as defined by IUPAC. Only 20 standard amino acid type are supported.

`count` is the number of copies of this protein chain (integer).

`glycans` is an optional list of dictionaries that carries descriptions of the
protein glycosylation.

*   `residues` is a string defining glycan. Please refer to the
    [FAQ](https://alphafoldserver.com/faq) for the format description and
    allowed glycans.
*   `position` is a position of the amino acid to which the glycan is attached
    (integer, 1-based indexing).

`modifications` is an optional list of dictionaries that carries descriptions of
the post-translational modifications.

*   `ptmType` is a string containing the
    [CCD code](https://www.wwpdb.org/data/ccd) of the modification; the same
    codes are allowed as in the UI.
*   `position` is a position of the modified amino acid (integer).
*   Allowed modifications: `CCD_SEP`, `CCD_TPO`, `CCD_PTR`, `CCD_NEP`,
    `CCD_HIP`, `CCD_ALY`, `CCD_MLY`, `CCD_M3L`, `CCD_MLZ`, `CCD_2MR`, `CCD_AGM`,
    `CCD_MCS`, `CCD_HYP`, `CCD_HY3`, `CCD_LYZ`, `CCD_AHB`, `CCD_P1L`, `CCD_SNN`,
    `CCD_SNC`, `CCD_TRF`, `CCD_KCR`, `CCD_CIR`, `CCD_YHA`

```json
{
  "proteinChain": {
    "sequence": "PREACHINGS",

    "glycans": [
      {
        "residues": "NAG(NAG)(BMA)",
        "position": 8
      },
      {
        "residues": "BMA",
        "position": 10
      }
    ],

    "modifications": [
      {
        "ptmType": "CCD_HY3",
        "ptmPosition": 1
      },
      {
        "ptmType": "CCD_P1L",
        "ptmPosition": 5
      }
    ],

    "count": 1
  }
},
{
  "proteinChain": {
    "sequence": "REACHER",
    "count": 1
  }
}
```

### DNA chains

Please note that the `dnaSequence` type refers to single stranded DNA. If you
wish to model double stranded DNA, please add a second `"dnaSequence`", carrying
the sequence of the reverse complement strand.

`sequence` is a string containing a DNA sequence; the same limitations as in the
UI are in place, i.e. only letters A, T, G, C are allowed.

`count` is a number of copies of this DNA chain (integer).

`modifications` is an optional list of dictionaries that carries descriptions of
the DNA chemical modifications.

*   `modificationType` is a string containing
    [CCD code](https://www.wwpdb.org/data/ccd) of modification; the same codes
    are allowed as in the UI.
*   `basePosition` is a position of the modified nucleotide (integer).
*   Allowed modifications: `CCD_5CM`, `CCD_C34`, `CCD_5HC`, `CCD_6OG`,
    `CCD_6MA`, `CCD_1CC`, `CCD_8OG`, `CCD_5FC`, `CCD_3DR`

```json
{
  "dnaSequence": {
    "sequence": "GATTACA",

    "modifications": [
      {
        "modificationType": "CCD_6OG",
        "basePosition": 1
      },
      {
        "modificationType": "CCD_6MA",
        "basePosition": 2
      }
    ],

    "count": 1
  }
},
{
  "dnaSequence": {
    "sequence": "TGTAATC",
    "count": 1
  }
}
```

### RNA chains

`sequence` is a string containing RNA sequence (single strand); the same
limitations as in the UI are in place, e.g. only letters A, U, G, C are allowed.

`count` is a number of copies of this RNA chain (integer).

`modifications` is an optional list of dictionaries that carries descriptions of
the RNA chemical modifications.

*   `modificationType` is a string containing
    [CCD code](https://www.wwpdb.org/data/ccd) of modification; the same codes
    are allowed as in the UI.
*   `basePosition` is a position of the modified nucleotide (integer).
*   Allowed modifications: `CCD_PSU`, `CCD_5MC`, `CCD_OMC`, `CCD_4OC`,
    `CCD_5MU`, `CCD_OMU`, `CCD_UR3`, `CCD_A2M`, `CCD_MA6`, `CCD_6MZ`, `CCD_2MG`,
    `CCD_OMG`, `CCD_7MG`, `CCD_RSQ`

```json
{
  "rnaSequence": {
    "sequence": "GUAC",

    "modifications": [
      {
        "modificationType": "CCD_2MG",
        "basePosition": 1
      },
      {
        "modificationType": "CCD_5MC",
        "basePosition": 4
      }
    ],

    "count": 1
  }
}
```

### Ligands

`ligand` is a string containing the [CCD code](https://www.wwpdb.org/data/ccd)
of the ligand; the same codes are allowed as in the UI.

`count` is the number of copies of this ligand (integer).

Allowed ligands: `CCD_ADP`, `CCD_ATP`, `CCD_AMP`, `CCD_GTP`, `CCD_GDP`,
`CCD_FAD`, `CCD_NAD`, `CCD_NAP`, `CCD_NDP`, `CCD_HEM`, `CCD_HEC`, `CCD_PLM`,
`CCD_OLA`, `CCD_MYR`, `CCD_CIT`, `CCD_CLA`, `CCD_CHL`, `CCD_BCL`, `CCD_BCB`

```json
{
  "ligand": {
    "ligand": "CCD_ATP",
    "count": 1
  }
},
{
  "ligand": {
    "ligand": "CCD_HEM",
    "count": 2
  }
}
```

### Ions

`ion` is a string containing [CCD code](https://www.wwpdb.org/data/ccd) of the
ion; the same codes are allowed as in the UI. The ion charge is implicitly
specified by the CCD code.

`count` is a number of copies of this ion (integer).

Allowed ions: `MG`, `ZN`, `CL`, `CA`, `NA`, `MN`, `K`, `FE`, `CU`, `CO`

```json
{
  "ion": {
    "ion": "MG",
    "count": 2
  }
},
{
  "ion": {
    "ion": "NA",
    "count": 3
  }
}
```

# Additional modeling jobs

You may specify multiple jobs in one JSON file. This is an example of a simple
job request for one protein chain and two copies of the palindromic DNA
sequence:

```json
{
  "name": "Test Fold Job Number Two",
  "modelSeeds": [],
  "sequences": [
    {
      "proteinChain": {
        "sequence": "TEACHINGS",
        "count": 1
      }
    },
    {
      "dnaSequence": {
        "sequence": "TAGCTA",
        "count": 2
      }
    }
  ]
}
```