lyst / lyst/lightfm

recommendations for cold start users when model trained without user_features?

Open
#645 1 comment 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

Due to the getting the same recommendations for almost all users, I trained the model without user_features as was suggested in [here](https://github.com/lyst/lightfm/issues/320#issuecomment-401329449) (~90 unique items are recommended). The model training is like so:
```
model = LightFM(no_components= embedding_dimension, learning_rate=0.01, loss='bpr',
learning_schedule = 'adadelta', random_state=seed)
model.fit(train_interactions,
epochs=NUM_EPOCHS,
num_threads=20,
verbose=True)
```
During the inference, for the cold and existing customers, I did the following as was suggested [here](https://github.com/lyst/lightfm/issues/210#issuecomment-324387779):
```
if not cold_start_user_flg:
scores = model.predict(user_ids=user_id_map[user_id],
item_ids=np.arange(n_items),
num_threads=20
)
else:
scores = model.predict(user_ids=0,
item_ids=np.arange(n_items),
user_features=user_feature_cold_start,
num_threads=20
)
```
My question is since the model got trained without user_features, how is it even able to provide recommendations for cold-start users?

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

Start with the linked discussions and the fit and predict calls shown in the report. Trace how user_features are supplied during training and inference, then document whether this usage can provide cold-start recommendations and what inputs are required; done means the behavior is clearly explained.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.