Hingefind (X-PLOR) -

an algorithm to investigate domain motions in proteins.

9-24-96

This page contains documentation specifically for the X-PLOR version.

Content:

1. General Remarks about the X-PLOR Version

The X-PLOR (Axel T. Brunger, 1992) version is designed for longer batch jobs which allow the user to run a large number of trial runs in various modes. The X-PLOR version has all the features described in the paper. In particular, it allows to maintain the spatial connectivity of the found domains. The version requires that the user obtains a free license for the X-PLOR software. The output psf and pdb files can be visualized with any standard graphics package.

2. Files and Shell Scripts

There are several files and scripts in this directory to set up the algorithm:

hingefind

A unix shell script that runs the X-PLOR job and writes three X-PLOR stream files which contain commands from which X-PLOR can compute filenames and the tolerance used the algorithm. It is recommended to run the cases within a range of tolerances between 50 and 100% of the initial rms deviation. There are case descriptors from which hingefind.inp computes the actual coordinate files (in pdb format) of the structures used in the comparison, i.e. here: foo.COO, soo.COO, bar.COO. Change these to your own filenames. Note that hingefind.inp will always interpret "foobar" as "foobar.COO", so you may want to edit hingefind.inp if you use other file suffixes (e.g. ".pdb") instead of ".COO".

partition.str

A stream file which contains necessary X-PLOR commands to set up the structure. It may contain a pointer to a psf file. The segid "APO" is be used for the parts of the protein which should be aligned, otherwise hingefind.inp has to be modified. Note that the coordinates in the two compared pdb files must be both compatible with the structure. The pdb files may contain additional atoms which do not have to be specified in partition.str if not used in the alignment. To appear in the output files, such additional structures which are not used in the alignment should be given a segid different from "APO" in partition.str.

dum.top

An X-PLOR topology file with the residues of dummy molecules used in the algorithm for visualization of pivot points and axes.

prexplor.dim

The X-PLOR file which contains array sizes for compilation (35,000 atom version). It will probably be necessary to compile X-PLOR with the larger BUFMAX parameter for the loops. This executable is named "xl" in the hingefind script.

hingefind.inp

The X-PLOR script with the algorithm. There are a variety of variables and paths the user has to specify in the head of the file :

Running a particular system with a range of tolerances in "fas" mode, it was found that there exists one or more windows of optimum tolerance where the relative errors were very small. Therefore it is recommended to try a range of tolerances first with the "fas" mode, find the window(s) of small error and then calculate selected tolerances in the window(s) in "slo" mode with a higher number of domains. The error of the domain fitting was found to decrease with "slo" partitioning due to the connectivity of the domains.

3. Output Files

There are three output files specified by the variables $oname $uname and $dname: pdb and psf files of the labeled structure, and the log file of the run. The pdb and psf files can be used to visualize the results of the algorithm: The data is labeled by segid's:

In addition, the user may also find untouched atoms with the segid "APO" and other segid's not used in the alignment.

The dummy molecules show an arrow along the rotation axis with it's orientation representing the left-handed rotation about the axis. The constructed "pivot" can be found in the middle of the arrow and is connected to the COM of the main and comparison coordinate set of the domain to illustrate the rotation angle. The rotation angle and other useful information about the run, the domains, and the accuracy of the rotational fitting can be found in the self-explanatory log file.

NOTE: The X-PLOR log files would contain several Mbytes of data for each run, so the standard output is piped to /dev/null. The standard output should only be used for debugging of modified or augmented scripts.

Other Links

Main Page

Domain Movements Hingefind Hingefind Tcl