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/
govg has quit [Ping timeout: 276 seconds]
vivekp has quit [Ping timeout: 255 seconds]
vivekp has joined #mlpack
raphael29_ has joined #mlpack
govg has joined #mlpack
govg has quit [Ping timeout: 248 seconds]
govg has joined #mlpack
govg has quit [Ping timeout: 240 seconds]
govg has joined #mlpack
aditya_ has joined #mlpack
aditya has joined #mlpack
govg has quit [Ping timeout: 245 seconds]
govg has joined #mlpack
govg has quit [Remote host closed the connection]
govg has joined #mlpack
ferbncode_ has joined #mlpack
govg has quit [Ping timeout: 260 seconds]
aditya_ has quit [Ping timeout: 240 seconds]
aditya has quit [Ping timeout: 255 seconds]
govg has joined #mlpack
cult- has joined #mlpack
< cult-> hi. I have an issue with hmm and the training data. some of my 'normal' training data are fails and throws error: chol(): decomposition failed
< cult-> sometimes, the beginning of the data works well, and the later part throws this exception. i am not sure what should I do with my data. also, the longer the data, eg. tens of thousands of observations, the probability of getting this error increases.
< cult-> how should I overcome of this annoying issue?
< cult-> i observed that if my data has more extreme residuals, this is more likely to happen too, the cholesky decomposition.
aditya_ has joined #mlpack
aditya__ has joined #mlpack
aditya__ has quit [Ping timeout: 240 seconds]
aditya_ has quit [Ping timeout: 255 seconds]
< rcurtin> cult-: what's the observation type, is it gaussian or GMMs?
< rcurtin> with Gaussians the cholesky decomposition can fail when the covariance matrix gets very small, it becomes non-invertible
< rcurtin> so one thing you can do is add noise to your observations, or possibly reducing the number of states can help too
< cult-> gaussian
< rcurtin> yeah, so try adding some noise to the observations and see if that helps
< rcurtin> I thought I had written code to help prevent this situation some time back though... are you using a new(ish) version of mlpack? 2.1.0 and newer should incorporate those fixes
< cult-> i tried both 2.0.x and 2.1.x
< cult-> 2.1.1 but not the master branch
< rcurtin> you can try the master branch, but I doubt it's different---I think HISTORY.md has documentation of when the HMM fixes occured; I think it was either 2.0.1 or 2.1.0
< cult-> i will first try some cleaning on my data, because it has some bad periods
< cult-> i think it will help but let's see
< rcurtin> yeah, often this might happen if, e.g., one state has observations that are all identical
< rcurtin> then the covariance matrix becomes noninvertible for that state
< rcurtin> anyway I have to go for now, I'll be back later---good luck :)
< cult-> thats the case, but i haven't yet cleaned it, thanks again!
ferbncode_ has quit [Quit: Connection closed for inactivity]
raphael29_ has quit [Quit: Konversation terminated!]