cdipaolo/goml

Roadmap / Comparison to other Go ML libraries

Opened this issue · 1 comments

derekperkins commented

How does goml compare to some of the other Go libraries in terms of product vision / roadmap?

There's a decent amount of overlap in terms of the implemented algorithms / models. Is your goal to eventually include all of the other types (neural networks, collaborative filtering, etc)? It seems like the stated goal of being more stream oriented than batch oriented differentiates this library too.

At the end of the day, this seems like the most active repo with an exciting direction. I'm very curious to know where you plan on taking things.

cdipaolo commented

Yeah I'd like to implement a bunch of other types of models. I'll write up
a roadmap when I have some free time (currently adding k-means++
instantiation to the batch k-means.)

I hope to base this library on online models/versions of models, but I want
to give the optionality to use batch methods so people won't have to switch
libraries to work with a potentially better model.

Let me know any questions, opinions, comments, etc. you may have.
On Tue, Aug 18, 2015 at 11:37 AM Derek Perkins notifications@github.com
wrote:

How does goml compare to some of the other Go libraries in terms of
product vision / roadmap?

There's a decent amount of overlap in terms of the implemented algorithms
/ models. Is your goal to eventually include all of the other types (neural
networks, collaborative filtering, etc)? It seems like the stated goal of
being more stream oriented than batch oriented differentiates this library
too.

At the end of the day, this seems like the most active repo with an
exciting direction. I'm very curious to know where you plan on taking
things.

—
Reply to this email directly or view it on GitHub
#3.