You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 30, 2021. It is now read-only.
Here is a screenshot, as one can see significant terms and terms return very different results in terms of ORDERING, while the count is the same. The issue is that they look the same when rendered on wordcloud (given that this will only use counts)
Wordcloud should ignore kind of ignore COUNTS but instead use the given SCORE.
Alternatively it could combine score (which is the most important thing ) with a function of count and BGcount (bgcount is the number of hits in the whole corpus)
Note there is a related, yet apparently abandoned issue in kibana. elastic/kibana#2018
(its about showing something of the BG count too)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Here is a screenshot, as one can see significant terms and terms return very different results in terms of ORDERING, while the count is the same. The issue is that they look the same when rendered on wordcloud (given that this will only use counts)
Wordcloud should ignore kind of ignore COUNTS but instead use the given SCORE.
Alternatively it could combine score (which is the most important thing ) with a function of count and BGcount (bgcount is the number of hits in the whole corpus)
Note there is a related, yet apparently abandoned issue in kibana. elastic/kibana#2018
(its about showing something of the BG count too)
The text was updated successfully, but these errors were encountered: