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/
lozhnikov has quit [Ping timeout: 244 seconds]
lozhnikov has joined #mlpack
Cooler_ has joined #mlpack
Cooler_ has quit [Remote host closed the connection]
topology has joined #mlpack
mentekid has joined #mlpack
mentekid has quit [Ping timeout: 272 seconds]
topology has quit [Ping timeout: 240 seconds]
theJonan has joined #mlpack
< theJonan> Hi. I'm afraid you've got this question many, many times... however, managing to build mlpack on MacOS _with_ OpenMP turns to be quite a hurdle. I've installed the llvm package (version 3.8.1, with included OpenMP-enabled clang), configured CMake to use it, but it stumbled on NewCXX11.cmake directives... I've commented this file inclusion, but during the build process, the double template parenthesis produced an error. Any suggestio
< rcurtin> theJonan: interesting, I am not sure I have ever tried that
< rcurtin> can you tell me more about what the actual error is?
< rcurtin> if you like you can open a github issue and we can figure it out there, or we can try here, whatever works for you :)
< theJonan> Probably openning a github issue will be more scalable approach :-)
< theJonan> I'll open two issues - one regarding the NewCXX.cmake errors, and the other - template closing double parenthesis - `>>` compilation error.
< rcurtin> the template closing issue shouldn't be a problem if CMake is properly setting the -std=c++11 flag, but it sounds like in your case maybe it is not doing that for some reason
< rcurtin> I'll take a look today when I have a chance and get back to you... I think we can get this one sorted out quickly :)
< theJonan> Ok, thank you. Actually, my main idea was to make some fixes to DET, so it can deal with ordinal (and/or constant) values of features better. If/when I succeed in this I'll post a pull request :-)
< rcurtin> ok, great, thanks :)
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#1567 (master - a2d45eb : Ryan Curtin): The build has errored.
travis-ci has left #mlpack []
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#1568 (master - dee2c82 : Ryan Curtin): The build has errored.
travis-ci has left #mlpack []
lozhnikov has joined #mlpack
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#1571 (master - c72f9c3 : Ryan Curtin): The build has errored.
travis-ci has left #mlpack []
< rcurtin> and here we have a great example of why I should be using PRs so travis checks everything before I merge it
< rcurtin> so I think I will need to do that in the future
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#1569 (master - 81be55c : Ryan Curtin): The build passed.
travis-ci has left #mlpack []
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#1570 (master - 316d4b0 : Ryan Curtin): The build passed.
travis-ci has left #mlpack []
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#1572 (master - ee0da57 : Ryan Curtin): The build passed.
travis-ci has left #mlpack []
< theJonan> I keep adding issues... this time it is for PARAM_VECTOR_IN misbehavior.
< rcurtin> ok, no problem, thanks
< rcurtin> I believe the two issues you filed earlier are linked, so I fixed the first and I think that that should fix the second
< rcurtin> let me know if that's not the case
< rcurtin> and we can reopen the issues :)
aspera has joined #mlpack
aspera has quit [Ping timeout: 240 seconds]
travis-ci has joined #mlpack
< travis-ci> akanuraj200/mlpack#9 (master - 5c6a096 : KANODIA): The build is still failing.
travis-ci has left #mlpack []
travis-ci has joined #mlpack
< travis-ci> akanuraj200/mlpack#8 (master - e553685 : Anuraj Kanodia): The build passed.
travis-ci has left #mlpack []
topology has joined #mlpack
< theJonan> Yes, they are. And I'm currently trying you fixes - everything seems OK. Thanks!
< rcurtin> great, glad to hear it worked
< rcurtin> I thought the vector parameters worked at least on linux... I'll look into it but I don't think that will be today unfortunately
< zoq> hm, the commit job is running for over a day now
< rcurtin> let's see...
< rcurtin> I think I will restart it. it's possible there is some low-probability error that results in an infinite loop
< jenkins-mlpack> Project mlpack - git commit test build #2534: ABORTED in 1 day 2 hr: http://masterblaster.mlpack.org/job/mlpack%20-%20git%20commit%20test/2534/
< jenkins-mlpack> * ryan: First commit, no code yet; just moving systems.
< jenkins-mlpack> * ryan: Minor updates.
< jenkins-mlpack> * ryan: Intermediate checkin so I can move systems easily.
< jenkins-mlpack> * ryan: Update some minor documentation and const correctness.
< jenkins-mlpack> * ryan: Fix typo.
< jenkins-mlpack> * ryan: Add some simple octree tests.
< jenkins-mlpack> * ryan: Add traits and main include file.
< jenkins-mlpack> * ryan: Add copy, move, and serialization, plus tests for the octree.
< jenkins-mlpack> * ryan: Add traversers for octree.
< jenkins-mlpack> * ryan: Add tested support to KNN/KFN for octree.
< jenkins-mlpack> * ryan: Add octree to RangeSearch and RASearch.
< jenkins-mlpack> * ryan: Refactor for changes in #788.
< jenkins-mlpack> * ryan: Fix spacing.
< jenkins-mlpack> * ryan: Move PerformSplit and fix edge case bugs.
< jenkins-mlpack> * ryan: Refactor tree-building to use PerformSplit.
< jenkins-mlpack> * ryan: Remove stray comment.
< zoq> here we go :)
< jenkins-mlpack> * ryan: Convert std::pow usage to shifts.
< rcurtin> let's see if the next one does better
< rcurtin> if it does it again, I'll start looking at the xml output of the tests to see what test it is hanging on
< rcurtin> I see that the matrix build has a couple builds that are hanging
< rcurtin> my guess is maybe there is some memory error in the octree
< rcurtin> so I will start investigating...
topology has quit [Quit: Page closed]
< zoq> So I guess, that's a nice situation where the build farm brings up some errors that are obviously not that easy to find.
< rcurtin> yeah, I really like the matrix build for that... it is good for identifying low-probability test failures