cameron.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/
strykerami has joined #mlpack
witness___ has quit [Quit: Connection closed for inactivity]
strykerami has quit [Ping timeout: 272 seconds]
jenkins-mlpack has quit [Ping timeout: 260 seconds]
jenkins-mlpack has joined #mlpack
< jenkins-mlpack> Starting build #2127 for job mlpack - svn checkin test (previous build: SUCCESS)
govg has quit [Quit: leaving]
< jenkins-mlpack> Project mlpack - svn checkin test build #2127: SUCCESS in 1 hr 32 min: http://big.cc.gt.atl.ga.us:8080/job/mlpack%20-%20svn%20checkin%20test/2127/
< jenkins-mlpack> Ryan Curtin: Add a benchmark for mlpack to be run daily.
govg has joined #mlpack
govg has quit [Remote host closed the connection]
minh94_ has quit [Remote host closed the connection]
govg has joined #mlpack
skat00sh has joined #mlpack
< skat00sh> hi
< naywhayare> hello there
< skat00sh> Sorry for the late reply
< skat00sh> I'm quite new to the norms of contributing to open source and I found mlpack quite intersting
< jenkins-mlpack> Starting build #2128 for job mlpack - svn checkin test (previous build: SUCCESS)
< skat00sh> ok! could you be a little more elaborative
< jenkins-mlpack> Project mlpack - svn checkin test build #2128: FAILURE in 3 min 22 sec: http://big.cc.gt.atl.ga.us:8080/job/mlpack%20-%20svn%20checkin%20test/2128/
< jenkins-mlpack> * Ryan Curtin: Remove comment about overclustering.
< jenkins-mlpack> * Ryan Curtin: Implement Elkan's algorithm for k-means (it's pretty fast).
< jenkins-mlpack> * Ryan Curtin: Refactor k-means significantly. Remove overclustering since I think nobody is
< jenkins-mlpack> using it (I don't think it's a very interesting technique) and it may be buggy.
< jenkins-mlpack> Speedups for the situation where only cluster centroids are desired.
skat00sh has quit [Ping timeout: 246 seconds]
sumedh has joined #mlpack
< sumedh> naywhayare: Hey Ryan, I was just going through CMakeLists file of MLPACK, the tutorial MLPACK Build says that MLPACK will be build with debugging symbols and profiling information if no option is provided to CMAKE...
< sumedh> but in CMakeLists DEBUG and PROFILE is set to OFF initially...
< sumedh> Is this correct??
< naywhayare> sumedh: hm, DEBUG and PROFILE are set to OFF for releases, but not for trunk
< sumedh> naywhayare: but I am compiling 1.0.10 release...
< naywhayare> yeah, so if you are compiling 1.0.10, then DEBUG and PROFILE are set to off by default
< naywhayare> I think the documentation is wrong, so let me clarify it
< naywhayare> I checked in some changes that should make things more clear, but I haven't rebuilt the documentation for the website yet
< jenkins-mlpack> Starting build #2129 for job mlpack - svn checkin test (previous build: FAILURE -- last SUCCESS #2127 13 hr ago)
< jenkins-mlpack> Project mlpack - svn checkin test build #2129: STILL FAILING in 10 min: http://big.cc.gt.atl.ga.us:8080/job/mlpack%20-%20svn%20checkin%20test/2129/
< jenkins-mlpack> * Ryan Curtin: Refactor for different KMeans API.
< jenkins-mlpack> * Ryan Curtin: Update and clarify build tutorial, since DEBUG and PROFILE are OFF by default in
< jenkins-mlpack> releases.
< jenkins-mlpack> * Ryan Curtin: Refactor test to remove overclustering parameter.
< jenkins-mlpack> * Ryan Curtin: Remove references to overclustering from tutorial.
sumedh has quit [Ping timeout: 272 seconds]
< naywhayare> sigh, I am not good at not breaking the build, I guess
< jenkins-mlpack> Starting build #2130 for job mlpack - svn checkin test (previous build: STILL FAILING -- last SUCCESS #2127 14 hr ago)
< jenkins-mlpack> Yippee, build fixed!
< jenkins-mlpack> Project mlpack - svn checkin test build #2130: FIXED in 1 hr 31 min: http://big.cc.gt.atl.ga.us:8080/job/mlpack%20-%20svn%20checkin%20test/2130/
< jenkins-mlpack> Ryan Curtin: Refactor for API change... forgot to check this one in.