-
Notifications
You must be signed in to change notification settings - Fork 149
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
Rearrange examples and models #542
Comments
Agreed with this. Could I suggest that we do something like this:
That way, we can group different models together (e.g. graph models, ranking models). |
Shall we have multiple hierarchies for grouping models into tasks (general recommendation, next-item recommendation, next-basket recommendation) or modalities (text or review, graph, image, sentiment), etc? |
Taking into consideration the increase in methods and number of models, could I suggest something like the following:
Feel free to suggest a better structure too. Thanks! |
@lthoang what do think about the suggestion by @darrylong? Do you think it’s a good idea to only keep generic examples here and move most of the examples into their corresponding model folders? |
Does it make sense to move all NEW models into their categorization folder?
I feel it's easier to navigate through the models when I approach a new recommender problem. |
@hieuddo I think it’s also a good idea to restructure the models folder. However, it’s a bit more complicated and involved than this one. How about we focus on the examples folder first? This exercise will also give us better idea on how we want to categorize models. Would you mind creating another issue for your suggestion above? |
Description
I was thinking to rearrange some files in examples folder into model-specific folders. We only retain the ones for basic usage. It will help tidy up examples folder a bit. At the same time, we can have a README file in each of the model folders for any relevant information (i.e., paper, authors, requirements, how-to-run example, any results/reproducibility/notes about the model, etc). Currently, when we click on a model from the main README, it opens the model folder without any useful information inside.
Expected behavior with the suggested feature
Other Comments
The text was updated successfully, but these errors were encountered: