mahout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAHOUT-103) Co-occurence based nearest neighbourhood
Date Tue, 17 Mar 2009 13:42:50 GMT

    [ https://issues.apache.org/jira/browse/MAHOUT-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682674#action_12682674
] 

Sean Owen commented on MAHOUT-103:
----------------------------------

Oh my just saw this. My thoughts after looking at the patch:

Overall this feels like its doing the same thing as a combination of TanimotoCoefficientSimilarity
and BooleanPreferenceUser -- defining user/item similarity in terms of simple co-occurrence
of items in users. 

In particular FitnessEvaluator looks like the same thing as ItemSimilarity. Click feels like
a domain-specific class -- to represent an Item in the framework that doesn't have an associated
pref value, use BooleanUserPreference with GenericUser.

The Hadoop job likewise seems domain-specific.

> Co-occurence based nearest neighbourhood
> ----------------------------------------
>
>                 Key: MAHOUT-103
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-103
>             Project: Mahout
>          Issue Type: New Feature
>          Components: Collaborative Filtering
>            Reporter: Ankur
>            Assignee: Ankur
>         Attachments: jira-103.patch
>
>
> Nearest neighborhood type queries for users/items can be answered efficiently and effectively
by analyzing the co-occurrence model of a user/item w.r.t another. This patch aims at providing
an implementation for answering such queries based upon simple co-occurrence counts.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message