Resonance Assignment/AutoAssign: Difference between revisions

From NESG Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 25: Line 25:
[[Image:Autoassign1.jpg]]  
[[Image:Autoassign1.jpg]]  


=== '''Creating a Data Set'''<br>  ===
== '''Creating a Data Set'''<br>  ==


==== Using the Peaklist Converter in the Graphical User Interface  ====
=== Using the Peaklist Converter in the Graphical User Interface  ===


The easiest way to create a dataset is to using the Dataset Creation Graphical User Interface. This interface will guide you through the basic steps of converting your peak lists, registering your peak lists, creating a control file, and evaluating the quality of your peak lists. Go to <code>File</code> -&gt; <code>Convert/Create Dataset</code> from the main menu option to start the Dataset Creation Graphical User Interface (Figure 2).<br>  
The easiest way to create a dataset is to using the Dataset Creation Graphical User Interface. This interface will guide you through the basic steps of converting your peak lists, registering your peak lists, creating a control file, and evaluating the quality of your peak lists. Go to <code>File</code> -&gt; <code>Convert/Create Dataset</code> from the main menu option to start the Dataset Creation Graphical User Interface (Figure 2).<br>  
Line 37: Line 37:
The process is divided into 4 steps:&nbsp; 1. Peak list conversion, 2. Registration, 3. Data set properties, and 4. Data set completion.  
The process is divided into 4 steps:&nbsp; 1. Peak list conversion, 2. Registration, 3. Data set properties, and 4. Data set completion.  


'''1.&nbsp; Peak list conversion'''
==== '''1.&nbsp; Peak list conversion''' ====


The peak list conversion process is designed to reformat given peak lists into AutoAssign format (Figure 3).&nbsp; Here the user defines the columns and spectral properties of each peak list.<br>  
The peak list conversion process is designed to reformat given peak lists into AutoAssign format (Figure 3).&nbsp; Here the user defines the columns and spectral properties of each peak list.<br>  


==== Figure 3:&nbsp; Peak List Conversion Page ====
==== Figure 3:&nbsp; Peak List Conversion Page ====


[[Image:Autoassign3.jpg]]
[[Image:Autoassign3.jpg]]  


*'''Working directory [text field]''': it is a base directory that the interface will use to create a subdirectory with a time stamp. The default is set to the current working directory.  
*'''Working directory [text field]''': it is a base directory that the interface will use to create a subdirectory with a time stamp. The default is set to the current working directory.  
Line 51: Line 51:
*'''Convert Peak Lists [button]:''' this function runs a set of AutoAssign perl scripts to converts peak lists entered by a user. It generates intermediate files used to compute registration/tolerance values for the subsequent steps. All scripts executions run by interface is logged in <code>event.log</code> file found under the subdirectory named with a time stamp along with other intermediate files.<br>
*'''Convert Peak Lists [button]:''' this function runs a set of AutoAssign perl scripts to converts peak lists entered by a user. It generates intermediate files used to compute registration/tolerance values for the subsequent steps. All scripts executions run by interface is logged in <code>event.log</code> file found under the subdirectory named with a time stamp along with other intermediate files.<br>


'''2.&nbsp; Registration''' <br> A user will be taken to the <code>Registration</code> tab when <code>Convert Peak List</code> button is clicked. This will allow a user to calculate registration values and apply those values to shift peaks by creating new / temporal peaklist files.
==== '''2.&nbsp; Registration''' ====
 
A user will be taken to the <code>Registration</code> tab when <code>Convert Peak List</code> button is clicked. This will allow a user to calculate registration values and apply those values to shift peaks by creating new / temporal peaklist files.  


== '''References'''  ==
== '''References'''  ==


