        ___________               ___________               ___________ 
       |\ __________\            |___________|            /__________ /|
       | |           |           |           |           |           | |
       | | **********|           |***********|           |********** | |
       | | * BLOCKS  |           |EMAIL & WWW|           |SEARCHER * | |
       | | **********|           |***********|           |********** | |
        \|___________|___________|___________|___________|___________|/
                     |\ __________\         /__________ /|
                     | |  blocks@  |       | http://   | |
                     | |   blocks. |       |  blocks.  | |
                     | |   fhcrc.  |       |  fhcrc.   | |
                     | |   org     |       |  org      | |
                      \|___________|       |___________|/


Here are your search results. The database searched was Blocks+ (10 June 00)
which includes: BLOCKS 12.0 consisting of 4071 blocks representing 998 groups
documented in InterPro 1.0/PROSITE, plus 3141 blocks from 498 groups documented 
in PRINTS 26.0 but not represented in BLOCKS, plus 2382 blocks from 569 groups 
documented in PFAM 5.3 but not represented in BLOCKS or PRINTS, plus
962 blocks from 250 groups documented in PRODOM 99.1 but not represented in
BLOCKS, PRINTS or PFAM, plus 282 blocks from 76 groups documented in DOMO 2.0
but not represented in BLOCKS, PRINTS, PFAM or PRODOM for a total of 10,838
blocks from 2391 groups.  Get more information at http://blocks.fhcrc.org.
If you found the Blocks Searcher useful, please cite:
   S Henikoff & JG Henikoff, "Protein family classification
   based on searching a database of blocks", Genomics 19:97-107 (1994).
Please report problems to:  webmaster@blocks.fhcrc.org
==============================================================================
Each hit consists of one or more blocks from a protein group found
in the query sequence. One set of the highest-scoring blocks that are in the 
correct order and separated by distances comparable to the Blocks database is 
selected for analysis. If this set includes multiple blocks the probability 
that the lower scoring blocks support the highest scoring block is reported. 
Maps of the database blocks and query sequence are shown:
AAA represents a block roughly in proportion to its width.
  : represents the minimum distance between blocks in the database.
  . represents the maximum distance between blocks in the database.
< > indicate the sequence has been truncated to fit the page.
The query map is aligned on the highest scoring block. Multiple block hits 
that are consistent with the highest scoring block are separated by colons.
Block hits that are not consistent are mapped below. The alignment of the
query sequence with the sequence closest to it in the BLOCKS database is
shown. The distance between detected blocks is listed as (min, max): for the
database entry followed by the distance in the query. Upper case in the query
indicates at least one occurrence of the residue in that column of the block.

=============================================================================
Note: For searches using DNA queries, "Location" refers to the position
in the query in base pairs from 5' to 3' on the + strand, whereas the map and 
alignment show the translated position in amino acid residues.
============================================================================= 
