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/
nishantkr18 has joined #mlpack
nishantkr18 has quit [Ping timeout: 258 seconds]
nishantkr18 has joined #mlpack
nishantkr18 has quit [Remote host closed the connection]
< jenkins-mlpack2> Yippee, build fixed!
< jenkins-mlpack2> Project docker ensmallen nightly build build #138: FIXED in 49 min: http://ci.mlpack.org/job/docker%20ensmallen%20nightly%20build/138/
namangup has joined #mlpack
vikram2000b has joined #mlpack
< VikramSinghChund> I am having problem running test files. Please help. Thanks.
namangup has quit [Quit: namangup]
< jenkins-mlpack2> Yippee, build fixed!
< jenkins-mlpack2> Project docker mlpack nightly build build #579: FIXED in 3 hr 35 min: http://ci.mlpack.org/job/docker%20mlpack%20nightly%20build/579/
ImQ009 has joined #mlpack
vikram2000b has quit [Remote host closed the connection]
manit has joined #mlpack
Param-29 has joined #mlpack
< Param-29> Hello can someone give me official mail i.d for MLpack for gsoc 2020?
< jeffin143[m]> You meant mailing list ?
< jeffin143[m]> @Param-29
< jeffin143[m]> Param-29: ?
< Param-29> JaskaranKalra[m] I actually am interested in working on an idea in GSOC 2020's idea's list and I am trying to get in touch with mlpack about it. I wanted to know more about that project and also wanted to contribute to better understand code-base.
< jeffin143[m]> @Param-29 : you can do soo here too
< jeffin143[m]> Everyone here is related to Mlpack :)
< jeffin143[m]> Also you can use mailing list mentioned here https://www.mlpack.org/community.html and https://www.mlpack.org/gsoc.html. These link should have enough info for you to get started.
manit has quit [Remote host closed the connection]
hello has joined #mlpack
hello has quit [Remote host closed the connection]
< Param-29> So how can I start contributing..?
femi90 has joined #mlpack
< zoq> Param-29: Hello there, the getting involved section here: https://www.mlpack.org/community.html and in case you are here for GSoC https://www.mlpack.org/gsoc.html should be helpful.
< zoq> Param-29: Let us know if there is anything we should clarify.
< zoq> Param-29: Those pages have some starting points, like picking an interesting issue or contributiong some new methods etc.
< zoq> Param-29: Mainly to get familair with the codebase.
< Param-29> zoq that is hepful thank you sir.
femi90 has quit [Ping timeout: 260 seconds]
nishantkr18 has joined #mlpack
nishantkr18 has quit [Remote host closed the connection]
Param-29 has quit [Ping timeout: 260 seconds]
< Nakul[m]> > Nakul: You mean: CTEST_OUTPUT_ON_FAILURE=1 ctest -T Test does run fine on your system?
< Nakul[m]> zoq 1/156 Test #1: python_bindings_test .............***Failed 4.21 sec
< Nakul[m]> 17/156 Test #17: CallbackTest .....................***Failed 0.31 sec
< Nakul[m]> these test fails
< Nakul[m]> all other passed successfully
< zoq> Nakul[m]: Okay, so sounds like you can repoduce the callbacks test issue on your system as well.
sjd07 has joined #mlpack
< sjd07> hi guys , this is my first time joining the irc channel
sjd07 has left #mlpack []
Aniruddha90 has joined #mlpack
Aniruddha90 has quit [Remote host closed the connection]
< Nakul[m]> zoq: 17/156 Test #17: CallbackTest ..................... Passed 0.21 sec
< Nakul[m]> callback passed but how do i approch for failling of the python binding
< Nakul[m]> Khizir Siddiqui (Gitter): thanks a lot how silly of me 😂
metahost has quit [Ping timeout: 240 seconds]
metahost has joined #mlpack
< zoq> Nakul[m]: Also make sure to build with debug informations: cmake -DDEBUG=ON ..
< zoq> &B#&BVikramSing: You should build mlpack and the test suite, and run the test case with ctest or mlpack_test, instead of using g++ manually, let me know if I should clarify anything.
HimanshuPathakGi has joined #mlpack
< zoq> HimanshuPathak: Hello, yeah take a closer look intot he Recurrent Network issue is on my list, it looks like this is a windows specific problem.
< zoq> HimanshuPathak: You can ignore the issue if you haven't changed something in that direction.
< HimanshuPathakGi> Thanks for clarification zoq
ImQ009 has quit [Quit: Leaving]