Hi i need some help, maybe its my fault but i dont know where this comes from. I installed

  1. Recommender API 7.x-4.0-alpha14
  2. Browser History 7.x-1.0-alpha6

Followed the documentation. All fine, similarities where found by mahout but no predictions. If i switched to source=access.log then nothing whether similarity or prediction items where found. The cont of total scanned items is still the same. If i now switch back to history source then this doesn't work too. Reinstallation of both modules doesn't fix it.

Need some help here to get predictions work and get the functionality of similarities back. Maybe there is a cache or other to clear if i switch the methods?

Comments

danithaca’s picture

danithaca commented
Status: Active » Postponed (maintainer needs more info)

You need data to see the recommendations. Please provide more info:
1) number of items/users in your drupal site
2) screen shot of the recommender running history

I'll take a look when you provide those information.

danithaca’s picture

danithaca commented
Issue summary: View changes

Added reinstallation test

stesind’s picture

stesind commented
Issue summary: View changes

I have the same problem with latest Drupal 7.27.

Using history table I have:

Users: 43. Items: 155. (Time spent: 0h0m4s) Users 43 Items 155 Similarity 8,595 Predictions 3,216

Changing to accesslog:

Success Users: 0. Items: 0. (Time spent: 0h0m1s)

My accesslog table is filled with 1205 records, but no outcome in similarity nor predictions.

stesind’s picture

stesind commented
Category: Support request » Bug report
Status: Postponed (maintainer needs more info) » Active
raj.chourasia’s picture

raj.chourasia commented

Having the same issue.

raj.chourasia’s picture

raj.chourasia commented

Started working when i generated traffic from 10+ different ip's.

stesind’s picture

stesind commented

In my accesslog I have 180,000+ records. But still no records for calculation.

stesind’s picture

stesind commented

OK, I have finally found some time to debug and found out.

The history_rec reads data from the accesslog table in bunches of 50,000 every cron run. Unfortunately it does not start at the first aid it finds, but at 0. As in my case the aid in accesslog starts at 600000+, so it takes a few cron jobs, which are executed every 30 mins, to fill the user map table. On my testing machine I never met this point since it whould have taken 6.5 hours.

Solution: set it up and wait a few days.

stesind’s picture

stesind commented
Status: Active » Closed (works as designed)