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/
witness has quit [Quit: Connection closed for inactivity]
govg has quit [Ping timeout: 256 seconds]
thepro has joined #mlpack
thepro has quit [Ping timeout: 240 seconds]
thepro has joined #mlpack
govg has joined #mlpack
thepro has quit [Ping timeout: 256 seconds]
thepro has joined #mlpack
thepro has quit [Ping timeout: 240 seconds]
vivekp has quit [Ping timeout: 264 seconds]
vivekp has joined #mlpack
ImQ009 has joined #mlpack
sulan_ has joined #mlpack
manthan has joined #mlpack
manthan has quit [Ping timeout: 260 seconds]
vivekp has quit [Ping timeout: 260 seconds]
vivekp has joined #mlpack
vivekp has quit [Ping timeout: 260 seconds]
vivekp has joined #mlpack
rajiv_ has joined #mlpack
rajiv_ has quit [Ping timeout: 260 seconds]
sumedhghaisas has joined #mlpack
sumedhghaisas2 has quit [Read error: Connection reset by peer]
sumedhghaisas2 has joined #mlpack
sumedhghaisas has quit [Ping timeout: 256 seconds]
sumedhghaisas has joined #mlpack
sumedhghaisas2 has quit [Ping timeout: 260 seconds]
manthan has joined #mlpack
< manthan>
zoq : you there?
< manthan>
i explicitly printed costPlus, costMinus, orgGradient and estGradient for the test and found that for both cases (full module and specific module), costPlus = costMinus, but still in full module test, estGradient comes to be equal to orgGradient but in specific test it comes to be 0.
< manthan>
might be due to any precision loss issues?
< zoq>
possible
< zoq>
Checked the backward and gradient step and I don't think there is an issue.
< manthan>
ya then why could the checkgradient be failing?
sumedhghaisas has quit [Read error: Connection reset by peer]
sumedhghaisas has joined #mlpack
sumedhghaisas has quit [Read error: Connection reset by peer]
sumedhghaisas has joined #mlpack
sumedhghaisas2 has joined #mlpack
sumedhghaisas has quit [Ping timeout: 245 seconds]
vivekp has quit [Ping timeout: 240 seconds]
vivekp has joined #mlpack
vivekp has quit [Ping timeout: 245 seconds]
vivekp has joined #mlpack
vivekp has quit [Ping timeout: 255 seconds]
sumedhghaisas2 has quit [Ping timeout: 240 seconds]
vivekp has joined #mlpack
sumedhghaisas has joined #mlpack
dmatt has joined #mlpack
robertohueso has joined #mlpack
dmatt has quit [Remote host closed the connection]
sumedhghaisas2 has joined #mlpack
sumedhghaisas has quit [Ping timeout: 240 seconds]
sumedhghaisas3 has joined #mlpack
sumedhghaisas has joined #mlpack
sumedhghaisas2 has quit [Ping timeout: 276 seconds]
sumedhghaisas3 has quit [Ping timeout: 265 seconds]
sulan_ has quit [Quit: Leaving]
Trion has joined #mlpack
vivekp has quit [Read error: Connection reset by peer]
daivik has joined #mlpack
vivekp has joined #mlpack
< daivik>
rcurtin: zoq: I opened PR #12 on the models repo which implements a CNN for the digit recognition Kaggle challenge. Unfortunately, there was already an open PR for implementing LeNet for the same - I apologize, I completely overlooked this. As of now, my model performs slightly better than the one on PR #9 (the LeNet PR) - giving a 94.485% accuracy
< daivik>
on the hidden test data on Kaggle in 40 epochs of training. Also, I think that PR#9 is going to use the original MNIST dataset now (instead of the Kaggle dataset)? I'm hesitant to close my PR right away because I think that I can push the performance a bit more with parameter tuning.. What do you suggest?
< rcurtin>
daivik: I agree, I'd prefer to take the model that does better. I hadn't looked into that #9 was going to use the MNIST dataset, I agree that we should stick wtih the Kaggle dataset
< rcurtin>
go ahead and leave it open, I'll try and comment in the next few days to figure out how to reconcile the two PRs, maybe we can take a little from each (but I haven't looked closely at yours, and it's been a few days since I looked at #9)
Trion has quit [Quit: Entering a wormhole]
< daivik>
okay, sorry again for not checking the open PRs beforehand
< rcurtin>
no problem at all, there are a lot of open PRs :)