Author: buildbot
Date: Tue Jul 8 01:13:31 2014
New Revision: 915434
Log:
Staging update by buildbot for mahout
Modified:
websites/staging/mahout/trunk/content/ (props changed)
websites/staging/mahout/trunk/content/users/recommender/intro-als-hadoop.html
Propchange: websites/staging/mahout/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jul 8 01:13:31 2014
@@ -1 +1 @@
-1607942
+1608637
Modified:
websites/staging/mahout/trunk/content/users/recommender/intro-als-hadoop.html
==============================================================================
---
websites/staging/mahout/trunk/content/users/recommender/intro-als-hadoop.html
(original)
+++
websites/staging/mahout/trunk/content/users/recommender/intro-als-hadoop.html
Tue Jul 8 01:13:31 2014
@@ -285,7 +285,10 @@ and it outputs a list of recommended ite
<h2 id="example">Example</h2>
<p>Letâs look at a simple example of how we could use Mahoutâs ALS
recommender to recommend items for users. First, youâll need to get Mahout up
and running, the instructions for which can be found <a
href="https://mahout.apache.org/users/basics/quickstart.html";>here</a>. After
you've ensured Mahout is properly installed, weâre ready to run the
example.</p>
<p><strong>Step 1: Prepare test data</strong></p>
-<p>Similar to Mahout's item based recommender, the ALS recommender relies on
the user to item preference data: <em>userID</em>, <em>itemID</em> and
<em>preference</em>. The preference could be explicit numeric rating or counts
of actions such as a click (implicit feedback). The test data file is organized
as each line is a tab-delimited string, the 1st field is user id, which must be
numeric, the 2nd field is item id, which must be numeric and the 3rd field is
preference, which should also be a number. </p>
+<p>Similar to Mahout's item based recommender, the ALS recommender relies on
the user to item preference data: <em>userID</em>, <em>itemID</em> and
<em>preference</em>. The preference could be explicit numeric rating or counts
of actions such as a click (implicit feedback). The test data file is organized
as each line is a tab-delimited string, the 1st field is user id, which must be
numeric, the 2nd field is item id, which must be numeric and the 3rd field is
preference, which should also be a number.</p>
+<p><strong>Note:</strong> You must create IDs that are ordinal positive
integers for all user and item IDs. Often this will require you to keep a
dictionary
+to map into and out of Mahout IDs. For instance if the first user has ID "xyz"
in your application, this would get an Mahout ID of the integer 1 and so on.
The same
+for item IDs. Then after recommendations are calculated you will have to
translate the Mahout user and item IDs back into your application IDs.</p>
<p>To quickly start, you could specify a text file like following as the input:
<pre>
1 100 1
