Just stirring you along a bit. 'Mace' and 'Mack' 'Macca' are just about all the McEdge cases.

If you look at the algorithm you will see it is just this:

($f) = /^(.)/; tr/AEHIOUWYBFPVCGJKQSXZDTLMNR/00000000111122222222334556/; ($fc) = /^(.)/; s/^$fc+//; tr///cs; tr/0//d; $_ = $f . $_ . '000'; s/^(.{4}).*/$1/;

While there is no doubt it gives useful results it is exceptionally simplistic. The problem you are trying to solve is threefold:

  1. Simple mis-spelling
  2. Pronuncitation Differences
  3. Dropped sylables

To a large extent the Knuth algorithm deals reasonably successfully with 1 and 2. Where it falls over is when there is either a mis-spelling of the first letter or a dropped sylable. As you could see in the example I fuzzed the matches by dropping symbols from the code to deal with this, given that there are only 6 numeric codes in use my estimate that it would on average pull 1% of the DB should have read more like 3% if you shorten the codes.

In my picture of a 'better' algorithm I imagine a mapping to perhaps [A-Z]{4} so you could perhaps do linear displacement rather than just dropping.....Oh well back to the real work Bayes filters are the soup de jour.

cheers

tachyon

s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print


In reply to Re: Re: Re: Re: Closest matches from string array by tachyon
in thread Closest matches from string array by Baz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.