Return-Path: Delivered-To: apmail-lucene-mahout-user-archive@minotaur.apache.org Received: (qmail 58193 invoked from network); 5 Nov 2009 13:08:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Nov 2009 13:08:40 -0000 Received: (qmail 74488 invoked by uid 500); 5 Nov 2009 13:08:40 -0000 Delivered-To: apmail-lucene-mahout-user-archive@lucene.apache.org Received: (qmail 74429 invoked by uid 500); 5 Nov 2009 13:08:39 -0000 Mailing-List: contact mahout-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mahout-user@lucene.apache.org Delivered-To: mailing list mahout-user@lucene.apache.org Received: (qmail 74419 invoked by uid 99); 5 Nov 2009 13:08:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Nov 2009 13:08:39 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of michal.shmueli@gmail.com designates 209.85.218.222 as permitted sender) Received: from [209.85.218.222] (HELO mail-bw0-f222.google.com) (209.85.218.222) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Nov 2009 13:08:31 +0000 Received: by bwz22 with SMTP id 22so10859073bwz.5 for ; Thu, 05 Nov 2009 05:08:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=Vrz8hHVpWWxkIJ+EKD/PpVMoachiTLeHbfRUOq5U5Sw=; b=ruyr4aXXXdW2xPtbsjZ6c7oODgcxfP4CdQJhXpSqugOWq+RFpP4Jj2dcNIsNWhnscd Clv3hWj6UAYe5lDkP4HdajW8ENtm5gwARQ1UHKHhxOfjf6iF9P4r2VMcYRX7dWynbfY/ fWfG4RTdT4su/a02ChI8NEoLt13jretvaxd6g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=KB2WJQoWsM4S+q6kgVveAJ6Z9YRcOiJxK6RWtInOddPLLsBJKcgX/P8bVArc9H+Hjt kEGDWrywTaXJ4pcco96gk8dn5h3gB/2XYy+BE/WgLKXWkFpY2OZ0omMebX/wgX2R1C/S v83GrgoL232TxU6ew9D6jYsyqrQeteU/QUmfw= MIME-Version: 1.0 Received: by 10.102.216.8 with SMTP id o8mr1164242mug.20.1257426491196; Thu, 05 Nov 2009 05:08:11 -0800 (PST) In-Reply-To: References: <394845f40911040422s4639e475ve574aac8348bf7d2@mail.gmail.com> <394845f40911042258q353dc885ic99597eaea14d48e@mail.gmail.com> <394845f40911050406r3dd11ddfu24fe95039f6755fd@mail.gmail.com> Date: Thu, 5 Nov 2009 15:08:11 +0200 Message-ID: <394845f40911050508m13c3a4f2teb90d76285df8e5d@mail.gmail.com> Subject: Re: problems with GenericRecommenderIRStatsEvaluator: From: michal shmueli To: mahout-user@lucene.apache.org Content-Type: multipart/alternative; boundary=0016364167f956c7ee04779f6bc7 X-Virus-Checked: Checked by ClamAV on apache.org --0016364167f956c7ee04779f6bc7 Content-Type: text/plain; charset=ISO-8859-1 The way i envision this is the follow: assume user rates 10 items, this 10 are the correct items. Further assume that for recommendation we use subset of this 10 items, say 70% (leave us with 30% for test) to build the similarity, etc. Now, during evaluation, we ask from the recommneder for say k items, and we check how many from the 3 correct item (the 30% of the tests) are within the k recommended items. This solutions ignore the ranking on the different items, however, this could be also added later. Does it make sense? thanks, Michal On Thu, Nov 5, 2009 at 2:16 PM, Sean Owen wrote: > It doesn't simulate "training" and "test", that's what I'm saying. > This concept exists in RecommenderEvaluator, not > RecommenderIRStatsEvaluator. They're reasonably different things. > > In RecommenderIRStatsEvaluator, there is instead a "relevance > threshold" parameter. > > But the final parameter, which you refer to, is something else still. > It simply controls what percentage of all data to use. It's a simple > way to use a lot less data to produce a result faster. > > You are right that in your 'boolean' data, all preference values are > effectively 1.0. So passing a 1.0 means that all items are considered > relevant. That's fine, that's reasonable. While the framework > typically removes all relevant items from a user for test purposes, it > will remove only up to "at" items -- that is, if you are evaluating > precision at 5, it will remove up to 5 items. In this case they are > effectively randomly chosen since all items are equal. > > How would you like it to choose the relevant and not relevant items in > this case? we can figure out how to do it then. > > Sean > > On Thu, Nov 5, 2009 at 12:06 PM, michal shmueli > wrote: > > >> I still don't get why this parameter simulates the "training" and > > the "test". In addition, since my data is Boolean, ain't it mean that > anyway > > what is 1 is relevant ? Is there another way to tell the recommender how > to > > chose the training and test sets? > --0016364167f956c7ee04779f6bc7--