Oops, sorry, I misspoke---I thought this was a bug in mlpack 2.1.0 but this code is only in master, not in 2.1.0, so there is no need for a sudden release.
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/mlpack/mlpack/pull/816#issuecomment-262600310
_______________________________________________ mlpack mailing list [email protected] http://knife.lugatgt.org/cgi-bin/mailman/listinfo/mlpack
