z-logo
Premium
A consensus prediction of the secondary structure for the 6‐phospho‐β‐ D ‐galactosidase superfamily
Author(s) -
Gerloff Dietlind L.,
Benner Steven A.
Publication year - 1995
Publication title -
proteins: structure, function, and bioinformatics
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.699
H-Index - 191
eISSN - 1097-0134
pISSN - 0887-3585
DOI - 10.1002/prot.340210402
Subject(s) - protein secondary structure , protein structure prediction , protein superfamily , computational biology , biology , sequence (biology) , superfamily , protein structure , divergence (linguistics) , protein family , sequence alignment , protein tertiary structure , evolutionary biology , genetics , peptide sequence , biochemistry , gene , linguistics , philosophy
Abstract Two separate unrefined models for the secondary structure of two subfamilies of the 6‐phospho‐β‐ D ‐galactosidase superfamily were independently constructed by examining patterns of variation and conservation within homologous protein sequences, assigning surface, interior, parsing, and active site residues to positions in the alignment, and identifying periodicities in these. A consensus model for the secondary structure of the entire superfamily was then built. The prediction tests the limits of an unrefined prediction made using this approach in a large protein with substantial functional and sequence divergence within the family. The protein belongs to the (α–β class), with the core β strands aligned parallel. The supersecondary structural elements that are readily identified in this model is a parallel β sheet built by strands C, D, and E, with helices 2 and 3 connecting strands (C + D) and (D + E), respectively, and an analogous α–β unit (strand G and helix 7) toward the end of the sequence. The resemblance of the supersecondary model to the tertiary structure formed by 8‐fold α–β barrel proteins is almost certainly not coincidental. © 1995 Wiley‐Liss, Inc.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here