ChanServ changed the topic of #mlpack to: "mlpack: a fast, flexible machine learning library :: We don't always respond instantly, but we will respond; please be patient :: Logs at http://www.mlpack.org/irc/
< abernauer[m]>
Well finished my draft for now 😁
< rcurtin>
awesome :)
< abernauer[m]>
The web design changes to the mlpack site are nice forgot to mention that.
< rcurtin>
abernauer[m]: thanks, @gmanlan did all the hard work :)
< zoq>
rcurtin: The comment - "I literally had to argue the security guard to let me in *to present my poster*, he kept trying to send me to the back of the queue and saying a line is a line.
xiaohong has quit [Remote host closed the connection]
osworker has joined #mlpack
osworker has quit [Read error: Connection reset by peer]
osworker has joined #mlpack
osworker has quit [Quit: Leaving.]
ImQ009 has joined #mlpack
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 268 seconds]
osworker has joined #mlpack
< abernauer[m]>
@rcurtin Would you ever consider going on an AI/machine learning podcast? Might be a decent way to market mlpack.
< abernauer[m]>
That poster situation sounds like a logistical nightmare too.
< rcurtin>
abernauer[m]; if someone approached me, I'd probably do it, but I don't think I have the time to seek that out myself
< abernauer[m]>
Yeah that's reasonable can only take on, so many things at a time. Lex Fridman has a pretty good A.I. podcast guests like Elon Musk, Gilbert Strang, Juda Pearl, Ian Goodfellow, etc.
< zoq>
abernauer[m]: Agreed, great podcast :)
osworker has quit [Read error: Connection reset by peer]
osworker has joined #mlpack
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 276 seconds]
< rcurtin>
abernauer[m]: if Lex Fridman ever called me up I would of course agree :)
osworker has quit [Ping timeout: 245 seconds]
osworker has joined #mlpack
osworker has left #mlpack []
metahost_ has joined #mlpack
metahost has quit [Quit: ~~ gtg ~~]
metahost_ is now known as metahost
ImQ009 has quit [Quit: Leaving]
< Nakul[m]>
Hi
< Nakul[m]>
I have added test for softmax_regression callback , and need to test what is the best way to run "FAST" all the tests ... I read more about testing from here https://github.com/mlpack/mlpack/wiki/Testing-Guidelines
< zoq>
Nakul[m]: You don't have to run all tests, which could take some time, instead you can run a single test suite; if you make a test suite called "TestSuite" (BOOST_AUTO_TEST_SUITE(TestSuite)), and then build 'mlpack_test' ('make mlpack_test'), you can run only the tests in that test suite with 'bin/mlpack_test -t TestSuite'. A specific test case called 'TestCase' (BOOST_AUTO_TEST_CASE(TestCase)) could be run
< zoq>
with 'bin/mlpack_test -t TestSuite/TestCase'.
< Nakul[m]>
@zo
< Nakul[m]>
zoq: thanks
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 265 seconds]
xiaohong has joined #mlpack
< rcurtin>
zoq: I think I'll release a version of ensmallen once we merge #145; anything else you think we should wait on?
< rcurtin>
I can make time to review #138 (the lookahead optimizer) too, and it seems like #137 is just about ready, but no rush
< rcurtin>
perfectly okay to release one version, then merge #138 or #137 and release again
< zoq>
yeah, let's make another release with the new optimization methods
xiaohong has quit [Ping timeout: 250 seconds]
< zoq>
so nothing else from my side, merging #145 and do a new relase sounds good
< zoq>
I had a minor comment about CMAES in #145, but we can move that into the next release.
< rcurtin>
sure, either way works
< rcurtin>
I can make the change for CMAES or focus on #138, just let me know which you'd rather have me do