BMERC : needle tools : Introduction : needle prediction overview
This page describes the larger context of sequence-based structure prediction within which the needle tools are useful.
Figure 1: Generating exposure, core, and sequence files
The figure above shows the dataflow involved in generating exposure, core, and sequence files from a given PDB file. Click on a program name (in the rectangular boxes) to follow a link to its detailed description; click on a file format name (in the ovals) to follow a link to its definition.
Note that the only input is the PDB file, and that the three files
can be generated independently. The core file is generated from the PDB
file and a segment
definition file, which can be supplied either from DSSP, or (if the
PDB file includes HELIX and/or SHEET records) from the
crystallographers' secondary structure assignments in the PDB file.
Generating multiple homolog alignments
Structure-directed multiple alignments of sequences homologous to a
given core segment are used to "sweeten" the amino acid counts made by
the mrf-counts program.
Instead of just counting the amino acid that actually appears in a
singleton position in a given core, we can use the homology data to
count each amino acid that could potentially appear there (and similarly
for each unique pair of AA's for pairwise environments). Doing so
appears to produce better threading results [data or reference?].
In the future, we would like to be able to thread sets of related sequences simultaneously, and hope to be able to bring these tools to bear on aligning the sequences to thread.
[The original multiple alignment implementation that was used to produce the files in the ~thread/aligment/ directory at BMERC (a) required a fair amount of manual intervention, and (b) was not a true multiple alignment in any case. The right thing to do would be to re-engineer it to use the pima_profile program. Since we are not actually using homolog data at present, preferring to use a large set of actual cores instead, this project is on indefinite hold. -- rgr, 20-Jan-98.]