ChemRxiv
These are preliminary reports that have not been peer-reviewed. They should not be regarded as conclusive, guide clinical practice/health-related behavior, or be reported in news media as established information. For more information, please see our FAQs.
1/1
2 files

Learning Protein-Ligand Binding Affinity with Atomic Environment Vectors

preprint
submitted on 21.12.2020, 15:58 and posted on 22.12.2020, 13:16 by Rocco Meli, Andrew Anighoro, Mike Bodkin, Garrett Morris, Philip Biggin

Scoring functions for the prediction of protein-ligand binding affinity have seen renewed interest in recent years when novel machine learning and deep learning methods started to consistently outperform classical scoring functions. Here we explore the use of atomic environment vectors (AEVs) and feed-forward neural networks, the building blocks of several neural network potentials, for the prediction of protein-ligand binding affinity. The AEV-based scoring function, which we term AEScore, is shown to perform as well or better than other state-of-the-art scoring functions on binding affinity prediction, with an RMSE of 1.22 pK units and a Pearson’s correlation coefficient of 0.83 for the CASF-2016 benchmark. However, AEScore does not perform as well in docking and virtual screening tasks. We therefore show that the model can be combined with the classical scoring function AutoDock Vina in the context of ∆-learning, where corrections to the AutoDock Vina scoring function are learned instead of the protein-ligand binding affinity itself. Combined with AutoDock Vina, ∆-AEScore has an RMSE of 1.32 pK units and a Pearson’s correlation coefficient of 0.80 on the CASF-2016 benchmark, while retaining the good docking and screening power of the underlying classical scoring function.

Funding

BBSRC (BB/MO11224/1)

National Productivity Investment Fund (BB/S507760X/1)

History

Email Address of Submitting Author

philip.biggin@bioch.ox.ac.uk

Institution

University of Oxford

Country

United Kingdom

ORCID For Submitting Author

0000-0001-5100-8836

Declaration of Conflict of Interest

The authors declare no conflict of interest

Version Notes

This is version 1.

Exports