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

Co-Occurence Unit Terminology #19

Open
rhpoon opened this issue Apr 10, 2018 · 0 comments
Open

Co-Occurence Unit Terminology #19

rhpoon opened this issue Apr 10, 2018 · 0 comments

Comments

@rhpoon
Copy link

rhpoon commented Apr 10, 2018

Hi I read the ModelTrainingParameters.cs about the parameters setup and definetion.

Out of my limited study, I tend to think or suggest that the Co-Occurrence unit is more referring to a levelling:

User Level - measure co-occurence of items in same user (regardless of time/date)
TimeDate Level - on top of same user, it further measure whether it is same date/time (for the same user)

If my understanding, based on the /// comments as given, then the wording or term "level" would be more appropriate, as "Co-occurence Unit" as standalone may refer to:

User - items bought by same user (regardless of time/date)
TimeStamp - items bought within the same time stamp (mostly it is by the same user, but if there are multiple check out machine / POS.... they may come from different users

So there would be a subtle / potential difference and this also puzzle beginners to this recommender system (esp the use of term here slightly deviate from literature elsewhere (co-occurrence refer more to products/items matrix or dimension *.

*It may be such as case at the implementation internal of the software that such as matrix is established (Product Co-Ocurrence Matrix for same user or same time stamp), however the term presented as such cause confusion for serious learner.

Hence the wording: Co-occurrence Level or Focus is suggested (especially the word Unit may also refer to quantity).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant