lyst / lyst/lightfm

Can the user user features for train be used for test if the data is chronological

Open
#614 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
5.1k
Forks
724
PR merge metrics
No merged PRs in 30d

Description

If we train a recommender system using Light FM and want to pass user features, how to do that in data that is time-dependent.

For evaluation, we divide the data into training and test set depending on date.

Item feature would be static so should be good.
But what about user features, such as average order value etc?
That would be different in the train and test dataset. And I would assume that won't work seeing the way we are creating the user feature.

Any advice on how to do that?

Also, how user features can be used? As in do we use it to get similar user.
Asking this because we have order history for the users and discounts that they have used. but we do not have same for train set(as the orders haven't been made).
So if we use it for similarity that would be fine.

So if you can give a little background on how these ffeatures are being used in the background, that would be very helpful.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start by locating the LightFM documentation and examples for user and item features, then clarify how chronological train/test data should be handled and what feature use is supported. Done means the issue has concrete, documented guidance rather than an unresolved usage question.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.