mahout-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sebastian Schelter <...@apache.org>
Subject Re: Setting up a recommender
Date Fri, 02 Aug 2013 21:13:01 GMT
I really like this approach, especially as it makes it possible to
individually recompute and update certain similarity matrices. Furthermore
it should enable rapid experimentation as its super easy to retrieve
recommendations based on differed behaviors.

2013/8/2 Ted Dunning <ted.dunning@gmail.com>

> So there is a lot of good discussion here and there were some key ideas.
>
> The first idea is that the *input* to a recommender is on the right in the
> matrix notation.  This refers inherently to the id's on the columns of the
> recommender product (either B'B or B'A).  The columns are defined by the
> right hand element of the product (either B or A in the B'B and B'A
> respectively).
>
> The results are in the row space and are defined by the left hand operand
> of the product.  IN the case of B'A and B'B, the left hand operand is B in
> both cases so the row space is consistent.
>
> In order to implement this in a search engine, we need documents that
> correspond to rows of B'A or B'B.  These are the same as the columns of B.
>  The fields of the documents will necessarily include the following:
>
> id: the column id from B corresponding to this item
> description: presentation info ... yada yada
> b-a-links: contents of this row of B'A expressed as id's from the column
> space of A where this row                  of llr-filter(B'A) contains a
> non-zero value.
> b-b-links: contents of this row of B'B expressed as id's from the column
> space of B ...
>
>
> The following operations are now single queries:
>
> get an item where id = x
>        query is [id:x]
>
> recommend based on behavior with regard to A items and actions h_a
>        query is [b-a-links: h_a]
>
> recommend based on behavior with regard to B items and actions h_b
>        query is [b-b-links: h_b]
>
> recommend based on a single item with id = x
>         query is [b-b-links: x]
>
> recommend based on composite behavior composed of h_a and h_b
>         query is [b-a-links: h_a b-b-links: h_b]
>
> Does this make sense by being more explicit?
>
> Now, it is pretty clear that we could have an index of A objects as well
> but the link fields would have to be a-a-links and a-b-links, of course.
>
>
>
>
> On Fri, Aug 2, 2013 at 1:25 PM, Pat Ferrel <pat.ferrel@gmail.com> wrote:
>
> > Assuming Ted needs to call it, not sure if an invite has gone out, I
> > haven't seen one.
> >
> > On Aug 2, 2013, at 12:49 PM, B Lyon <bradflyon@gmail.com> wrote:
> >
> > I am planning on sitting in as flaky connection allows.
> > On Aug 2, 2013 3:21 PM, "Pat Ferrel" <pat.ferrel@gmail.com> wrote:
> >
> > > We doing a hangout at 2 on the Solr recommender?
> > >
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message