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/
gtank___ has quit [Ping timeout: 260 seconds]
gtank___ has joined #mlpack
gtank___ has quit [Ping timeout: 245 seconds]
kyrre has quit [Ping timeout: 252 seconds]
vansika__ has quit [Ping timeout: 260 seconds]
vansika__ has joined #mlpack
vansika__ has quit [Ping timeout: 260 seconds]
kyrre has joined #mlpack
kyrre has quit [Ping timeout: 272 seconds]
kyrre has joined #mlpack
kyrre has quit [Ping timeout: 272 seconds]
hlopuwki[m] has joined #mlpack
gtank___ has joined #mlpack
vansika__ has joined #mlpack
kyrre has joined #mlpack
SachaD has joined #mlpack
< jenkins-mlpack2> Project docker mlpack nightly build build #584: STILL UNSTABLE in 3 hr 2 min: http://ci.mlpack.org/job/docker%20mlpack%20nightly%20build/584/
hlopuwki[m] has left #mlpack []
kumaran[m] has joined #mlpack
roopsai has joined #mlpack
< roopsai> hi
roopsai has quit [Remote host closed the connection]
< SachaD> Another question: What wrong with this csv file https://yadi.sk/d/RxhD2xALODmy2w (26.6 mb). When I opened it in LibreOffice it has 31 columns, but when I open it in mlpack I see n_cols == 61 in debugger and values are wrong.
SachaD has quit [Quit: Konversation terminated!]
< zoq> SachaD: Check line 79552, not sure what LibreOffice does here
soham has joined #mlpack
soham has quit [Remote host closed the connection]
ImQ009 has joined #mlpack
< HimanshuPathakGi> Hey zoq can you please have a look at https://github.com/mlpack/mlpack/pull/2099
< zoq> HimanshuPathak: Sure, it's on my list of things to review, perhaps I can take a look later today.
< HimanshuPathakGi> Ok I can wait.
< rcurtin> HimanshuPathak: there are too many PRs and too few reviewers :( if you want to help out, you should feel free to review other PRs too and help other contributors. that can be really helpful :)
< HimanshuPathakGi> Sure I will try to review other PRs
< rcurtin> awesome, thanks. a lot of the times there are PRs where there is some build failure that needs to be debugged and the contributor is having trouble with it
< jeffin143[m]> Today Mozilla made its biggest layoff employees ,-> fighting financial crises.
< jeffin143[m]> Maintain an open source project is difficult :'(
< HimanshuPathakGi> Sure I will try to help other contributors thanks for suggestion rcurtin
< rcurtin> jeffin143[m]: yeah, it is not easy :(
< rcurtin> especially trying to make a business out of open source software is hard
ImQ009 has quit [Read error: Connection reset by peer]
< rcurtin> my company works with Julia Computing, which is a company that helps maintain Julia and makes money consulting, and it's a hard business
ImQ009 has joined #mlpack
Anind95 has joined #mlpack
Anind95 has quit [Ping timeout: 260 seconds]
< HimanshuPathakGi> Hey rcurtin I was trying to look at the build of https://github.com/mlpack/mlpack/pull/2127 but there was an error BUILD not found is it usual same with https://github.com/mlpack/mlpack/pull/2122
SachaD has joined #mlpack
< rcurtin> maybe because the build is sufficiently old that it got deleted?
< rcurtin> maybe there is something in our azure configuration that could be modified to preserve builds for longer? I'm not sure, I don't know very much about that
< HimanshuPathakGi> Ok I will try any other PR
ImQ009 has quit [Quit: Leaving]
< rcurtin> you can also look into how azure could be reconfigured; I don't know anything about it
< rcurtin> it would certainly be useful if it kept builds around for longer
< HimanshuPathakGi> Sure I will try to look for this
ibtihaj has joined #mlpack
ibtihaj has quit [Remote host closed the connection]
< HimanshuPathakGi> Hey rcurtin we can keep builds for longer time by changing the retention policies of run in setting tab of the project https://docs.microsoft.com/en-us/azure/devops/pipelines/policies/retention?view=azure-devops#release-retention
< zoq> HimanshuPathak: Thanks, let me set everything to the maximum.
< HimanshuPathakGi> Saving builds for longer time will help us you're welcome zoq
< kumaran[m]> Hey. I've build mlpack from GitHub source, (by building armadillo from source) and I'm looking at issues related to porting project to modern cmake.
< kumaran[m]> I have some experience with cmake and I've previously used googletest and boost with cmake.
< kumaran[m]> What can I do to get started?
SachaD has quit [Quit: Konversation terminated!]
< zoq> kumaran[m]: Hello, there is a PR open for ensmallen which you could review.
< Nakul[m]> Hey zoq whne some test fails how to see where might be fault because running ctest -T simply says either passed or fails. I have buided with debug mode on
< Nakul[m]> *when
< zoq> Nakul[m]: If you can't reproduce the issue on you system, tracking down an error is difficult, I'll see if I can reproduce the error on my system tomorrow.
< Nakul[m]> Ok
< zoq> Nakul[m]: Maybe you have another system at hand to test this as well.
< zoq> Nakul[m]: Btw. looks like it failed to build on windows, if you don't have a windows system, you can take a look at the log and maybe figure out what the issue is.
< zoq> Nakul[m]: Another idea to reproduce the issue, is to build against the same armadillo version as used on the build jobs.
< rcurtin> Nakul[m]: you also don't have to run the tests with ctest. You could call `bin/mlpack_test -t NameOfTestSuite/NameOfTestCase` directly
< rcurtin> you can also get output like `CTEST_OUTPUT_ON_VERBOSE=1 ctest`