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/
Yashwants19 has joined #mlpack
Yashwants19 has quit [Ping timeout: 256 seconds]
favre49 has joined #mlpack
< favre49> zoq: just wanted to give you a reminder to take a look at ny proposed NEAT interface whenever you're free
favre49 has quit [Client Quit]
sreenik has joined #mlpack
jeffin143 has joined #mlpack
vivekp has joined #mlpack
jeffin143 has quit [Remote host closed the connection]
pd09041999 has joined #mlpack
< zoq> favre49: Ahh, thanks, just responded.
pd09041999 has quit [Ping timeout: 248 seconds]
vivekp has quit [Read error: Connection reset by peer]
vivekp has joined #mlpack
pd09041999 has joined #mlpack
favre49 has joined #mlpack
< favre49> rcurtin: I've recently reinstalled ubuntu, and hence mlpack. There are a couple maybe pedantic issues i have
< favre49> with the website
< favre49> Maybe it's just me, but it's weird to me that the installation instructions are under a "tutorials" section
< favre49> It's not as intuitive as having a dedicated link to installation instructions from the main page
< favre49> Also, copy pasting the install command from the "Dependencies" section in http://mlpack.org/doc/stable/doxygen/build.html doesn't work since there are newlines at the end of the line
< favre49> (No clue if this can be fixed, just something that i found somewhat annoying)
< favre49> Also, there are multiple scroll bars on the screen. This may be something only I find weird though.
favre49 has quit [Quit: Page closed]
favre49 has joined #mlpack
< favre49> It occurred to me that the install command is more annoying to bash users, since it treats newlines as enter keypresses. Another reason to use zsh :)
favre49 has quit [Client Quit]
< zoq> favre49: gmanlan is working on an update (https://github.com/mlpack/mlpack/issues/1892) which I think will address some of the issues you mentioned
jeffin143 has joined #mlpack
< jeffin143> Zoq : I have used boost::string_view and for that included <boost/utility/string_view.hpp> , but Travis cl is failing throwing error that no file found
< jeffin143> Compiles fine In My local system*
< jeffin143> What should I do to debug it
< lozhnikov> jeffin143: string_view is a part of boost since 1.60. Travis uses boost 1.58
< jeffin143> Ohh ok*
< jeffin143> The I should just ignore it
< jeffin143> Then*
< lozhnikov> jeffin143: Actually string_view is a pretty small class. So, I think we could backport it to src/mlpack/core/boost_backport
< jeffin143> Ok I will look into it*
< jeffin143> And once done will ping you
< lozhnikov> jeffin143: But it's better to discuss with Ryan and Marcus before backporting.
< jeffin143> Ok*
< jeffin143> Sure
< zoq> If it's small, sure backporting is an option.
pd09041999 has quit [Ping timeout: 264 seconds]
vivekp has quit [Ping timeout: 255 seconds]
KimSangYeon-DGU_ has quit [Quit: Page closed]
zoq_ has joined #mlpack
< jeffin143> Lozhnikov : added some commits to pr1814, would like to have your comments on it, also I am unable to resolve Travis failure .
< jeffin143> Added string_view.hpp class to src/core/boost_backport , and also update cmake * , but it still throws an error.
< lozhnikov> jeffin143: Looks like string_view.hpp includes string_view_fwd.hpp. And you didn't backport this file. Actually, maybe string_view_fwd.hpp isn't needed at all. We need to check that.
< lozhnikov> jeffin143: I think this line is incorrect: "#if BOOST_VERSION <= 105800". string_view appeared in boost 1.61 (I've just checked).
< jeffin143> Ok*
< jeffin143> So I have to If boost_version <= 106100..?
< lozhnikov> jeffin143: I guess < 106100 or <= 106000
< jeffin143> Ok
zoq has quit [Quit: leaving]
zoq_ is now known as zoq
zoq has quit [Quit: leaving]
zoq has joined #mlpack
sreenik has quit [Quit: Page closed]
< rcurtin> lozhnikov: jeffin143: yeah, backporting string_view is probably the right call here.
< rcurtin> also, I hope that including string_view doesn't also include tons of other headers. if so, there are a few options, like how we split data/load.hpp and data/load_impl.hpp and used explicit template specialization
< jenkins-mlpack2> Project docker mlpack nightly build build #329: ABORTED in 2 days 8 hr: http://ci.mlpack.org/job/docker%20mlpack%20nightly%20build/329/