1. &nbsp; Zimmerman, D.E., Kulikowski, C.A., Huang, Y., Feng, W., Tashiro, M.,&nbsp; Shimotakahara, S., Chien, C., Powers, R. and Montelione, G.T. (1997) Automated analysis of protein NMR assignments using methods from artificial intelligence. ''J. Mol. Biol. 269'', 592-610. <br>
1. &nbsp; Zimmerman, D.E., Kulikowski, C.A., Huang, Y., Feng, W., Tashiro, M.,&nbsp; Shimotakahara, S., Chien, C., Powers, R. and Montelione, G.T. (1997) Automated analysis of protein NMR assignments using methods from artificial intelligence. ''J. Mol. Biol. 269'', 592-610. <br>

Revision as of 18:56, 9 November 2009

Introduction

AutoAssign is a constraint-based expert system for automating the assignment and analysis of backbone NMR resonance assignments of proteins (Ref. 1).  The program is implemented in C++, Java2, and Perl programming languages and supported on  SGI-IRIX, Sun-Solaris, MAC-OSX, x86-Linux, and x86_64-Linux architectures. The newest AutoAssign distribution (version 2.4.0) automates the assignments of HN, NH, CO, CA, CB, HA, and HB resonances in non-, partially-, and fully-deuterated samples.  The rich graphical user interface (GUI) provides a many sets of tools for dataset conversions, assignment validations, and various graphical displays of assignment results.  AutoAssign is well tested on a large number of independently-collected triple-resonance NMR data sets of proteins ranging in size from ~6 to ~32 kD, including one fully-deuterated protein and and a dataset with reduced-dimensionality experiments.  AutoAssign performs the automated analysis of assignments in only seconds on current RISC and x86 platforms.

The following description is mainly taken from the AutoAssign SOP (tutorial).  Please check this tutorial and the version 2.4.0 help documentation for more information and usage.

Using AutoAssign

Input Files

The input files for AutoAssign are:

Opening AutoAssign

  • Run the startup script autoassign If you are running the client on the same machine as the server.
  • If you are running the client on a machine different from the server, then you must first make sure that the server is running on the other machine. The easiest way to do this is to run the startup script autoserver on this other computer.

The main AutoAssign window will appear (Figure 1).

Figure 1:  AutoAssign Main Window

Autoassign1.jpg

Creating a Data Set

Using the Peaklist Converter in the Graphical User Interface

The easiest way to create a dataset is to using the Dataset Creation Graphical User Interface. This interface will guide you through the basic steps of converting your peak lists, registering your peak lists, creating a control file, and evaluating the quality of your peak lists. Go to File -> Convert/Create Dataset from the main menu option to start the Dataset Creation Graphical User Interface (Figure 2).

Figure 2:  The Peak List Converter

Autoassign2.jpg

The process is divided into 4 steps:  1. Peak list conversion, 2. Registration, 3. Data set properties, and 4. Data set completion.

1.  Peak list conversion

The peak list conversion process is designed to reformat given peak lists into AutoAssign format (Figure 3).  Here the user defines the columns and spectral properties of each peak list.

Figure 3:  Peak List Conversion Page

Autoassign3.jpg

  • Working directory [text field]: it is a base directory that the interface will use to create a subdirectory with a time stamp. The default is set to the current working directory.
  • Auto Fill [button]: when a user decides to reuse the same peak lists or the same type of configuration based on the previous analysis, this function allows a user to import the data previously used.
  • Add Experiment [button]: This function allows a user to display additional blank peaklist panel.
  • Clear All Entries [button]: this function clears populated data fields displayed on screens.
  • Convert Peak Lists [button]: this function runs a set of AutoAssign perl scripts to converts peak lists entered by a user. It generates intermediate files used to compute registration/tolerance values for the subsequent steps. All scripts executions run by interface is logged in event.log file found under the subdirectory named with a time stamp along with other intermediate files.

2.  Registration

A user will be taken to the Registration tab when Convert Peak List button is clicked. This will allow a user to calculate registration values and apply those values to shift peaks by creating new / temporal peaklist files.

References

1.   Zimmerman, D.E., Kulikowski, C.A., Huang, Y., Feng, W., Tashiro, M.,  Shimotakahara, S., Chien, C., Powers, R. and Montelione, G.T. (1997) Automated analysis of protein NMR assignments using methods from artificial intelligence. J. Mol. Biol. 269, 592-610.