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
Reading the source code (bertopic version 0.17.3), I realised that :
to compute the dendogram in visualize_hierarchy, the default behaviour was to use the the c-TF-IDF embeddings and the ward linkage function (cf _bertopic.py L3064 and L3099).
to reduce the number of topics in _reduce_to_n_topics, the default behaviour was to use the topic embeddings and the average linkage function (cf _bertopic.py L4442 and L4464).
This made me confused, as I'd expect that the visualisation method and the topic reduction method to follow the same logic.
My question is: why not using the same linkage function? Why using the C-TF-IDF embeddings?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Reading the source code (bertopic version 0.17.3), I realised that :
visualize_hierarchy, the default behaviour was to use the the c-TF-IDF embeddings and the ward linkage function (cf _bertopic.py L3064 and L3099)._reduce_to_n_topics, the default behaviour was to use the topic embeddings and the average linkage function (cf _bertopic.py L4442 and L4464).This made me confused, as I'd expect that the visualisation method and the topic reduction method to follow the same logic.
My question is: why not using the same linkage function? Why using the C-TF-IDF embeddings?
Thank you for your time.
Beta Was this translation helpful? Give feedback.
All reactions