[
https://issues.apache.org/jira/browse/MAHOUT-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864334#action_12864334
]
Sean Owen commented on MAHOUT-389:
--
De-emphasizing common items is often desir
[
https://issues.apache.org/jira/browse/MAHOUT-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864296#action_12864296
]
Sean Owen commented on MAHOUT-391:
--
Hm, that method has been in JUnit since ancient t
[
https://issues.apache.org/jira/browse/MAHOUT-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863861#action_12863861
]
Sean Owen commented on MAHOUT-389:
--
The issue with that is you are implicitly assu
[
https://issues.apache.org/jira/browse/MAHOUT-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen updated MAHOUT-387:
-
Priority: Minor (was: Major)
Nevermind I'll add UncenteredCosineSimilarity, can't hurt
>
[
https://issues.apache.org/jira/browse/MAHOUT-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen resolved MAHOUT-387.
--
Fix Version/s: 0.4
(was: 0.3)
Resolution: Fixed
> Cosine item similar
[
https://issues.apache.org/jira/browse/MAHOUT-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen reopened MAHOUT-387:
--
> Cosine item similarity implementation
> -
>
>
Actually scratch that patch I sent over. I see the trick now that
makes the existing approach quite good. I think I can make a version
that preserves that trick and still streamlines the processing. I will
benchmark and report back if successful.
On Wed, Apr 28, 2010 at 3:20 PM, Sean Owen wrote
0 items
> P = 50,000,000 preferences
>
> P*I = 250 billion
> P2/U = 2,5 billion
>
> -
> Or stated as inequality:
>
> P2/U > PI
> P/U > I
> P > UI <-- obviously not true
>
>
> Sean Owen schrieb:
>> Well it
It should only have been used in places where the Vector needed a name
-- where getName() or setName() was called. That was the intent at
least.
This code snippet looks familiar; aren't the members of this
collection used as NamedVector later?
Well to be sure you can change any occurrences back t
Good eye, this was fixed in the manuscript a while ago.
I will ping Manning to re-publish Chapters 1-6 since a lot of small
updates have happened since then.
On Fri, Apr 23, 2010 at 4:53 PM, Jeff Eastman
wrote:
> Section 4.5.1 says:
> "The third line shows how it is based on item-item similariti
[
https://issues.apache.org/jira/browse/MAHOUT-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen resolved MAHOUT-382.
--
Assignee: Sean Owen
Fix Version/s: 0.3
(was: 0.4)
Resolution
[
https://issues.apache.org/jira/browse/MAHOUT-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen updated MAHOUT-381:
-
Assignee: Sean Owen
Priority: Minor (was: Major)
> org.apache.mahout.cf.taste.hadoop.item is m
More on Vector, as I'm browsing through it:
AbstractVector.minus(Vector) says:
public Vector minus(Vector x) {
if (size() != x.size()) {
throw new CardinalityException();
}
if (x instanceof RandomAccessSparseVector || x instanceof DenseVector) {
// TODO: if both are Rand
13 matches
Mail list logo
