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
I recently noticed that the topic numbers that result from lda_model$plot() differ from those that lda_model$get_top_words() produces.
For example, if I run lda_model$plot(n=5, lambda =0.6), the bubble for topic #1 actually aligns perfectly with topic #15 from lda_model$get_top_words(). I checked and the plot is not reordering topics, so I cannot figure out why this is happening.
Ideally I'd like to produce a list of the top terms for each topic using lda_model$get_top_words(), and also use the LDAvis plot from lda_model$plot() to explore them even further, but this is difficult to do without the topic numbers matching.
The text was updated successfully, but these errors were encountered:
Hi @fishdontfly. This is due to the fact that LDAvis CRAN version is dated 2015. Please install latest from github (devtools::install_github("cpsievert/LDAvis")) - after that it will work as you expect.
This is related to #233 - once it will be rewritten in text2vec we won't be depend on unreleased version of LDAvis.
dselivanov
changed the title
Topic Numers/Labels
Topic Numers/Labels in LDAvis
Jun 5, 2018
Thank you for creating such a useful package!
I recently noticed that the topic numbers that result from lda_model$plot() differ from those that lda_model$get_top_words() produces.
For example, if I run lda_model$plot(n=5, lambda =0.6), the bubble for topic #1 actually aligns perfectly with topic #15 from lda_model$get_top_words(). I checked and the plot is not reordering topics, so I cannot figure out why this is happening.
Ideally I'd like to produce a list of the top terms for each topic using lda_model$get_top_words(), and also use the LDAvis plot from lda_model$plot() to explore them even further, but this is difficult to do without the topic numbers matching.
The text was updated successfully, but these errors were encountered: