Update content personalization #1333
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The goal of this PR is to clarify/improve how to do recsys with River. There's a tutorial called
content-personalization.ipynbwhich should showcase these changes. The end-goal is to look a bit more like what Vowpal Wabbit does here. We are a bit different than VW in that we have more pure recsys models (I'm thinking about FunkMF and other stuff in therecomodule) whilst less contextual bandit stuff (we have LinUCB but it's not very fast). I see a way forward to improve therecomodule so that it can do recsys by itself, whilst also allowing the use of (contextual) bandit policies.Here's a todo:
recomodule. We can rank items. We can then do sampling. But it’s not clear how to this in an optimal fashion. There needs to be some kind of exploration/exploitation tradeoff. How does Vowpal Wabbit do this?recomodule to make it usable in a recsys context.There's a quite a lot of work to do, and I'm not sure I'll have time to finish. So I'll keep this PR in draft-mode, and we'll see what happens.