Resonance Assignment/Abacus/FMCGUI objects: Difference between revisions
No edit summary |
No edit summary |
||
Line 67: | Line 67: | ||
=== Contact map === | === Contact map === | ||
:There are three fragment contact maps: C<sup>f1</sup><sub>CA | :There are three fragment contact maps: C<sup>f1</sup><sub>CA</sub><span>(f2) , </span>C<sup>f1</sup><sub>B</sub><span>(f2) ,</span><span> and </span>C<sup>f1</sup><sub>F</sub><span>(f2) </span><span>, respectively. Each contact map scores the possibility for any fragment ''f1'' to be next to the fragment ''f1'' in protein sequence. Here ''f''1 and ''f2'' stand for fragment's user ID. </span> | ||
<div><span> Fragment contact map </span>C<sup>f1</sup><sub>CA | <div><span> Fragment contact map </span>C<sup>f1</sup><sub>CA</sub><span>(f2) </span><span>is calculated based on HNCA spectrum by the command {Assignment>Contact>HNCA}</span></div><div> Fragment<span> contact maps </span>C<sup>f1</sup><sub>B</sub><span>(f2) </span><span> and </span>C<sup>f1</sup><sub>F</sub><span>(f2) </span><span /><span> are calculated from NOESY spectra with or without using BACUS procedure, respectively.</span></div><div><span> </span><span> </span>C<sup>f1</sup><sub>F</sub><span>(f2) </span><span> can be calculated for all values of f1 and f2 by both commands {Assignment>Contact>NOE>fawn} and {Assignment>Contact>NOE>abacus}, while </span>C<sup>f1</sup><sub>B</sub><span>(f2) </span><span /><span> is calculated by command {Assignment>Contact>NOE>abacus}.</span></div><div> </div> | ||
=== Assignment probabilities === | === Assignment probabilities === |
Revision as of 21:43, 30 November 2009
- protein sequence
- peak list
- and PB fragments.
Protein sequence
Peak list
- (+) peak list is required to be referenced
- (+/-) peak lists could be referenced optionally
- (-) peak lists for which referencing is not used even if it is present in the input file
N15 NOESY
|
-
|
C13 NOESY H2O
|
-
|
Arom NOESY
|
-
|
N15 HSQC
|
+
|
C13 HSQC
|
+
|
HNCA
|
+/-
|
HNCO
|
-
|
CBCACONH
|
+/-
|
HBHACONH
|
+
|
List of PB fragments
User ID
Fragment ID assigned by user, U_id. U_id can’t be changed within FMCGUI.
Assignment ID
Assignment ID, A_id, indicates the sequence position ID to which the fragment is assigned.
A_id = -99 if the fragment is not assigned to any position in the sequence.
A_id could be set up or modified by the following commands {Assignment>Fix Assignment>Manually}, {Assignment>Fix Assignment>Using probability Map}, and {Assignment>Fix Assignment>Reset all }.
Typing probabilities
Tt (f) is a probability for fragment f to have amino acid type t. Here t corresponds to one of 20 amino acid residue types, and f is fragment user ID.
Typing probbilities could be calculated or modified manually by the commands {Fragment>Type>Calculate} and {Fragment>Type>Fix}, respectively.
Contact map
- There are three fragment contact maps: Cf1CA(f2) , Cf1B(f2) , and Cf1F(f2) , respectively. Each contact map scores the possibility for any fragment f1 to be next to the fragment f1 in protein sequence. Here f1 and f2 stand for fragment's user ID.
Assignment probabilities
- FragmentFragment assignment probabilities and are calculated using SA and REM Monte Carlo simulations, respectively. Here s stands for protein sequence position ID.