Chih-Wei Chang

Then I think we may need to implement some basic matrix computation algorithms first? If we want to re-build whole algorithms, it's definitely we will heavily need some fundamental infrastructures.

If we want to do so many things by ourself, we probably should think a better way to organize the packages / subpackages etc. Any thought on this?

Agree! We do need some formatting, naming conventions, so that others can contribute more easily. For formatting, I recommend to use http://godoc.org/code.google.com/p/go.tools/cmd/goimports For naming conventions, I have no idea yet....

@marcoseravalli I'm not sure whether it is a good practice. However, I found it in the [Choose a good import path Secion](http://blog.golang.org/organizing-go-code). Maybe we should follow that. You can pull...

I also found a interesting organization on Github: https://github.com/gonum They implement some numeric libraries. I think we should consider whether to use [go.matrix](https://github.com/skelterjohn/go.matrix) in the future or not. ML heavily...

It seems both of `gonum/matrix/mat64` and `biogo.matrix` are created by same author, and it seems that the former are more active. So I prefer to use `gonum/matrix/mat64`. What do you...

Totally agree with you! I will fork and add some docs to functions that I know how they work, and send PR back to upstream.

Hi @hpxro7 It would be great if you could fork this repo and open a new branch for this feature. After finishing your work, you can then just send us...

I think basic linear models are required: logistic regression, linear regression. SVM integration would be great (w/ [libsvm](http://www.csie.ntu.edu.tw/~cjlin/libsvm/)). Cross validation is also essential. @Sentimentron I'm not sure in what case...

will then the base be too big and complicated? IMO, separating the CV-related into a individual sub-package can be just for cleanness.