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/
vivekp has joined #mlpack
witness_ has quit [Quit: Connection closed for inactivity]
vivekp has quit [Ping timeout: 256 seconds]
vivekp has joined #mlpack
vivekp has quit [Read error: Connection reset by peer]
vivekp has joined #mlpack
yaswagner has quit [Ping timeout: 260 seconds]
vivekp has quit [Read error: Connection reset by peer]
vivekp has joined #mlpack
vivekp has quit [Ping timeout: 240 seconds]
vivekp has joined #mlpack
< ShikharJ> zoq: I pushed in the missing file, sorry foe the delay.
vivekp has quit [Ping timeout: 264 seconds]
vivekp has joined #mlpack
< jenkins-mlpack> Yippee, build fixed!
< jenkins-mlpack> Project docker mlpack nightly build build #363: FIXED in 4 hr 11 min: http://masterblaster.mlpack.org/job/docker%20mlpack%20nightly%20build/363/
< sumedhghaisas> Atharva: Hi Atharva
< sumedhghaisas> sorry was little busy yesterday
< sumedhghaisas> I will take a look at the jocobian test today
< Atharva> sumedhghaisas: No problem. After the jacobian is taken care of, I will update the reconstruction PR. We need to merge both of them to start with the models. I have prepared the README.md
< Atharva> Or maybe, after we merge the normal dist PR, I will rebase the reconstruction PR and then we can get it merged
< sumedhghaisas> Atharva: It might take a while to merge them, I recommend working by rebasing on them
< Atharva> Okay, sure
< sumedhghaisas> in case they change, we can always rebase again
< sumedhghaisas> Regarding models, you will need to link models with the local copy of your code
< Atharva> Okay, so I will be able to start working on it before the PRs are merged
< sumedhghaisas> yes
< Atharva> As soon as we get the jacobian sorted, I will start working on the models with a local copy with all the changes
< sumedhghaisas> Atharva: Haven't taken a look yet though what is the issue you are facing? the approximate and real gradient for LogProb don't match right?
< Atharva> Yes
< Atharva> They dont
ImQ009 has joined #mlpack
yaswagner has joined #mlpack
manish7294 has joined #mlpack
< manish7294> rcurtin: Please try to review the eval bounds as you get the chance https://github.com/mlpack/mlpack/issues/1449#issuecomment-401056900
< rcurtin> right, I saw them, I have it lined up for today
< rcurtin> intuitively, glancing at them they seem correct, I'll take a closer look though and verify
< rcurtin> you can always go ahead and implement as-is, and then see if it still gives the same results :)
< manish7294> Ya sure :)
< rcurtin> even if the bound is a little wrong, the code you implement could probably be easily adapted to a different version of the bound, so no need to wait until we have verified bounds to implement
< manish7294> you may not find the handwriting pleasant though :)
< rcurtin> that's ok, mine is not so great either :)
< rcurtin> I have to step out for lunch, back in a little while
vivekp has quit [Read error: Connection reset by peer]
vivekp has joined #mlpack
manish7294 has quit [Quit: Page closed]
pd09041999 has joined #mlpack
pd09041999 has quit [Ping timeout: 268 seconds]
pd09041999 has joined #mlpack
pd09041999 has quit [Ping timeout: 260 seconds]
witness_ has joined #mlpack
< ShikharJ> zoq: Looks like the issue with enable_if is resolved. As of yet, we'll need to have three Evaluate and Gradient functions (one for both GAN and DCGAN, and one each for standard WGAN and Gradient-Penalized WGAN). Out of these functions, three are ready, and three more would be ready by Sunday. Then we can review and merge the PR.
< ShikharJ> zoq: Ah, I noticed that Gradient-Penalised WGAN also has a similar Gradient routine as Standard GAN and DCGAN. So now only the Evaluate functions for the WGANs are remaining to be implemented.
< zoq> ShikharJ: I think this are good news :)
ImQ009 has quit [Quit: Leaving]
witness_ has quit [Quit: Connection closed for inactivity]