verne.freenode.net changed the topic of #mlpack to: http://www.mlpack.org/ -- We don't respond instantly... but we will respond. Give it a few minutes. Or hours. -- Channel logs: http://www.mlpack.org/irc/
decltypeme has joined #mlpack
edlinde has joined #mlpack
edlinde has quit [Quit: edlinde]
edlinde has joined #mlpack
< naywhayare> so, I've realized that the homepage (http://www.mlpack.org/) is not very good and doesn't really provide a way for people to figure out what the library does, how to use it, where to get it, etc.
< naywhayare> I've prototyped a new homepage: http://www.mlpack.org/index-new.html , and I'd be happy to hear feedback
< naywhayare> none of the links on it work yet, this is just a basic design idea
edlinde has quit [Quit: edlinde]
edlinde has joined #mlpack
edlinde has quit [Quit: edlinde]
govg has quit [Quit: leaving]
SinisterMJ has quit [Quit: Page closed]
govg has joined #mlpack
< zoq> naywhayare: Looks really nice, perhaps I would change 'get mlpack' with 'get started'. Not sure because I like the reference to mlpack.
govg has quit [Ping timeout: 264 seconds]
govg has joined #mlpack
curiousguy13 has joined #mlpack
sumedhghaisas has joined #mlpack
govg has quit [Quit: leaving]
govg has joined #mlpack
govg has quit [Ping timeout: 265 seconds]
< naywhayare> zoq: if I change it to "get started", do you think I should move the links to "about mlpack" and "how to get help" into that section too? (it seems to me like those are things people might want to know when getting started)
< zoq> naywhayare: I guess it would make sense to move the links into the get started section.
< naywhayare> hm, but if I do that, then I don't think I have anything left for the "learn about mlpack" category
< naywhayare> I suppose I could just change it to "get started", leave the links as-is, and also have a potentially non-orthogonal "learn about mlpack" category
< naywhayare> maybe I am putting too much thought into this :)
< zoq> Maybe the sections are fine the way they are :)
< naywhayare> ok, I'll leave them as-is for now then
< naywhayare> I'll start fleshing out the rest of the new site, and then when it's all ready to go I'll let the channel know again for any other comments, then deploy it to mlpack.org
< zoq> sounds great
< naywhayare> here's an interesting post to twitter I found: https://twitter.com/michiexile/status/577739688485740545
< naywhayare> the guy is having difficulty understanding how to sample from GMMs... so someone, in the reply, instead of suggesting a statistics textbook, suggests he look at the mlpack source code :)
< naywhayare> I'm glad to know all this documentation hasn't been for nothing :)
< zoq> textbook .... just read mlpack source code :)
< naywhayare> maybe I'll find a publisher and see if they'll print some version of mlpack into a book
KTL has joined #mlpack
< KTL> not sure but GaussianDistribution::FactorCovariance uses arma::log_det ... and that logarithm appears to be base 10 ? shouldn't that be base e ? but ... it's probably just me being chaotic
curiousguy13 has quit [Ping timeout: 252 seconds]
govg has joined #mlpack
< zoq> naywhayare: On OSX we need to link against libc++ instead of stdc++ at least on some 'older' versions. That should solve the homebrew build error on mountain lion as pointed out in the svd issue.
< zoq> naywhayare: https://gist.github.com/zoq/5f228a6ec890 Maybe there is a better solution?
curiousguy13 has joined #mlpack
< naywhayare> zoq: the gist link 404'ed; I don't see any other gists under your username that seem to be for the clang linker issue
< zoq> maybe now?
< naywhayare> KTL: yeah, arma::log_det uses std::log internally (see armadillo_bits/fn_log_det.hpp if you're interested)
< naywhayare> that looks good to me, but do you know any more about which versions of OS X require -stdlib=libc++?
< naywhayare> it looks like line 9 is missing '-lm'
< naywhayare> hang on, stupid thing for me to say... that's CXXFLAGS not linker flags
< zoq> I could reproduce the build issue on OS X Lion so OS X Lion and mountain Lion. OS X mavariks comes with an updated version of libstdc++ which covers boost fusion. Regarding http://stackoverflow.com/questions/14972425/should-i-use-libc-or-libstdc and the llvm page (http://libcxx.llvm.org/) we should generally link against libc++ on OSX.
< zoq> And of course homebrew generally builds against libc++
< naywhayare> ah, thanks for the link
< naywhayare> I don't know very much about development on OS X, so this clarifies a lot
< zoq> I guess we could say update the OS or link against libc++
< naywhayare> if you push the CMake configuration patch, then he can just use that as a patch to 1.0.12
< naywhayare> (...assuming he starts actually patching the releases right...)
< zoq> so just as create a patch or update the CMake configuration in the master branch?
< naywhayare> I'd just update it in master
< naywhayare> if he says he doesn't know how to make a patch out of that, I'll do it for him because it should be quite easy
< zoq> yeah probably the best solution
edlinde has joined #mlpack
< KTL> this might be interesting to get rid of the singular covariance-matrices: http://www.doc.ic.ac.uk/~dfg/ProbabilisticInference/IDAPILecture17.pdf (the current algorithm in gaussian distribution is adding a growing perturbation to the diagonal till the determinant > 0)
< KTL> (look for "Regularisation (or shrinkage) methods")
< naywhayare> it seems like equation (9) is basically what we are doing now, and iteratively growing alpha until the matrix is nonsingular
< naywhayare> I'm still reading, but I've always thought there must be a better way
< naywhayare> if you have an idea to apply, please feel free to take a shot and submit it as a PR; I'd be more than happy to accept a better strategy
< KTL> (btw, equation 9 also lowers the entire existing covariance matrix)
< naywhayare> yeah, what we are doing isn't exactly the same, just sort of similar :)
< KTL> :D
< naywhayare> I always thought about the problem from the perspective of "can we project the matrix onto the cone of positive definite matrices in some way that minimizes || A - A' ||_F" or something like that
< naywhayare> but I didn't put too much time into it, and I couldn't quickly find any algorithms that didn't have huge amounts of overhead, which is why I eventually went with the "just add crap to the diagonal until it works" approach
< KTL> after looking through a bunch of papers i figured there is lots of academic crap around :D
< naywhayare> yeah, I figured there must be something, but I didn't have the time to devote to it
< KTL> time is limited :(
KTL has quit [Ping timeout: 248 seconds]
edlinde has quit [Quit: edlinde]
decltypeme has quit [Ping timeout: 264 seconds]
sumedhghaisas has quit [Quit: AndroIRC - Android IRC Client ( http://www.androirc.com )]