Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[QST] Projecting inputs of NextItemPredictionTask to'64' As weight tying requires the input dimension '320' to be equal to the item-id embedding dimension '64' #750

Closed
ralgond opened this issue Oct 14, 2023 · 4 comments

Comments

@ralgond
Copy link

ralgond commented Oct 14, 2023

Projecting inputs of NextItemPredictionTask to'64' As weight tying requires the input dimension '320' to be equal to the item-id embedding dimension '64'. Should I care the warning?

Details

I found a warning on this example page:

https://nvidia-merlin.github.io/Transformers4Rec/stable/examples/end-to-end-session-based/02-End-to-end-session-based-with-Yoochoose-PyT.html

Should I care the warning?

Thank you.

@rnyak
Copy link
Contributor

rnyak commented Oct 15, 2023

@ralgond you can ignore the warning, it is telling that the it applies projection and it will be projected to the item_id embedding dimension which is 64 by default. Note that you can also change this embedding dimension if you want.

@ralgond
Copy link
Author

ralgond commented Oct 17, 2023

So how can I change the item embedding dimension?

@rnyak
Copy link
Contributor

rnyak commented Oct 17, 2023

you can add it here: inputs = tr.TabularSequenceFeatures.from_schema(...) as an argument of embedding_dims.

Please see this ticket as well.

@rnyak
Copy link
Contributor

rnyak commented Nov 27, 2023

closing this due to low activity.

@rnyak rnyak closed this as completed Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants