[#LUCENE-626] Extended spell checker with phrase support and adaptive user session analysis.

Lucene - Java

Extended spell checker with phrase support and adaptive user session analysis.

Created: 13/Jul/06 04:18 PM Updated: 17/Apr/08 08:02 PM

Return to search

Component/s:

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

File Attachments:

	File Name	Date Attached	Attached By	Size
	LUCENE-626_20071023.txt	2007-10-23 08:18 PM	Karl Wettin	234 kB

Lucene Fields:

Patch Available

Description

« Hide

Extensive javadocs available in patch, but I also try to keep it compiled here: http://ginandtonique.org/~kalle/javadocs/didyoumean/org/apache/lucene/search/didyoumean/package-summary.html#package_description

A semi-retarded reinforcement learning thingy backed by algorithmic second level suggestion schemes that learns from and adapts to user behavior as queries change, suggestions are accepted or declined, etc.

Except for detecting spelling errors it considers context, composition/decomposition and a few other things.

heroes of light and magik -> heroes of might and magic
vinci da code -> da vinci code
java docs -> javadocs
blacksabbath -> black sabbath

Depends on ~~LUCENE-550~~

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Karl Wettin made changes - 13/Jul/06 04:19 PM

Field	Original Value	New Value
Attachment		spellcheck_0.0.1.tar.gz [ 12336793 ]

Karl Wettin made changes - 26/Jul/06 01:02 AM

Attachment

spellcheck_20060725.tar.gz [ 12337519 ]

Karl Wettin made changes - 04/Aug/06 05:59 AM

Attachment

spellcheck_20060804.tar.gz [ 12338119 ]

Karl Wettin made changes - 04/Aug/06 09:15 PM

Attachment

spellcheck_20060804_2.tar.gz [ 12338186 ]

Karl Wettin made changes - 30/Jan/07 01:00 AM

Attachment

spellcheck_0.0.1.tar.gz [ 12336793 ]

Karl Wettin made changes - 30/Jan/07 01:00 AM

Attachment

spellcheck_20060725.tar.gz [ 12337519 ]

Karl Wettin made changes - 30/Jan/07 01:01 AM

Attachment

spellcheck_20060804.tar.gz [ 12338119 ]

Karl Wettin made changes - 30/Jan/07 12:23 PM

Attachment

spellchecker.diff [ 12349911 ]

Karl Wettin made changes - 30/Jan/07 12:24 PM

Attachment

spellcheck_20060804_2.tar.gz [ 12338186 ]

Karl Wettin made changes - 03/Feb/07 01:46 AM

Comment

[

I've been running this version live today. Suggests great stuff all
the time. It is however a bit RAM hogging just as everything else I
do. Think I'll add some sort of external persistency to handle that
(probably BDB), backed by a soft referenced cache.

There is a problem with the adaptive layer not adapting to (correct)
suggestions with large edit distance supplied by the multi word/term
position vector layer on top of the ngram spell checker. E.g. "magic
might heros" -> "heroes might magic".
]

Karl Wettin made changes - 03/Feb/07 01:46 AM

Comment

[ It uses the ngram spell checker for queries yet not corrected by users, but it handles more than one word at the time, and it inspects the term position vector if available. This way it can also rearange input to the most probable order.

    addDocument(indexWriter, field, "heroes of might and magic III complete");
    addDocument(indexWriter, field, "it might be the best game ever made");

    assertEquals("heroes of might and magic", suggester.didYouMean("hereos of magic and might"));
    assertEquals("heroes of might and magic", suggester.didYouMean("hereos of light and magic"));
    assertEquals("heroes might magic", suggester.didYouMean("magic light heros"));
    assertEquals("best game made", suggester.didYouMean("game best made"));
    assertEquals("game made", suggester.didYouMean("made game"));
    assertEquals("game made", suggester.didYouMean("made lame"));
    assertEquals(null, suggester.didYouMean("may game"));

Once someone clicks on a suggestion (you have to report this back to the suggester) it will get a higher priority. If the person reports interest in one or many of the results in the followed suggested query, it will get an even higher priority. If something is suggested but not clicked on, then the priority will go down. When the priority reaches a lower threadshold, it will no loger be suggested, and the next best suggestion will appear. And so on.

To change the query manually is the same thing as clicking on a suggestions, given it is similar enough and withing a certain timeframe.

    assertEquals("homm", suggester.didYouMean("heroes of might and magic"));
    assertEquals("heroes of might and magic", suggester.didYouMean("heroes of night and magic"));

    assertEquals("homm", suggester.didYouMean("heroes of might and magic"));
    assertEquals("heroes of might and magic", suggester.didYouMean("homm"));

The data is stored in a Map<String /*query*/, List<Suggestion>>, and the default implementation strips the query from p{Punct}. That should help with composite and decomposite, amongst much.

    assertEquals("the da vinci code", suggester.didYouMean("thedavincicode"));
    assertEquals("the da vinci code", suggester.didYouMean("the dav-inci code"));
    assertEquals("heroes of might and magic", suggester.didYouMean("heroes ofnight andmagic"));

It seems as the ngram spell check tests is broken - requires the removed class English. I've re-introduced it in Lucene-550.

I will not work further on this patch and issue. It will be added to Lucene-550 for chaching and such. ]

Karl Wettin made changes - 03/Feb/07 01:46 AM

Comment

[ beta 3

total rewrite with focus on adaptation.

session search sequence extraction, training and suggesting are now seperate classes passed to the spell checker.

still require lots of user interaction to build a sufficient dictionary.

has no optimization. bootstrap has been removed and will probably re-appear in future default suggestion scheme instead. should be fast enough.

now also comes with some junit test cases.

default implementations are quite simple, but effective: strips suggestive data (trained suggestive- and test phrases) from punctuation and whitespace in order to find incorrect composite and decomposed words. e.g. "the davinci code" --> "the da vinci code", "a clock work orange" --> "a clockwork orage".

beta 4 will focus on training- and suggestion classes that works on secondary trie populated with known good data extracted from corpus, navigated with edit distance. perhaps a forest-type trie to allow any starting point in a phrase.

OR

beta 4 will focus on discrimiating trained queries to build clusters and suggest (facet) classes parallell to a plain text suggestion. that would be a major ram-consumer and require lots of manual tweaking per implemenation, but a cool enough feature.

time will tell. ]

Karl Wettin made changes - 03/Feb/07 01:46 AM

Comment

[ oups, i attached the old code last time. ]

Karl Wettin made changes - 03/Feb/07 01:46 AM

Comment

[ Bugfixes in bootstrap() and correction sequence extraction.

A couple of optimizations.

Negative training (didNotMean), but no automatic detection yet. I'm evaluation a couple of solutions. So perhaps next time(tm). ]

Karl Wettin made changes - 03/Feb/07 01:46 AM

Comment

[ Beta 1.

Will add prevayler transactions in future. ]

[ Permlink | « Hide ]

Karl Wettin added a comment - 03/Feb/07 02:19 AM

All of the old comments was obsolete, so I re-initialized the whole issue.

Karl Wettin made changes - 03/Feb/07 02:19 AM

Assignee		Karl Wettin [ karl.wettin ]
Lucene Fields		[Patch Available]
Issue Type	New Feature [ 2 ]	Improvement [ 4 ]
Description	From javadocs: This is an adaptive, user query session analyzing spell checker. In plain words, a word and phrase dictionary that will learn from how users act while searching. Be aware, this is a beta version. It is not finished, but yeilds great results if you have enough user activity, RAM and a faily narrow document corpus. The RAM problem can be fixed if you implement your own subclass of SpellChecker as the abstract methods of this class are the CRUD methods. This will most probably change to a strategy class in future version. TODO: 1. Gram up results to detect compositewords that should not be composite words, and vice verse. 2. Train a gramed token (markov) chain with output from an expectation maximization algorithm (weka clusters?) parallel to a closest path (A* or bredth first?) to allow contextual suggestions on queries that never was placed. Usage: Training At user query time, create an instance of QueryResults containg the query string, number of hits and a time stamp. Add it to a chronologically ordered list in the user session (LinkedList makes sense) that you pass on to train(sessionQueries) as the session times out. You also want to call the bootstrap() method every 100000 queries or so. Spell checking Call getSuggestions(query) and look at the results. Don't modify it! This method call will be hidden in a facade in future version. Note that the spell checker is case sensitive, so you want to clean up query the same way when you train as when you request the suggestions. I recommend something like query = query.toLowerCase().replaceAll(" ", " ").trim()	Some minor changes to how the single token ngram spell checker in contrib/spellcheck, but nothing that breaks any old implementation I think. Also fixed the broken test. NgramPhraseSuggestier tokenizes a query and suggests combinations of the single token suggestions matrix. They must match as a query against an apriori index. By using a span near query (default) you get features like this: assertEquals("lost in translation", ngramSuggester.didYouMean("lost on translation")); If term position vectors are available it is possible to make it context sensitive (or what one may call it) to suggest a new term order. assertEquals("heroes might magic", ngramSuggester.didYouMean("magic light heros")); assertEquals("heroes of might and magic", ngramSuggester.didYouMean("heros on light and magik")); assertEquals("best game made", ngramSuggester.didYouMean("game best made")); assertEquals("game made", ngramSuggester.didYouMean("made game")); assertEquals("game made", ngramSuggester.didYouMean("made lame")); assertEquals("the game", ngramSuggester.didYouMean("the game")); assertEquals("in the fame", ngramSuggester.didYouMean("in the game")); assertEquals("game", ngramSuggester.didYouMean("same")); assertEquals(0, ngramSuggester.suggest("may game").size()); SessionAnalyzedDictionary is the adaptive layer, that learns from how users changed their queries, what data they inspected, et c. It will automagically find and suggest synonyms, decomposed words, and probably a lot of other neat features I still have not detected. A bit depending on the situation, ignored suggestions get suppresed and followed suggestions get suggeted even more. assertEquals("the da vinci code", dictionary.didYouMean("thedavincicode")); assertEquals("the da vinci code", dictionary.didYouMean("the davinci code")); assertEquals("homm", dictionary.didYouMean("heroes of might and magic")); assertEquals("heroes of might and magic", dictionary.didYouMean("homm")); assertEquals("heroes of might and magic 2", dictionary.didYouMean("heroes of might and magic ii")); assertEquals("heroes of might and magic ii", dictionary.didYouMean("heroes of might and magic 2")); The adaptive layer is not yet(tm) persistent, but soft referenced so that the dictionary don't go eat up all your RAM.
Summary	Adaptive, user query session analyzing spell checker.	Extended spell checker with phrase support and adaptive user session analysis.

[ Permlink | « Hide ]

Karl Wettin added a comment - 03/Feb/07 02:21 AM

NgramPhraseSuggester is now decoupled from the adaptive layer, but I would like to refactor it even more so it is easy to replace the SpellChecker with any other single token suggester.

Karl Wettin made changes - 03/Feb/07 02:21 AM

Attachment

spellchecker.diff [ 12350263 ]

Karl Wettin made changes - 03/Feb/07 02:22 AM

Attachment

spellchecker.diff [ 12349911 ]

Karl Wettin made changes - 17/Feb/07 07:54 AM

Link

This issue is part of ~~LUCENE-550~~ [ ~~LUCENE-550~~ ]

[ Permlink | « Hide ]

Karl Wettin added a comment - 17/Feb/07 07:54 AM

Patch in this issue have no dependencies to anything out of the ordinary.

However, a large refactor and well documented version dependent to ~~LUCENE-550~~ is available.

Karl Wettin made changes - 17/Feb/07 07:55 AM

Comment

[ Almost all TODO:s in the code (mostly refactoring to support alternative single token suggesters [as in the old spell checker]) have been fixed, but as it depends on ~~LUCENE-550~~ is is available in that issue. ]

[ Permlink | « Hide ]

Karl Wettin added a comment - 03/Mar/07 07:59 PM

Patch depends on ~~LUCENE-550~~.

Karl Wettin made changes - 03/Mar/07 07:59 PM

Attachment

didyoumean.patch.bz2 [ 12352515 ]

Karl Wettin made changes - 03/Mar/07 08:05 PM

Description

Some minor changes to how the single token ngram spell checker in contrib/spellcheck, but nothing that breaks any old implementation I think. Also fixed the broken test.

NgramPhraseSuggestier tokenizes a query and suggests combinations of the single token suggestions matrix.

They must match as a query against an apriori index. By using a span near query (default) you get features like this:

    assertEquals("lost in translation", ngramSuggester.didYouMean("lost on translation"));

If term position vectors are available it is possible to make it context sensitive (or what one may call it) to suggest a new term order.

    assertEquals("heroes might magic", ngramSuggester.didYouMean("magic light heros"));
    assertEquals("heroes of might and magic", ngramSuggester.didYouMean("heros on light and magik"));
    assertEquals("best game made", ngramSuggester.didYouMean("game best made"));
    assertEquals("game made", ngramSuggester.didYouMean("made game"));
    assertEquals("game made", ngramSuggester.didYouMean("made lame"));
    assertEquals("the game", ngramSuggester.didYouMean("the game"));
    assertEquals("in the fame", ngramSuggester.didYouMean("in the game"));
    assertEquals("game", ngramSuggester.didYouMean("same"));
    assertEquals(0, ngramSuggester.suggest("may game").size());

SessionAnalyzedDictionary is the adaptive layer, that learns from how users changed their queries, what data they inspected, et c. It will automagically find and suggest synonyms, decomposed words, and probably a lot of other neat features I still have not detected.

A bit depending on the situation, ignored suggestions get suppresed and followed suggestions get suggeted even more.

    assertEquals("the da vinci code", dictionary.didYouMean("thedavincicode"));
    assertEquals("the da vinci code", dictionary.didYouMean("the davinci code"));

    assertEquals("homm", dictionary.didYouMean("heroes of might and magic"));
    assertEquals("heroes of might and magic", dictionary.didYouMean("homm"));

    assertEquals("heroes of might and magic 2", dictionary.didYouMean("heroes of might and magic ii"));
    assertEquals("heroes of might and magic ii", dictionary.didYouMean("heroes of might and magic 2"));

The adaptive layer is not yet(tm) persistent, but soft referenced so that the dictionary don't go eat up all your RAM.

Extensive java docs available in patch, but I try to keep it compiled here: http://ginandtonique.org/~kalle/javadocs/didyoumean/org/apache/lucene/search/didyoumean/package-summary.html#package_description

The patch spellcheck.diff should not depend on anything but Lucene trunk. It has basic support for phrase suggestions and query goal detection, but is pretty buggy and lacks features available in didyoumean.diff.bz2. The latter depends on ~~LUCENE-550~~.

Example:
{code:java}
public void testImportData() throws Exception {

    // load 200 000 user queries with session data and time stamp. no goals specified.

    System.out.println("Processing http://ginandtonique.org/~kalle/data/pirate.data.gz");
    importFile(new InputStreamReader(new GZIPInputStream(new URL("http://ginandtonique.org/~kalle/data/pirate.data.gz").openStream())));
    System.out.println("Processing http://ginandtonique.org/~kalle/data/hero.data.gz");
    importFile(new InputStreamReader(new GZIPInputStream(new URL("http://ginandtonique.org/~kalle/data/hero.data.gz").openStream())));
    System.out.println("Done.");

    // run some tests without the second level suggestions,
    // i.e. user behavioral data only. no ngrams or so.

    assertEquals("pirates of the caribbean", facade.didYouMean("pirates ofthe caribbean"));

    assertEquals("pirates of the caribbean", facade.didYouMean("pirates of the carribbean"));

    assertEquals("pirates caribbean", facade.didYouMean("pirates carricean"));
    assertEquals("pirates of the caribbean", facade.didYouMean("pirates of the carriben"));
    assertEquals("pirates of the caribbean", facade.didYouMean("pirates of the carabien"));
    assertEquals("pirates of the caribbean", facade.didYouMean("pirates of the carabbean"));

    assertEquals("pirates of the caribbean", facade.didYouMean("pirates og carribean"));

    assertEquals("pirates of the caribbean soundtrack", facade.didYouMean("pirates of the caribbean music"));
    assertEquals("pirates of the caribbean score", facade.didYouMean("pirates of the caribbean soundtrack"));

    assertEquals("pirate of caribbean", facade.didYouMean("pirate of carabian"));
    assertEquals("pirates of caribbean", facade.didYouMean("pirate of caribbean"));
    assertEquals("pirates of caribbean", facade.didYouMean("pirates of caribbean"));

    // depening on how many hits and goals are noted with these two queries
    // perhaps the delta should be added to a synonym dictionary?
    assertEquals("homm iv", facade.didYouMean("homm 4"));

    // not yet known.. and we have no second level yet.
    assertNull(facade.didYouMean("the pilates"));

    // use the dictionary built from user queries to build the token phrase and ngram suggester.
    facade.getDictionary().getPrioritesBySecondLevelSuggester().put(Factory.ngramTokenPhraseSuggesterFactory(facade.getDictionary()), 1d);

    // now it's learned
    assertEquals("the pirates", facade.didYouMean("the pilates"));

    // typos
    assertEquals("heroes of might and magic", facade.didYouMean("heroes of fight and magic"));
    assertEquals("heroes of might and magic", facade.didYouMean("heroes of right and magic"));
    assertEquals("heroes of might and magic", facade.didYouMean("heroes of magic and light"));

    // composite dictionary key not learned yet..
    assertEquals(null, facade.didYouMean("heroesof lightand magik"));
    // learn
    assertEquals("heroes of might and magic", facade.didYouMean("heroes of light and magik"));
    // test
    assertEquals("heroes of might and magic", facade.didYouMean("heroesof lightand magik"));

    // wrong term order
    assertEquals("heroes of might and magic", facade.didYouMean("heroes of magic and might"));

  }
{code}

[ Permlink | « Hide ]

Nicolas Lalevée added a comment - 03/Mar/07 09:04 PM

This feature looks interesting, but why should it depend on ~~LUCENE-550~~ ?

[ Permlink | « Hide ]

Karl Wettin added a comment - 03/Mar/07 09:13 PM

Nicolas Lalevée [03/Mar/07 01:04 PM]
> This feature looks interesting, but why should it depend on ~~LUCENE-550~~ ?

It use the Index (notification, unison index factory methods, et c.) and IndexFacade (cache, fresh reader/searcher et c.) available in that patch. And by doing that, it also enables me to use InstantiatedIndex for the a priori corpus and ngram index to speed up the response time even more.

Karl Wettin made changes - 17/Mar/07 08:18 PM

Link

This issue is part of ~~LUCENE-550~~ [ ~~LUCENE-550~~ ]

[ Permlink | « Hide ]

Karl Wettin added a comment - 17/Aug/07 12:10 AM

As the phrase-suggestion layer on top of contrib/spell in this patch was noted in a bunch of forums the last weeks, I've removed the 550-dependency and brought it up to date with the trunk.

Second level suggesting (ngram token, phrase) can run stand alone. See TestTokenPhraseSuggester. However, I recommend the adaptive dictonary as it will act as a cache on top of second level suggestions. (See docs.)

Output from using adaptive layer only, i.e. suggestions based on how users previously behaved. About half a million user queries analyed to build the dictionary (takes 30 seconds to build on my dual core):

3ms pirates ofthe caribbean -> pirates of the caribbean
2ms pirates of the carribbean -> pirates of the caribbean
0ms pirates carricean -> pirates caribbean
1ms pirates of the carriben -> pirates of the caribbean
0ms pirates of the carabien -> pirates of the caribbean
0ms pirates of the carabbean -> pirates of the caribbean
1ms pirates og carribean -> pirates of the caribbean
0ms pirates of the caribbean music -> pirates of the caribbean soundtrack
0ms pirates of the caribbean soundtrack -> pirates of the caribbean score
0ms pirate of carabian -> pirate of caribbean
0ms pirate of caribbean -> pirates of caribbean
0ms pirates of caribbean -> pirates of caribbean
0ms homm 4 -> homm iv
0ms the pilates -> null

Using the phrase ngram token suggestion using token matrices checked against an apriori index. A lot of queries required for one suggestion. Instantiated index as apriori saves plenty of millis. This is expensive stuff, but works pretty good.

72ms the pilates -> the pirates
440ms heroes of fight and magic -> heroes of might and magic
417ms heroes of right and magic -> heroes of might and magic
383ms heroes of magic and light -> heroes of might and magic
20ms heroesof lightand magik -> null
385ms heroes of light and magik -> heroes of might and magic
0ms heroesof lightand magik -> heroes of might and magic
385ms heroes of magic and might -> heroes of might and magic

(That 0ms is becase previous was cached. One does not have to use this cache.)

Karl Wettin made changes - 17/Aug/07 12:10 AM

Attachment

LUCENE-626_20070817.patch [ 12363980 ]

[ Permlink | « Hide ]

Karl Wettin added a comment - 17/Aug/07 02:06 AM

RAMDirectory vs. InstantiatedIndex as apriori index: the latter is 5 to 25 times faster (leave first out).

RAMDirectory:
72ms the pilates -> the pirates
440ms heroes of fight and magic -> heroes of might and magic
417ms heroes of right and magic -> heroes of might and magic
383ms heroes of magic and light -> heroes of might and magic
20ms heroesof lightand magik -> null
385ms heroes of light and magik -> heroes of might and magic
0ms heroesof lightand magik -> heroes of might and magic
385ms heroes of magic and might -> heroes of might and magic

InstantiatedIndex:
171ms the pilates -> the pirates
66ms heroes of fight and magic -> heroes of might and magic
36ms heroes of right and magic -> heroes of might and magic
14ms heroes of magic and light -> heroes of might and magic
6ms heroesof lightand magik -> null
15ms heroes of light and magik -> heroes of might and magic
0ms heroesof lightand magik -> heroes of might and magic
16ms heroes of magic and might -> heroes of might and magic

[ Permlink | « Hide ]

Karl Wettin added a comment - 16/Oct/07 06:45 PM

New in this patch:

Dictionary persistence using BDB/je/3.2.44
Lots of refactoring to make the code easier to follow

Next patch will probably focus on:

Pruning of dictionary
Documentation of non-consumer methods

Karl Wettin made changes - 16/Oct/07 06:45 PM

Attachment

LUCENE-626_2007_10_16.txt [ 12367833 ]

Karl Wettin made changes - 16/Oct/07 06:45 PM

Attachment

didyoumean.patch.bz2 [ 12352515 ]

Karl Wettin made changes - 16/Oct/07 06:45 PM

Attachment

LUCENE-626_20070817.patch [ 12363980 ]

Karl Wettin made changes - 16/Oct/07 06:45 PM

Attachment

spellchecker.diff [ 12350263 ]

Karl Wettin made changes - 16/Oct/07 06:47 PM

Description

Extensive java docs available in patch, but I try to keep it compiled here: http://ginandtonique.org/~kalle/javadocs/didyoumean/org/apache/lucene/search/didyoumean/package-summary.html#package_description

Example:
{code:java}
public void testImportData() throws Exception {

    // load 200 000 user queries with session data and time stamp. no goals specified.

    System.out.println("Processing http://ginandtonique.org/~kalle/data/pirate.data.gz");
    importFile(new InputStreamReader(new GZIPInputStream(new URL("http://ginandtonique.org/~kalle/data/pirate.data.gz").openStream())));
    System.out.println("Processing http://ginandtonique.org/~kalle/data/hero.data.gz");
    importFile(new InputStreamReader(new GZIPInputStream(new URL("http://ginandtonique.org/~kalle/data/hero.data.gz").openStream())));
    System.out.println("Done.");

    // run some tests without the second level suggestions,
    // i.e. user behavioral data only. no ngrams or so.

    assertEquals("pirates of the caribbean", facade.didYouMean("pirates ofthe caribbean"));

    assertEquals("pirates of the caribbean", facade.didYouMean("pirates of the carribbean"));

    assertEquals("pirates caribbean", facade.didYouMean("pirates carricean"));
    assertEquals("pirates of the caribbean", facade.didYouMean("pirates of the carriben"));
    assertEquals("pirates of the caribbean", facade.didYouMean("pirates of the carabien"));
    assertEquals("pirates of the caribbean", facade.didYouMean("pirates of the carabbean"));

    assertEquals("pirates of the caribbean", facade.didYouMean("pirates og carribean"));

    assertEquals("pirates of the caribbean soundtrack", facade.didYouMean("pirates of the caribbean music"));
    assertEquals("pirates of the caribbean score", facade.didYouMean("pirates of the caribbean soundtrack"));

    assertEquals("pirate of caribbean", facade.didYouMean("pirate of carabian"));
    assertEquals("pirates of caribbean", facade.didYouMean("pirate of caribbean"));
    assertEquals("pirates of caribbean", facade.didYouMean("pirates of caribbean"));

    // depening on how many hits and goals are noted with these two queries
    // perhaps the delta should be added to a synonym dictionary?
    assertEquals("homm iv", facade.didYouMean("homm 4"));

    // not yet known.. and we have no second level yet.
    assertNull(facade.didYouMean("the pilates"));

    // use the dictionary built from user queries to build the token phrase and ngram suggester.
    facade.getDictionary().getPrioritesBySecondLevelSuggester().put(Factory.ngramTokenPhraseSuggesterFactory(facade.getDictionary()), 1d);

    // now it's learned
    assertEquals("the pirates", facade.didYouMean("the pilates"));

    // typos
    assertEquals("heroes of might and magic", facade.didYouMean("heroes of fight and magic"));
    assertEquals("heroes of might and magic", facade.didYouMean("heroes of right and magic"));
    assertEquals("heroes of might and magic", facade.didYouMean("heroes of magic and light"));

    // composite dictionary key not learned yet..
    assertEquals(null, facade.didYouMean("heroesof lightand magik"));
    // learn
    assertEquals("heroes of might and magic", facade.didYouMean("heroes of light and magik"));
    // test
    assertEquals("heroes of might and magic", facade.didYouMean("heroesof lightand magik"));

    // wrong term order
    assertEquals("heroes of might and magic", facade.didYouMean("heroes of magic and might"));

  }
{code}

Karl Wettin made changes - 23/Oct/07 08:17 PM

Assignee	Karl Wettin [ karl.wettin ]
Description	Extensive java docs available in patch, but I try to keep it compiled here: http://ginandtonique.org/~kalle/javadocs/didyoumean/org/apache/lucene/search/didyoumean/package-summary.html#package_description Example: {code:java} public void testImportData() throws Exception { // load 200 000 user queries with session data and time stamp. no goals specified. System.out.println("Processing http://ginandtonique.org/~kalle/data/pirate.data.gz"); importFile(new InputStreamReader(new GZIPInputStream(new URL("http://ginandtonique.org/~kalle/data/pirate.data.gz").openStream()))); System.out.println("Processing http://ginandtonique.org/~kalle/data/hero.data.gz"); importFile(new InputStreamReader(new GZIPInputStream(new URL("http://ginandtonique.org/~kalle/data/hero.data.gz").openStream()))); System.out.println("Done."); // run some tests without the second level suggestions, // i.e. user behavioral data only. no ngrams or so. assertEquals("pirates of the caribbean", facade.didYouMean("pirates ofthe caribbean")); assertEquals("pirates of the caribbean", facade.didYouMean("pirates of the carribbean")); assertEquals("pirates caribbean", facade.didYouMean("pirates carricean")); assertEquals("pirates of the caribbean", facade.didYouMean("pirates of the carriben")); assertEquals("pirates of the caribbean", facade.didYouMean("pirates of the carabien")); assertEquals("pirates of the caribbean", facade.didYouMean("pirates of the carabbean")); assertEquals("pirates of the caribbean", facade.didYouMean("pirates og carribean")); assertEquals("pirates of the caribbean soundtrack", facade.didYouMean("pirates of the caribbean music")); assertEquals("pirates of the caribbean score", facade.didYouMean("pirates of the caribbean soundtrack")); assertEquals("pirate of caribbean", facade.didYouMean("pirate of carabian")); assertEquals("pirates of caribbean", facade.didYouMean("pirate of caribbean")); assertEquals("pirates of caribbean", facade.didYouMean("pirates of caribbean")); // depening on how many hits and goals are noted with these two queries // perhaps the delta should be added to a synonym dictionary? assertEquals("homm iv", facade.didYouMean("homm 4")); // not yet known.. and we have no second level yet. assertNull(facade.didYouMean("the pilates")); // use the dictionary built from user queries to build the token phrase and ngram suggester. facade.getDictionary().getPrioritesBySecondLevelSuggester().put(Factory.ngramTokenPhraseSuggesterFactory(facade.getDictionary()), 1d); // now it's learned assertEquals("the pirates", facade.didYouMean("the pilates")); // typos assertEquals("heroes of might and magic", facade.didYouMean("heroes of fight and magic")); assertEquals("heroes of might and magic", facade.didYouMean("heroes of right and magic")); assertEquals("heroes of might and magic", facade.didYouMean("heroes of magic and light")); // composite dictionary key not learned yet.. assertEquals(null, facade.didYouMean("heroesof lightand magik")); // learn assertEquals("heroes of might and magic", facade.didYouMean("heroes of light and magik")); // test assertEquals("heroes of might and magic", facade.didYouMean("heroesof lightand magik")); // wrong term order assertEquals("heroes of might and magic", facade.didYouMean("heroes of magic and might")); } {code}	Extensive javadocs available in patch, but I also try to keep it compiled here: http://ginandtonique.org/~kalle/javadocs/didyoumean/org/apache/lucene/search/didyoumean/package-summary.html#package_description A semi-retarded reinforcement learning thingy backed by algorithmic second level suggestion schemes that learns from and adapts to user behavior as queries change, suggestions are accepted or declined, etc. Except for detecting spelling errors it considers context, composition/decomposition and a few other things. heroes of light and magik -> heroes of might and magic vinci da code -> da vinci code java docs -> javadocs blacksabbath -> black sabbath Depends on ~~LUCENE-550~~

Karl Wettin made changes - 23/Oct/07 08:18 PM

Attachment

LUCENE-626_2007_10_16.txt [ 12367833 ]

[ Permlink | « Hide ]

Karl Wettin added a comment - 23/Oct/07 08:18 PM

In this patch:

Updated package javadoc

Simplified consumer interface with persistent session management :

SuggestionFacade facade = new SuggestionFacade(new File("data"));
facade.getDictionary().getPrioritesBySecondLevelSuggester().putAll(facade.secondLevelSuggestionFactory());
...
QuerySession session = facade.getQuerySessionManager().sessionFactory();
...
String query = "heros of mght and magik";
Hits hits = searcher.search(queryFactory(query));
String suggested = facade.didYouMean(query);
session.query(query, hits.length(), suggested);
...
facade.getQuerySessionManager().getSessionsByID().put(session);
...
facade.trainExpiredSessions();
...
facade.close();

Optimizations. On my MacBook it now takes five minutes for the big unit test to process 3,500,000 queries: training the dictionary and extracts an a priori corpus by inverting the dictionary of the phrases and words people have most problem spelling.

Depends on ~~LUCENE-550~~ by default again. When it took 30 seconds to execute 100,000 span near queries in a RAMDirectory and less than one second to do the same witn an InstantiatedIndex it simply did not make sense to use RAMDirectory as default. Replacing one line of code removes the dependency to InstantiatedIndex.

New algorithmic second level suggester for queries containing terms not close enough in the text to be found in the a priori. Added with lowest priority and checks against the system index rather than the a priori index. Soon the second level suggster classes will needs a bit of refactoring.

Karl Wettin made changes - 23/Oct/07 08:18 PM

Attachment

LUCENE-626_20071023.txt [ 12368239 ]

[ Permlink | « Hide ]

Karl Wettin added a comment - 17/Apr/08 08:02 PM

If anyone have some rather large query logs with session id, time stamp and preferably click through data that I can test on this, that would be great. It really needs to be adjusted to more than one.