AutoStructure Theory: Difference between revisions

From NESG Wiki
Jump to navigation Jump to search
(Created page with ''''<span style="font-size:11.0pt;mso-bidi-font-size: 12.0pt;font-family:Arial">AutoStructure – An automated NOESY assignment engine.</span>''' '''<span style="font-size:11…')
 
No edit summary
Line 1: Line 1:
'''<span style="font-size:11.0pt;mso-bidi-font-size: 12.0pt;font-family:Arial">AutoStructure – An automated NOESY assignment engine.</span>'''
<span style="font-size:11.0pt;mso-bidi-font-size: 12.0pt;font-family:Arial">AutoStructure – An automated NOESY assignment engine.<font class="Apple-style-span" face="sans-serif" size="3"><span class="Apple-style-span" style="font-size: 13px;">&nbsp;</span></font><span class="Apple-style-span" style="font-family: sans-serif; font-size: 13px; "><span lang="FR" style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-ansi-language: FR">AutoStructure [1,2,3], written in C/C++ and Perl/Tk, uses a distinct bottom-up</span> topology-constrained approach for iterative NOE interpretation and structure determination. <span style="font-size:11.0pt;mso-bidi-font-size:12.0pt; font-family:Arial">AutoStructure first builds an initial chain fold based on
 
'''&lt;span style="font-size:11.0pt;mso-bidi-font-size:''' 12.0pt;font-family:Arial" /&gt;'''<span lang="FR" style="font-size:11.0pt;mso-bidi-font-size:12.0pt; font-family:Arial;mso-ansi-language:FR">AutoStructure </span><span lang="FR" style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-ansi-language: FR">[1,2,3]</span><span lang="FR" style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-ansi-language: FR">, written in C/C++ and Perl/Tk, uses a distinct bottom-up</span>''' topology-constrained approach for iterative NOE interpretation and structure determination. <span style="font-size:11.0pt;mso-bidi-font-size:12.0pt; font-family:Arial">AutoStructure first builds an initial chain fold based on
intraresidue and sequential NOESY data, together with characteristic NOE
intraresidue and sequential NOESY data, together with characteristic NOE
patterns of secondary structures, including helical medium-range NOE
patterns of secondary structures, including helical medium-range NOE
Line 9: Line 7:
methods are not used in the initial structure calculations.<span style="mso-spacerun: yes">&nbsp; </span>Once initial structures are generated and validated, additional NOESY cross peaks are iteratively assigned using the intermediate 3D structures and contact maps, together with knowledge of high-order topology constraints of alpha-helix and beta-sheet packing geometries </span><span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial">[82]</span><span style="font-size: 11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial">. This protocol, in
methods are not used in the initial structure calculations.<span style="mso-spacerun: yes">&nbsp; </span>Once initial structures are generated and validated, additional NOESY cross peaks are iteratively assigned using the intermediate 3D structures and contact maps, together with knowledge of high-order topology constraints of alpha-helix and beta-sheet packing geometries </span><span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial">[82]</span><span style="font-size: 11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial">. This protocol, in
principle, resembles the method that an expert would utilize in manually
principle, resembles the method that an expert would utilize in manually
solving a protein structure by NMR.<span style="mso-spacerun: yes">&nbsp;&nbsp;</span></span><!--StartFragment-->
solving a protein structure by NMR.<span style="mso-spacerun: yes">&nbsp;&nbsp;</span></span></span></span>
 
<span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial">&lt;o:p&gt;&nbsp;&lt;/o:p&gt;</span>  


<!--[if gte vml 1]><v:shapetype
<span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial">&lt;o:p&gt;&nbsp;&lt;/o:p&gt;</span> <!--[if gte vml 1]><v:shapetype
  id="_x0000_t202" coordsize="21600,21600" o:spt="202" path="m0,0l0,21600,21600,21600,21600,0xe">
  id="_x0000_t202" coordsize="21600,21600" o:spt="202" path="m0,0l0,21600,21600,21600,21600,0xe">
  <v:stroke joinstyle="miter"/>
  <v:stroke joinstyle="miter"/>
Line 74: Line 70:
  <v:textbox style='mso-rotate-with-shape:t'/>
  <v:textbox style='mso-rotate-with-shape:t'/>
  <w:wrap type="tight"/>
  <w:wrap type="tight"/>
</v:shape><![endif]-->[[Image:]]&lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt;  
</v:shape><![endif]-->[[Image:]]&lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt; &lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt; &lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt; &lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt; &lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt; &lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt; &lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt; &lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt; &lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt; <span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes">This ‘bottom up’ strategy is quite different from the “top down”
 
&lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt;  
 
&lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt;  
 
&lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt;  
 
&lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt;  
 
&lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt;  
 
&lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt;  
 
&lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt;  
 
&lt;span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /&gt;  
 
<span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes">This</span><span style="font-size:11.0pt;mso-bidi-font-size:12.0pt; font-family:Arial"> ‘bottom up’ strategy is quite different from the “top down”
strategies used by the alternative programs CANDID and ARIA, which rely on
strategies used by the alternative programs CANDID and ARIA, which rely on
“ambiguous constraints”.<span style="mso-spacerun: yes">&nbsp; </span>For NOESY spectra with poor signal-to-noise ratios, such automatically assigned ‘ambiguous constraint” sets may not include any true NOESY assignments, and result in distortions of the protein structure which can be avoided by the “bottom up” approach of AutoStructure </span><!--[if supportFields]><span
“ambiguous constraints”.<span style="mso-spacerun: yes">&nbsp; </span>For NOESY spectra with poor signal-to-noise ratios, such automatically assigned ‘ambiguous constraint” sets may not include any true NOESY assignments, and result in distortions of the protein structure which can be avoided by the “bottom up” approach of AutoStructure </span><!--[if supportFields]><span
Line 175: Line 153:
style='mso-element:field-end'></span></span><![endif]--><span style="font-size: 11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial">. The AutoStructure program
style='mso-element:field-end'></span></span><![endif]--><span style="font-size: 11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial">. The AutoStructure program
has been used to determine 3D structures for most of the &gt; 300 proteins
has been used to determine 3D structures for most of the &gt; 300 proteins
solved by the NESG consortium.&lt;o:p&gt;&lt;/o:p&gt;</span>  
solved by the NESG consortium.&lt;o:p&gt;&lt;/o:p&gt;</span> <span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial">&lt;o:p&gt;&nbsp;&lt;/o:p&gt;</span> <span>Fig. 4 shows AutoStructure results for three different human protein NMR
 
<span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial">&lt;o:p&gt;&nbsp;&lt;/o:p&gt;</span>  
 
<span>Fig. 4 shows AutoStructure results for three different human protein NMR
test data sets: FGF-2, IL-13 and MMP-1, ranging in size from 113 to 169
test data sets: FGF-2, IL-13 and MMP-1, ranging in size from 113 to 169
amino-acid residues. The mean coordinate differences between structures
amino-acid residues. The mean coordinate differences between structures
determined by AutoStructure and by manual analysis (0.5 to 0.8 Å for backbone
determined by AutoStructure and by manual analysis (0.5 to 0.8 Å for backbone
atoms of ordered residues) demonstrate good accuracy of these automated
atoms of ordered residues) demonstrate good accuracy of these automated
methods. <span style="color:blue"><span style="mso-spacerun: yes">&nbsp;</span></span>The input data for AutoStructure are: (i) resonance assignment table, (ii) 2D, 3D, and/or 4D NOESY peak lists, (iii) list of scalar coupling, RDC and slow amide exchange data. AutoStructure generates distance constraint lists and utilizes the programs DYANA/CYANA</span><span>, Xplor&nbsp;</span><span>for 3D structure
methods. <span style="color:blue"><span style="mso-spacerun: yes">&nbsp;</span></span>The input data for AutoStructure are: (i) resonance assignment table, (ii) 2D, 3D, and/or 4D NOESY peak lists, (iii) list of scalar coupling, RDC and slow amide exchange data. AutoStructure generates distance constraint lists and utilizes the programs DYANA/CYANA, Xplor&nbsp;</span><span>for 3D structure
generation on a Linux-based computer cluster.</span><!--EndFragment-->
generation on a Linux-based computer cluster.</span><!--EndFragment-->

Revision as of 21:30, 17 December 2009

AutoStructure – An automated NOESY assignment engine. AutoStructure [1,2,3], written in C/C++ and Perl/Tk, uses a distinct bottom-up topology-constrained approach for iterative NOE interpretation and structure determination. AutoStructure first builds an initial chain fold based on intraresidue and sequential NOESY data, together with characteristic NOE patterns of secondary structures, including helical medium-range NOE interactions and interstrand b-sheet NOE interactions, and unambiguous long-range NOE interactions, based on chemical shift matching and NOESY spectral symmetry considerations. NOESY cross peaks that cannot be uniquely assigned using these methods are not used in the initial structure calculations.  Once initial structures are generated and validated, additional NOESY cross peaks are iteratively assigned using the intermediate 3D structures and contact maps, together with knowledge of high-order topology constraints of alpha-helix and beta-sheet packing geometries [82]. This protocol, in principle, resembles the method that an expert would utilize in manually solving a protein structure by NMR.  

<o:p> </o:p> [[Image:|Text Box: Fig. 4. Ribbon diagrams of representative structures of FGF-2, MMP-1 and IL-13 proteins used for the validation of the AutoStructure process: (a) final structures from AutoStructure using XPLOR for stucture generation, (b) manual-analyzed structures deposited in PDB, analyzed using the same NMR data set, (c) structures determined by X-ray crystallography or third NMR group. Tabulated on the right are mean coordinate differences (Å) in secondary structure regions for backbone atoms between structures (a), (b) and (c). ]][[Image:]]<span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /> <span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /> <span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /> <span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /> <span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /> <span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /> <span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /> <span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /> <span style="font-size:11.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;mso-no-proof: yes" /> This ‘bottom up’ strategy is quite different from the “top down” strategies used by the alternative programs CANDID and ARIA, which rely on “ambiguous constraints”.  For NOESY spectra with poor signal-to-noise ratios, such automatically assigned ‘ambiguous constraint” sets may not include any true NOESY assignments, and result in distortions of the protein structure which can be avoided by the “bottom up” approach of AutoStructure [4].  CANDID/CYANA also uses a ‘network anchoring” approach similar to, but less comprehensive than, the topology-constrained approach used by AutoStructure [4].  For these reasons, some users may prefer to use both AutoStructure and CANDID/CYANA or ARIA in parallel to assess potential errors in automated NOESY cross peak assignments [83]. The AutoStructure program has been used to determine 3D structures for most of the > 300 proteins solved by the NESG consortium.<o:p></o:p> <o:p> </o:p> Fig. 4 shows AutoStructure results for three different human protein NMR test data sets: FGF-2, IL-13 and MMP-1, ranging in size from 113 to 169 amino-acid residues. The mean coordinate differences between structures determined by AutoStructure and by manual analysis (0.5 to 0.8 Å for backbone atoms of ordered residues) demonstrate good accuracy of these automated methods.  The input data for AutoStructure are: (i) resonance assignment table, (ii) 2D, 3D, and/or 4D NOESY peak lists, (iii) list of scalar coupling, RDC and slow amide exchange data. AutoStructure generates distance constraint lists and utilizes the programs DYANA/CYANA, Xplor for 3D structure generation on a Linux-based computer cluster.