| Literature DB >> 28324365 |
Conan K Wang1, Andreas Hofmann2,3.
Abstract
The mapping of secondary structure elements onto amino acid sequences enhances the quality of alignments frequently used in phylogenetic, genomic and transcriptomic studies, as well as in molecular modelling. Here, we report recent updates to the Java application SBAL, an integrated tool to generate, edit, visualise and analyse secondary structure-based sequence alignments. The main goal of the software is to streamline the work flow in generation of structure-based alignments, and we have thus implemented the option to import and visualise sequence and structure information directly from any PDB file. The new feature is achieved by a Java application named ASSP which follows the original framework of the well-established dictionary of protein secondary structure by Kabsch and Sander. ASSP is also available as a stand-alone application. Other major additions to SBAL include the calculation of distance matrices, peptide properties, as well as detailed on-line tutorials for typical applications.Entities:
Keywords: Modelling; Structure analysis; Structure-based amino acid sequence alignments
Year: 2014 PMID: 28324365 PMCID: PMC4327748 DOI: 10.1007/s13205-014-0222-0
Source DB: PubMed Journal: 3 Biotech ISSN: 2190-5738 Impact factor: 2.406
Fig. 1Screen shots of importing PDB file 4mdu (Leow et al. 2014) into SBAL. Top panel SBAL recognises the presence of different chains in the file and prompts the user to choose which chain should be imported. Middle panel If the starting residue number differs from ‘1’, the user can choose to retain the residue numbering as in the PDB file or re-number from 1. Bottom panel Since the PDB file did not have any ‘HELIX’/‘SHEET’ records, SBAL automatically assigns secondary structure using the embedded version of ASSP. Helical structure is indicated in green, β-strands are coloured red
Distribution of assigned secondary structure types (‘summary’) in the benchmarking dataset analysed with DSSP and ASSP
| DSSP assignment | ASSP assignment | |||||||
|---|---|---|---|---|---|---|---|---|
| None | B | E | G | H | I | S | T | |
| None | 5,264 | 150 | 179 | 5 | 23 | 0 | 0 | 5 |
| B | 76 | 156 | 28 | 0 | 2 | 0 | 48 | 11 |
| E | 245 | 49 | 5,342 | 2 | 0 | 3 | 73 | 16 |
| G | 24 | 0 | 0 | 909 | 9 | 2 | 160 | 201 |
| H | 3 | 0 | 0 | 547 | 9,016 | 104 | 78 | 74 |
| I | 0 | 0 | 0 | 0 | 0 | 24 | 0 | 0 |
| S | 0 | 0 | 16 | 3 | 4 | 0 | 2,235 | 0 |
| T | 15 | 5 | 0 | 244 | 81 | 38 | 56 | 2,549 |
Fig. 2Excerpt from the secondary structure analysis of the same PDB file as in Fig. 1 with DSSP (top section), and ASSP (middle and bottom sections). The type of information reported by ASSP is the same as that of DSSP. The middle section shows a report generated by ASSP mimicking the DSSP output format with relative referencing of residues. For user convenience, ASSP can also produce reports where residues are referenced with their absolute names, i.e. chain identifier and residue number as in the PDB file (bottom section)
Comparison of simplified ASSP and DSSP secondary structure assignment results obtained with the benchmarking dataset
| Sec. structure | DSSP | ASSP | Agreement |
|---|---|---|---|
| Unstructured | 11,193 | 10,204 | 0.912 |
| Helical | 11,151 | 9,949 | 0.892 |
| Extended | 5,730 | 5,342 | 0.932 |