gensim VS tensorflow

This is our optimization problem. Now, we hope that you have an idea of what our goal is. Luckily for us, this is already implemented in a Python module called gensim. Yes, these guys are brilliant in natural language processing and we will make use of it. 🤝

Try LDA as implemented in gemsin https://github.com/RaRe-Technologies/gensim

Standout python NLP libraries include Spacy and Gensim, as well as pre-trained model availability in Hugginface. These libraries have widespread use in and support from industry and it shows. Spacy has best-in-class methods for pre-processing text for further applications. Gensim helps you manage your corpus of documents, and contains a lot of different tools for solving a common industry task, topic modeling.

Here we have to install the gensim library in a jupyter notebook to be able to use it in our project, consider the code below;

Nice work! I wonder if you're going the same challenges that gensim had for being generic in summarization.

For context:

> Despite its general-sounding name, the module will not satisfy the majority of use cases in production and is likely to waste people's time.

https://github.com/RaRe-Technologies/gensim/wiki/Migrating-f...

TextRank will work without any problems. https://radimrehurek.com/gensim/

For the topic modelling itself, I am going to use Gensim library by Radim Rehurek, which is very developer friendly and easy to use.

To get up to speed with TensorFlow, check their quickstart Support TensorFlow on GitHub ⭐

Explore here.

Part of the major userbase pull in GitHub revolves around hosting a considerable number of popular projects including Angular, React, Kubernetes, cpython, Ruby, tensorflow, and well even the software that powers this site Forem.

Right but that's not an inherent GPU determinism issue. It's a software issue.

https://github.com/tensorflow/tensorflow/issues/3103#issueco... is correct that it's not necessary, it's a choice.

Your line of reasoning appears to be "GPUs are inherently non-deterministic don't be quick to judge someone's code" which as far as I can tell is dead wrong.

Admittedly there are some cases and instructions that may result in non-determinism but they are inherently necessary. The author should thinking carefully before introducing non-determinism. There are many scenarios where it is irrelevant, but ultimately the issue we are discussing here isn't the GPU's fault.

and things like y = layers.ELU()(y) work as expected. I wanted to see a list of the available layers so I went to the Tensorflow GitHub repository and to the keras directory. There's a warning in that directory that says:

Exactly what language do you think TensorFlow is written in? :)

You can use Tensorflow's deep learning API for this.

Since you've specifically mentioned ML, here's Tenserflow's GitHub. I'm sure a quick glance through that will change your mind.