Resonance Assignment/Abacus/Spin systems format: Difference between revisions

From NESG Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
<div>Not assigned spin-systems (PB fragments) could be loaded in FMCGUI using only one, "standad", format.</div><div>Assigned chemical shifts (spin-systems) could be loaded using&nbsp;two different formats, standard and cyana format.</div><div>&nbsp;</div><div>'''1. PB-fragments in standard format.'''</div><div></div><div></div><div>Each fragment is represented by a number of lines. The groups of lines corresponding to different fragments are separated by empty line. </div><div>The line that follow the last fragment should have 'Q' at the first position.</div><div>&nbsp;</div><div>A fragment is described as follows:</div><div><span><font size="2"></font></span></div><div></div><div><span><font size="2"></font></span></div><div><span><font size="2">&nbsp;</font></span>Here, the first line specify user ID, 1-letter residue type ('X' if not known), the number of the following lines (regading the fragment), and chemical shift of backbone C' atom ( should be '0.000' if it is not known). </div><div>&nbsp;</div><div>The fragments user ID could be any digit number &lt; 500. There is no restriction on the order of fragments in the input&nbsp;file.</div><div>&nbsp;</div><div>''<font size="2">Example</font>''<font size="2">1.1. Not assigned PB-fragments.</font></div><div><font size="2"></font></div><div><font size="2"></font></div><div>'''2. Assigned AA-fragments in standard format.''' </div><div></div><div></div><div></div><div>AA-fragments should be ordered in the input file according to their assignment to </div><div>protein sequence positions. </div><div>Each fragment is described as follows:</div><div></div><div></div><div>Here, the first line specifies&nbsp; protein sequence position to which the fragment is assigned, 1-letter amino acid type, the number of the following lines describing the fragment, chemical shift of backbone C' atom, and user ID of the fragment.The last number, user ID, is optional.</div><div></div><div></div><div>&nbsp;</div><div>''<font size="2">Example</font>''<font size="2">2.1. Assigned AA-fragments with user ID specified.</font></div><div><font size="2"></font><div><font size="2">''<font size="2"></font>''</font></div></div>
<div>Not assigned spin-systems (PB fragments) could be loaded in FMCGUI using only one, "standad", format.</div><div>Assigned chemical shifts (spin-systems) could be loaded using&nbsp;two different formats, standard and cyana format.</div><div>&nbsp;</div><div>'''1. PB-fragments in standard format.'''</div><div></div><div></div><div>Each fragment is represented by a number of lines. The groups of lines corresponding to different fragments are separated by empty line. </div><div>The line that follow the last fragment should have 'Q' at the first position.</div><div>&nbsp;</div><div>A fragment is described as follows:</div><div></div><pre>31 X&nbsp;&nbsp;&nbsp; 7&nbsp;&nbsp;&nbsp;&nbsp; 0.000&nbsp;
&nbsp;&nbsp; 9.025&nbsp; HN&nbsp;&nbsp;&nbsp; 106.560&nbsp; N
&nbsp;&nbsp; 5.221&nbsp; HA&nbsp;&nbsp;&nbsp;&nbsp; 55.302&nbsp; CA
&nbsp;&nbsp; 1.940&nbsp; HB*&nbsp;&nbsp;&nbsp; 33.679&nbsp; CB
&nbsp;&nbsp; 1.480&nbsp; HG1&nbsp;&nbsp;&nbsp; 27.976&nbsp; CG
&nbsp;&nbsp; 1.775&nbsp; HG2&nbsp;&nbsp;&nbsp; 27.976&nbsp; CG
&nbsp;&nbsp; 2.943&nbsp; HD1&nbsp;&nbsp;&nbsp; 43.958&nbsp; CD
&nbsp;&nbsp; 3.205&nbsp; HD2&nbsp;&nbsp;&nbsp; 43.958&nbsp; CD
</pre><div></div><div>&nbsp;31 X&nbsp;&nbsp;&nbsp; 7&nbsp;&nbsp;&nbsp;&nbsp; 0.000&nbsp; <br>&nbsp;&nbsp; 9.025&nbsp; HN&nbsp;&nbsp;&nbsp; 106.560&nbsp; N <br>&nbsp;&nbsp; 5.221&nbsp; HA&nbsp;&nbsp;&nbsp;&nbsp; 55.302&nbsp; CA <br>&nbsp;&nbsp; 1.940&nbsp; HB*&nbsp;&nbsp;&nbsp; 33.679&nbsp; CB <br>&nbsp;&nbsp; 1.480&nbsp; HG1&nbsp;&nbsp;&nbsp; 27.976&nbsp; CG <br>&nbsp;&nbsp; 1.775&nbsp; HG2&nbsp;&nbsp;&nbsp; 27.976&nbsp; CG <br>&nbsp;&nbsp; 2.943&nbsp; HD1&nbsp;&nbsp;&nbsp; 43.958&nbsp; CD <br>&nbsp;&nbsp; 3.205&nbsp; HD2&nbsp;&nbsp;&nbsp; 43.958&nbsp; CD <br></div><div></div><div><span><font size="2"></font></span></div><div></div><div><span><font size="2"></font></span></div><div><span><font size="2">&nbsp;</font></span>Here, the first line specify user ID, 1-letter residue type ('X' if not known), the number of the following lines (regading the fragment), and chemical shift of backbone C' atom ( should be '0.000' if it is not known). </div><div>&nbsp;</div><div>The fragments user ID could be any digit number &lt; 500. There is no restriction on the order of fragments in the input&nbsp;file.</div><div>&nbsp;</div><div>''<font size="2">Example</font>''<font size="2">1.1. Not assigned PB-fragments.</font></div><div><font size="2"></font></div><div><font size="2"></font></div><div><font size="2"></font></div><div><font size="2"></font></div><div>'''2. Assigned AA-fragments in standard format.''' </div><div></div><div></div><div></div><div>AA-fragments should be ordered in the input file according to their assignment to </div><div>protein sequence positions. </div><div>Each fragment is described as follows:</div><div></div><div></div><div>Here, the first line specifies&nbsp; protein sequence position to which the fragment is assigned, 1-letter amino acid type, the number of the following lines describing the fragment, chemical shift of backbone C' atom, and user ID of the fragment.The last number, user ID, is optional.</div><div></div><div></div><div>&nbsp;</div><div>''<font size="2">Example</font>''<font size="2">2.1. Assigned AA-fragments with user ID specified.</font></div><div><font size="2"></font></div><div><font size="2"></font></div><div><font size="2"></font><div><font size="2">''<font size="2"></font>''</font></div></div>
<font size="2"><div><font size="2"></font></div><div><font size="2"></font></div><div><font size="2"></font></div><div><font size="2"></font></div><div><font size="2"></font></div><div><font size="2"></font></div><div>''<font size="2"></font>''</div><div>''<font size="2">Example</font>''<font size="2">2.2. Assigned AA-fragments without user ID specified.</font></div><div><font size="2"></font></div><div><font size="2"></font></div></font>
<font size="2"><div><font size="2"></font></div><div><font size="2"></font></div><div><font size="2"></font></div><div><font size="2"></font></div><div><font size="2"></font></div><div><font size="2"></font></div><div>''<font size="2"></font>''</div><div>''<font size="2">Example</font>''<font size="2">2.2. Assigned AA-fragments without user ID specified.</font></div><div><font size="2"></font></div><div><font size="2"></font></div></font>
<div>'''<span style="display: none" />'''</div><div>'''<span id="1259349916483S" style="display: none">&nbsp;</span>3. CYANA chemical shift file (prot-file).'''</div><div></div><div></div><div>Assigned chemical shifts caould be loaded in FMCGUI and automatically transformed in a set of assigned PB-frsagments.</div><div></div><div></div><div></div><div>''<font size="2">Example</font>''<font size="2">3.1. Assigned chemical shifts.</font></div><div><font size="2"></font></div><div></div><div></div>
<div</div><div</div><</div><div>'''<span id="1259349916483S" style="display: none">&nbsp;</span>3. CYANA chemical shift file (prot-file).'''</div><div></div><div></div><div>Assigned chemical shifts caould be loaded in FMCGUI and automatically transformed in a set of assigned PB-frsagments.</div><div></div><div></div><div></div><div></div><div>''<font size="2">Example</font>''<font size="2">3.1. Assigned chemical shifts.</font></div><div><font size="2"></font></div><div><font size="2"></font></div><div><font size="2"></font></div><div><font size="2"></font></div><div></div><div></div>

Revision as of 19:39, 27 November 2009

Not assigned spin-systems (PB fragments) could be loaded in FMCGUI using only one, "standad", format.
Assigned chemical shifts (spin-systems) could be loaded using two different formats, standard and cyana format.
 
1. PB-fragments in standard format.
Each fragment is represented by a number of lines. The groups of lines corresponding to different fragments are separated by empty line.
The line that follow the last fragment should have 'Q' at the first position.
 
A fragment is described as follows:
31 X    7     0.000  
   9.025  HN    106.560  N 
   5.221  HA     55.302  CA 
   1.940  HB*    33.679  CB 
   1.480  HG1    27.976  CG 
   1.775  HG2    27.976  CG 
   2.943  HD1    43.958  CD 
   3.205  HD2    43.958  CD
 31 X    7     0.000 
   9.025  HN    106.560  N
   5.221  HA     55.302  CA
   1.940  HB*    33.679  CB
   1.480  HG1    27.976  CG
   1.775  HG2    27.976  CG
   2.943  HD1    43.958  CD
   3.205  HD2    43.958  CD
 Here, the first line specify user ID, 1-letter residue type ('X' if not known), the number of the following lines (regading the fragment), and chemical shift of backbone C' atom ( should be '0.000' if it is not known).
 
The fragments user ID could be any digit number < 500. There is no restriction on the order of fragments in the input file.
 
Example1.1. Not assigned PB-fragments.
2. Assigned AA-fragments in standard format.
AA-fragments should be ordered in the input file according to their assignment to
protein sequence positions.
Each fragment is described as follows:
Here, the first line specifies  protein sequence position to which the fragment is assigned, 1-letter amino acid type, the number of the following lines describing the fragment, chemical shift of backbone C' atom, and user ID of the fragment.The last number, user ID, is optional.
 
Example2.1. Assigned AA-fragments with user ID specified.
Example2.2. Assigned AA-fragments without user ID specified.

<div<div<

3. CYANA chemical shift file (prot-file).
Assigned chemical shifts caould be loaded in FMCGUI and automatically transformed in a set of assigned PB-frsagments.
Example3.1. Assigned chemical shifts.
Retrieved from "https://nesgwiki.chem.buffalo.edu/index.php?title=Resonance_Assignment/Abacus/Spin_systems_format&oldid=2283"