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
|
Structure comparison examples
=============================
OpenStructure provides "actions" for general benchmarking use cases.
* **compare-structures**: Focuses on comparisons involving polymer entities, i.e.
protein, DNA and RNA chains
* **compare-ligand-structures**: Focuses on comparisons of interactions between
polymer entities and non-polymer entities, i.e. small molecule ligands
# Before doing any scoring
Pull example data from the repository:
```
wget https://git.scicore.unibas.ch/schwede/openstructure/-/archive/master/openstructure-master.zip?path=examples/scoring -O example.zip
unzip -j example.zip
```
# Run the examples
The example commands here assume an OpenStructure installation
([compile instructions](https://openstructure.org/docs/install/)).
To simplify the setup, we recommend Conda or containers instead of compiling
OpenStructure from source. Instructions for setup and
running equivalent computations are available below for
* [Conda](#conda)
* [Docker](#docker)
* [Singularity](#singularity)
A detailed list of options can be found in the
[action documentation](https://openstructure.org/docs/actions/).
Alternatively, the commands
```
ost compare-structures -h
ost compare-ligand-structures -h
```
will list all available options of the respective action. Both actions compute
scores on an “opt-in” basis and produce output in JSON format. Example to compute
global and per-residue LDDT scores, as well as as QS-scores which are written to
default output (out.json):
```
ost compare-structures -m model.pdb -r reference.cif.gz --lddt --local-lddt --qs-score
```
Results should be computed within seconds and saved in the `out.json` file
([see example output](compare-structures_example_out.json)). We refer to the
[action documentation](https://openstructure.org/docs/actions/) for in-depth
description of the provided data items and description of optional flags that
compute additional scores.
By default, model-reference chains are aligned using Needleman-Wunsch.
Many benchmarking efforts such as CASP and CAMEO assume residue numbers
according to target sequence(s). Both "actions" allow to derive model-reference
chain alignments according to these numbers which should be preferred in these
cases. This can be enabled by adding a `-rna` (residue number alignment) flag:
```
ost compare-structures -m model.pdb -r reference.cif.gz --lddt --local-lddt --qs-score -rna
```
The same example also contains small molecule ligands.
We can compute LDDT-PLI and BiSyRMSD with:
```
ost compare-ligand-structures -m model.pdb -r reference.cif.gz -ml *.sdf --rmsd --lddt-pli -rna
```
Results should be computed within seconds and saved in the `out.json` file
([See example output ](compare-ligand-structures_example_out.json)). We refer
to the action documentation for in-depth description of the provided data
items.
Again, it is advised to use the `-rna` flag if applicable. In this example,
reference ligands are directly extracted from the provided mmCIF file based on
"non-polymer" entity types.
This only works in case of mmCIF input AND if the respective ligand is in the
PDB component dictionary which defines connectivity (matching based on compound
name).
Container solutions come with such a dictionary which has been created at build
time. Check the detailed
[Docker](https://git.scicore.unibas.ch/schwede/openstructure/tree/master/docker)/[Singularity](https://git.scicore.unibas.ch/schwede/openstructure/tree/master/singularity)
instructions on how to set the latest dictionary, i.e. "Compound Library".
You can override automatic extraction by providing SDF files with ligand
coordinates and connectivity information. If the receptor is provided in
PDB format, ligands must be provided in SDF format.
# Conda
OpenStructure is available as a [conda package on
Bioconda](https://bioconda.github.io/recipes/openstructure/README.html)
Installing OpenStructure in Conda is as easy as:
```
conda install -c conda-forge bioconda::openstructure
```
Commands can be run as usual. Tested with [miniforge](https://conda-forge.org/miniforge/).
# Docker
For complete documentation on using Docker with OpenStructure,
[click here](https://git.scicore.unibas.ch/schwede/openstructure/tree/master/docker).
This section provides a quick-start guide to help you get up and running with scoring using Docker.
Get the latest Docker image from the OpenStructure registry:
```
sudo docker pull registry.scicore.unibas.ch/schwede/openstructure:latest
```
run one of the scoring examples, other examples need to be adapted accordingly:
```
sudo docker run --rm -v $(pwd):/home registry.scicore.unibas.ch/schwede/openstructure:latest compare-structures -m model.pdb -r reference.cif.gz --lddt --local-lddt --qs-score
```
# Singularity
For complete documentation on using Singularity with OpenStructure,
[click here](https://git.scicore.unibas.ch/schwede/openstructure/tree/master/singularity).
This section provides a quick-start guide to help you get up and running with scoring using Singularity.
Building the singularity container requires root permissions:
```
wget https://git.scicore.unibas.ch/schwede/openstructure/-/raw/master/singularity/Singularity
sudo singularity build ost.img Singularity
```
run one of the scoring examples, other examples need to be adapted accordingly:
```
singularity run --app OST ost.img compare-structures -m model.pdb -r reference.cif.gz --lddt --local-lddt --qs-score
```
|
