Is the growth rate of Protein Data Bank sufficient to solve the protein structure prediction problem using template-based modeling? release_do3bulu5qrdvnn24tocjbwfjom

by Michal Brylinski

Published in Bio-Algorithms and Med-Systems by Walter de Gruyter GmbH.

2015   Volume 11, p1-7

Abstract

<jats:title>Abstract</jats:title>The Protein Data Bank (PDB) undergoes an exponential expansion in terms of the number of macromolecular structures deposited every year. A pivotal question is how this rapid growth of structural information improves the quality of three-dimensional models constructed by contemporary bioinformatics approaches. To address this problem, we performed a retrospective analysis of the structural coverage of a representative set of proteins using remote homology detected by COMPASS and HHpred. We show that the number of proteins whose structures can be confidently predicted increased during a 9-year period between 2005 and 2014 on account of the PDB growth alone. Nevertheless, this encouraging trend slowed down noticeably around the year 2008 and has yielded insignificant improvements ever since. At the current pace, it is unlikely that the protein structure prediction problem will be solved in the near future using existing template-based modeling techniques. Therefore, further advances in experimental structure determination, qualitatively better approaches in fold recognition, and more accurate template-free structure prediction methods are desperately needed.
In application/xml+jats format

Archived Files and Locations

application/pdf   655.7 kB
file_5e2w5n3ztrcchgsid34da7ekxi
application/pdf   656.3 kB
file_tywa4uybffgb5ffiaxsokwjqvq
web.archive.org (webarchive)
pdfs.semanticscholar.org (aggregator)
Read Archived PDF
Preserved and Accessible
Type  article-journal
Stage   published
Date   2015-01-31
Container Metadata
Not in DOAJ
In Keepers Registry
ISSN-L:  1895-9091
Work Entity
access all versions, variants, and formats of this works (eg, pre-prints)
Catalog Record
Revision: d04b8b16-672d-46f1-8f21-41f392169a52
API URL: JSON