Repository navigation
Replies: 1 comment
|
The merged topics are indeed not directly tracked between operations as that would require quite some tracking. Instead, you can take a document from topic 1 before merging and see what topic it becomes after merging. The updated topics can be found in |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
I have a list of around 170 clusters, some of which are similar and so I decided to use 'merge_topic' to merge them together and decrease the clusters size. It's unclear how some of the new merged clusters relate to the 'merge_topic' list. Is there a way to check say the new cluster 0 , relates to the second list in the 'merge_topic'? Thank you
I used this as an example:
topics_to_merge = [[1, 2],
[3, 4]]
topic_model.merge_topics(docs, topics_to_merge)
All reactions