NVIDIA-Merlin / NVIDIA-Merlin/Transformers4Rec

[QST] Understanding the feature dependency from Example

Open
#387 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/examples question
Dominant language
Python
Stars
1.3k
Forks
165
Avg merge
1m
Merged PRs (30d)
2

Description

❓ Questions & Help

While training the model we are taking multiple features which also includes 'item_id-list_seq', 'category-list_seq' as categorical features and 'product_recency_days_log_norm-list_seq', 'et_dayofweek_sin-list_seq' as continuous variables. As per my understanding of training task the model is learning all 4 features separately and while evaluating it predicts all the features and take their ground truth to provide NDGC and recall.

If that's the case just wanted to understand that are the continuous features 'product_recency_days_log_norm-list_seq', 'et_dayofweek_sin-list_seq' needed by the model because as per my understanding these features are impacting the final results. Predicting the recency and time of interaction can be a tough task.

Could you please explain the dependency of these features and correct me if I have misunderstood any of the point.
I have tried training model only on categorical features and the results are pretty good, the model is able to predict next item id and category at a very good NDGC and recall.

Thanks

Contributor guide

Open the contributing guide

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 files, tests, or entry points are named. Start by tracing the training and evaluation behavior described in the question, then document whether the continuous features are required and how feature predictions and ground truth affect NDCG and recall.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, pytorch
Domain
machine-learning
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.