Protein-Ligand Benchmark Dataset for testing Parameters and Methods of Free Energy Calculations.
Documentation for the openforcefield toolkit is hosted at readthedocs.
The data is organized as followed:
data
├── targets.yml # list of all targets and their directories
├── <date>_<target_name_1> # directory for target 1
│ ├── 00_data # metadata for target 1
│ │ ├── edges.yml # edges/perturbations
│ │ ├── ligands.yml # ligands and activities
│ │ └── target.yml # target
│ ├── 01_protein # protein data
│ │ ├── crd # coordinates
│ │ │ ├── protein.pdb # aminoacid residues
│ │ │ └── cofactors_crystalwater.pdb # cofactors and cyrstal waters
│ │ └── top # topology(s)
│ │ │ └── amber99sb-star-ildn-mut.ff # force field spec.
│ │ │ ├── topol.itp # Gromacs ITP file
│ │ │ └── topol.top # Gromacs TOP file
│ └── 02_ligands # ligands
│ ├── lig_<name_1> # ligand 1
│ │ ├── crd # coordinates
│ │ │ └── lig_<name_1>.sdf # SDF file
│ │ └── top # topology(s)
│ │ └── openff-1.0.0.offxml # force field spec.
│ │ ├── fflig_<name_1>.itp # Gromacs ITP file : atom types
│ │ ├── lig_<name_1>.itp # Gromacs ITP file
│ │ ├── lig_<name_1>.top # Gromacs TOP file
│ │ └── posre_lig_<name_1>.itp # Gromacs ITP file : position restraint file
│ ├── lig_<name_2> # ligand 2
│ …
│ └── 03_hybrid # edges (perturbations)
│ ├── edge_<name_1>_<name_2> # edge between ligand 1 and ligand 2
│ │ └── water # edge in water
│ │ ├── crd # coordinates
│ │ │ ├── mergedA.pdb # merged conf based on coords of ligand 1
│ │ │ ├── mergedB.pdb # merged conf based on coords of ligand 2
│ │ │ ├── pairs.dat # atom mapping
│ │ │ └── score.dat # similarity score
│ │ └── top # topology(s)
│ │ └── openff-1.0.0.offxml # force field spec.
│ │ ├── ffmerged.itp # Gromacs ITP file
│ │ ├── ffMOL.itp # Gromacs ITP file
│ │ └── merged.itp # Gromacs ITP file
│ …
├── <date>_<target_name_2> # directory for target 2
…
This file lists all the registered targets in the benchmark set. Each entry denotes one target and contains the following information:
mcl1_sample:
name: mcl1_sample
date: 2020-08-26
dir: 2020-08-26_mcl1_sample
mcl1_sample is the entry name and each entry has three sub-entries:
nameis the target name, which is usually the same as the entry name of the target.dateis the date when the target was initially added to the benchmark set.diris the directory name where all the data for the target is found. Usually it is thedateand thenamefield, connected by a underscore_.
This file is found in the meta data directory of each target: <date>_<target_name>/00_data/target.yml. It contains additionally information about the target:
alternate:
iridium_classifier: HT
iridium_score: 0.3
pdb: 6O6F
associated_sets:
- Schrodinger JACS
comments: hydrophobic interactions contributing to binding
date: 2019-12-13
dpi: 0.26
id: 9
iridium_classifier: HT
iridium_score: 0.41
name: mcl1
netcharge: 4 e
pdb: 4HW3
references:
calculation:
- 10.1021/ja512751q
- 10.1021/acs.jcim.9b00105
- 10.1039/C9SC03754C
measurement:
- 10.1021/jm301448p
Explanation of the entries:
alternate: Alternate X-ray structure which could be usediridium_classifier: Iridium classifier of the alternate structureiridium_score: Iridium score of the alternate structurepdb: PDB ID of the alternate structure
associated_sets: list of benchmark set tags, where this target is in (e.g."Schrodinger JACS")comments: hydrophobic interactions contributing to bindingdate: date when the target was initially added to the benchmark set.dpi: diffraction precision index of the used structure (quality metric for the structure)id: a given IDiridium_classifier: Iridium classifier of the used structureiridium_score: Iridium score of the used structurename: name/identifier of the targetnetcharge: total charge of the prepared protein (this should be equalized with counter ions during preparation of the simulation system)pdb: PDB ID of the used structurereferences: doi to referencescalculation: list of references where this target was used in calculationsmeasurement: list of references of affinity measurements
This file is found in the meta data directory of each target: <date>_<target_name>/00_data/ligands.yml. It contains information of the ligand of one target. The entries of the ligands are separated by three dashes (---). One entry looks like this:
measurement:
comment: Table 2, entry 23
doi: 10.1021/jm301448p
ki:
- 0.37
- 0.03
- uM
name: lig_23
smiles: '[H]c1c(c(c2c(c1[H])c(c(c(c2OC([H])([H])C([H])([H])C([H])([H])C3=C(Sc4c3c(c(c(c4[H])[H])[H])[H])C(=O)[O-])[H])[H])[H])[H])[H]'
---
Explanation of the entries:
measurement: affinity measurement entrycomment: comment about the measurementdoi: DOI (digital object identifier) pointing to the reference for this measurementki: binding constant Ki, being a list of value, error and the unit of the measurement. The error is-1, if it is not given in the reference. Instead ofki,ic50(IC50 value),pic50(pIC50 value), ordg(free energy of binding) are accepted entries.
name: name of ligand, which always starts withlig_, followed by a unique identifier.smiles: SMILES string of the ligand, with charge state information and chirality information.
This file is found in the meta data directory of each target: <date>_<target_name>/00_data/edges.yml. It contains information of the edges of one target. The entries of the ligands are separated by three dashes (---). One entry looks like this:
- 50
- 60
---
Each entry is just a list of two ligand identifiers.
Releases follow the major.minor.micro scheme recommended by PEP440, where
majorincrements denote a change that may break API compatibility with previous major releasesminorincrements denote addition of new targets or addition and larger changes to the APImicroincrements denote bugfixes, addition of API features, changes of coordinates or topologies, and changes of metadata
MIT. See the License File for more information.
CC-BY-4.0 for data (content of directory data. See the License File for more information.
Copyright (c) 2019, Open Force Field Consortium, David F. Hahn
Project based on the Computational Molecular Science Python Cookiecutter version 1.1.