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
When I'm using topic modeling widget at Windows 11 using AMD Processor, that accepts input from Bag Of Words -> (Corpus) -> Topic Modeling. It will stuck at 100% for LSI and 0% with LDA. If I click something in my screen, it will said python is not responding and the screen will go blank. I'm only using 100 inputs of tweet. But if I'm using topic modeling widget with the same workflow in Mac OS, it will be fast and there's no problem.
I already tried the solution from previous issues which is marked as complete.
Python Version : 3.9.12
Gensim Version: 4.3.2
Orange3-Text Version : 1.15
Orange Version 3.36.2
Sometimes the LSI will be success and changin the topic modeling technique from LSI to LDA will be executed instantly.
I already try this in 4 other laptop, which 3 using AMD processor and 1 using Intel.
The problem only occurs with the AMD one.
Thank you
The text was updated successfully, but these errors were encountered:
When I'm using topic modeling widget at Windows 11 using AMD Processor, that accepts input from Bag Of Words -> (Corpus) -> Topic Modeling. It will stuck at 100% for LSI and 0% with LDA. If I click something in my screen, it will said python is not responding and the screen will go blank. I'm only using 100 inputs of tweet. But if I'm using topic modeling widget with the same workflow in Mac OS, it will be fast and there's no problem.
I already tried the solution from previous issues which is marked as complete.
Python Version : 3.9.12
Gensim Version: 4.3.2
Orange3-Text Version : 1.15
Orange Version 3.36.2
Sometimes the LSI will be success and changin the topic modeling technique from LSI to LDA will be executed instantly.
I already try this in 4 other laptop, which 3 using AMD processor and 1 using Intel.
The problem only occurs with the AMD one.
Thank you
The text was updated successfully, but these errors were encountered: