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/
caiojcarvalho has joined #mlpack
caiojcarvalho has quit [Ping timeout: 240 seconds]
caiojcarvalho has joined #mlpack
caiojcarvalho has quit [Ping timeout: 250 seconds]
amanpro30 has joined #mlpack
amanpro30 has quit [Client Quit]
vivekp has quit [Read error: Connection reset by peer]
vivekp has joined #mlpack
< jenkins-mlpack2> Project docker mlpack nightly build build #187: STILL UNSTABLE in 3 hr 20 min: http://ci.mlpack.org/job/docker%20mlpack%20nightly%20build/187/
witness has quit [Quit: Connection closed for inactivity]
petris has quit [Quit: Bye bye.]
petris has joined #mlpack
Mukesh has joined #mlpack
< Mukesh> JOIN
Mukesh has quit [Client Quit]
vivekp has quit [Read error: Connection reset by peer]
vivekp has joined #mlpack
vivekp has quit [Ping timeout: 246 seconds]
vivekp has joined #mlpack
niteya has joined #mlpack
Xuwei has joined #mlpack
< niteya> hello , I am trying to debug my PR , Travis CI is reporting an error that home/jenkins/workspace/pull-requests mlpack memory/src/mlpack/methods/range_search/rs_model_impl.hpp:66:31: error: ‘approx_equal’ is not a member of ‘arma’ , even though it compiles on my computer and i am pretty sure that approx_equal is indeed a function of armadillo .
< niteya> where is the error coming from ?
< niteya> PR #1632
niteya has quit [Quit: Page closed]
< zoq> niteya: ‘approx_equal’ was introduced in armadillo 6.700, but we support/build against armadillo 6.500 (6.500 as a minimum). See https://github.com/mlpack/mlpack/pull/1369#discussion_r183142822 for a possible solution.
< Xuwei> Hello, I just want to check that is anyone working on the choco inistaller for windows issue#1589?
ImQ009 has joined #mlpack
< rcurtin> Xuwei: sure, nobody is working on that, you should feel free
< Xuwei> Great, Do you know what's the minimum supported cmake version for mlpack? I can't find it.
niteya has joined #mlpack
< rcurtin> Xuwei: isn't it at the top of the main CMakeLists.txt?
< Xuwei> Oh I see, sorry somehow missed that
< rcurtin> :)
< niteya> zoq: Thanks a lot for the help
< Xuwei> I know it's open source, but I just want to make sure do I have the legal right to distribute package like boost, cmake, armadillo, mlpack?
< rcurtin> so long as you follow the license guidelines of those packages, yeah, shouldn't be a problem. but I think that 'following the license guidelines' means just distributing the licenses of those packages
< rcurtin> and not claiming that you wrote them ;)
< Xuwei> Ok cool, thanks for the help
< rcurtin> or at least boost/cmake/armadillo. for mlpack you can claim that since you are contributing :)
Xuwei has quit [Ping timeout: 256 seconds]
manish7294 has joined #mlpack
< manish7294> rcurtin:zoq: Everytime I am trying to cmake mlpack, it is throwing missing ensmallen error and is downloading it ensmallen again & again. I suppose this shouldn't be happening right? Here's the log of two consecutive cmake calls https://pastebin.com/JCr7L11v
< rcurtin> ooh, that is a bug. there's a call 'find_package(Ensmallen 1.10.0)' but that doesn't find it if we already downloaded it
< rcurtin> what happens if you configure with ENSMALLEN_INCLUDE_DIR=deps/ensmallen-1.12.2/include/?
< rcurtin> i.e. cmake -DENSMALLEN_INCLUDE_DIR="$PWD/deps/ensmallen-1.12.2/include/" ../ in an already-configured build directory?
manish7294_ has joined #mlpack
manish7294 has quit [Ping timeout: 256 seconds]
niteya has quit [Ping timeout: 250 seconds]
< manish7294_> rcurtin: that works without re-download
< rcurtin> hm, ok, so we can make a patch then, that sets ENSMALLEN_INCLUDE_DIR (if it isn't already set) before the find_package() call
< manish7294_> this time we have : Found ensmallen: /home/manish/mlpack/build/deps/ensmallen-1.12.2/include (found version "0.0.0")
< rcurtin> perfect, though the version seems off
< manish7294_> hmm
< rcurtin> want me to open an issue for this?
< rcurtin> or if you want you can try and patch it, it shouldn't be too hard I think
< manish7294_> sure, let me see
< rcurtin> I guess we just have to see if there is a deps/ensmallen-x.y.z/ directory and use that as ENSMALLEN_INCLUDE_DIR if ENSMALLEN_INCLUDE_DIR isn't specified
manish7294_ has quit [Ping timeout: 256 seconds]
< rcurtin> I'm trying to do my best to go through old issues that have fallen off my radar and help describe them well enough that others can handle the task
< rcurtin> hopefully it is helpful, especially for all the incoming prospective GSoC students
travis-ci has joined #mlpack
< travis-ci> manish7294/mlpack#95 (cmakeEnsmallen - f3c506e : Manish): The build has errored.
< travis-ci> Change view : https://github.com/manish7294/mlpack/compare/3b95e90555f4^...f3c506e212f1
travis-ci has left #mlpack []
travis-ci has joined #mlpack
< travis-ci> manish7294/mlpack#30 (cmakeEnsmallen - f3c506e : Manish): The build has errored.
< travis-ci> Change view : https://github.com/manish7294/mlpack/compare/3b95e90555f4^...f3c506e212f1
travis-ci has left #mlpack []
ImQ009 has quit [Quit: Leaving]
< jenkins-mlpack2> Project mlpack - git commit test build #81: FAILURE in 1 min 35 sec: http://ci.mlpack.org/job/mlpack%20-%20git%20commit%20test/81/
< jenkins-mlpack2> noreply: Merge pull request #1659 from manish7294/cmakeEnsmallen
< jenkins-mlpack2> Yippee, build fixed!
< jenkins-mlpack2> Project mlpack - git commit test build #82: FIXED in 34 min: http://ci.mlpack.org/job/mlpack%20-%20git%20commit%20test/82/
< jenkins-mlpack2> Ryan Curtin: Fix typos in ensmallen configuration.