mahout-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claudia Grieco" <gri...@crmpa.unisa.it>
Subject R: R: R: R: Problems with evaluator.
Date Thu, 27 Aug 2009 09:54:57 GMT
Oh, I see, I was using even an older version of the mahout code, and this problem had been
fixed after. I had downloaded the before-150 code but forgot to substitute the libraries

-----Messaggio originale-----
Da: Claudia Grieco [mailto:grieco@crmpa.unisa.it] 
Inviato: giovedì 27 agosto 2009 11.42
A: mahout-user@lucene.apache.org
Oggetto: R: R: R: R: Problems with evaluator.

But since I'm using boolean preference data, all the preferences are relevant (score 1) so
they are all erased from the training data:

for (Preference pref : prefs) {
          if (pref.getValue() >= theRelevanceThreshold) {
            relevantItems.add(pref.getItem());
          }
        }

-----Messaggio originale-----
Da: Sean Owen [mailto:srowen@gmail.com] 
Inviato: giovedì 27 agosto 2009 11.29
A: mahout-user@lucene.apache.org
Oggetto: Re: R: R: R: Problems with evaluator.

Yes, that is correct. The framework splits the user's preferences into
"relevant" and "not relevant" items. It then takes away the relevant
items, and leaves the non-relevant items in the training data. Then,
it sees how many of those relevant items are recommended back to the
user, to compute precision and recall.

On Thu, Aug 27, 2009 at 10:24 AM, Claudia Grieco<grieco@crmpa.unisa.it> wrote:
> Notice this part:
> for (Preference pref : prefs2) {
>        if (!relevantItems.contains(pref.getItem())) {
>          trainingPrefs.add(pref);
>        }}
> It adds a preference only if it's NOT in the relevant items


Mime
View raw message