[
https://issues.apache.org/jira/browse/MAHOUT-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662213#action_12662213
]
Sean Owen commented on MAHOUT-95:
---------------------------------
It's been a while since I looked at this so apologies if I lost the original
point --
I think the bit you want to change is the inner class Estimator. estimate()
should return NaN if the similarity it computes is below your threshold. Then
you don't need changes to getTopUsers() or Rescorers (indeed Rescorer<Item>
doesn't seem to be what you want). The only chnage you need is what's in your
patch now -- a new parameter to the constructor that is made available to
Estimator then.
> UserSimilarity-based NearestNNeighborhood
> -----------------------------------------
>
> Key: MAHOUT-95
> URL: https://issues.apache.org/jira/browse/MAHOUT-95
> Project: Mahout
> Issue Type: Improvement
> Components: Collaborative Filtering
> Reporter: Otis Gospodnetic
> Priority: Minor
> Attachments: MAHOUT-95-diff-against-nearestN.txt, MAHOUT-95.patch,
> MAHOUT-95.patch
>
>
> A variation of NearestNUserNeighborhood. This version adds the minSimilarity
> parameter, which is the primary factor for including/excluding other users
> from the target user's neighbourhood. Additionally, the 'n' parameter was
> renamed to maxHoodSize and is used to optionally limit the size of the
> neighbourhood.
> The patch is for a brand new class, but we may really want just a single
> class (either keep this one and axe NearestNUserNeighborhood or add this
> functionality to NearestNUserNeighborhood), if this sounds good.
> I'll update the unit test and provide a patch for that if others think this
> can go in.
> Thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
