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/
< AakashkaushikGit> Thanks @zoq
_slack_mlpack_46 has joined #mlpack
kunalsingh2002Gi has joined #mlpack
< kunalsingh2002Gi> Hello Mentors , I'm KUNAL SINGH 2nd year computer science undergraduate from IIT Kharagpur, India , I'm very much interested in contributing to mlpack but I'm unable to find a starting point , can anyone help me with this ?
SuryamArnavKalra has joined #mlpack
< SuryamArnavKalra> Hi developers !
< SuryamArnavKalra> I am Suryam Arnav Kalra , second year undergraduate student in Computer Science and Engineering department at IIT Kharagpur , India.
< SuryamArnavKalra> I am a beginner in open source and i am interested in contributing to mlpack. It would be really great if you could help me get a starting point to begin my journey
Samyak has joined #mlpack
< NippunSharmaGitt> Hi @suryam35 @kunalsingh2002 , you can look at the community page as a start [https://www.mlpack.org/community.html ]( https://www.mlpack.org/community.html), [https://www.mlpack.org/gsoc.html ]( https://www.mlpack.org/gsoc.html ) might be helpful
< RishabhGarg108Gi> @suryam35 @kunalsingh2002 , taking up a "good first issue" would be a good entry point. If you don't find anything interesting to work, then you can always open an issue for something that you would like to work and could be added to mlpack. Feel free to post your queries here :)
< Samyak> Hi, I am working on parallelization using MPI(message passing interface) library. Has anyone worked before in this area? Are there any challenges you faced for any particular algorithm?
Samyak has left #mlpack []
Samyak has joined #mlpack
ib07 has joined #mlpack
Samyak has quit [Ping timeout: 245 seconds]
ImQ009 has joined #mlpack
ib07 has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
< NippunSharmaGitt> Hi I was looking at the source code of the automatic bindings of mlpack. Can someone tell what will be a good place to start understanding it ?
qur70 has joined #mlpack
_qur70 has joined #mlpack
qur70 has quit [Ping timeout: 268 seconds]
_slack_mlpack_49 has joined #mlpack
_qur70 has quit [Ping timeout: 272 seconds]
qur70 has joined #mlpack
ishita has joined #mlpack
ishita has quit [Remote host closed the connection]
< jeffin143[m]> @yashwants19:matrix.org: are you there?
ib07 has joined #mlpack
ImQ009 has quit [Quit: Leaving]
VivekTalwarGitte has joined #mlpack
< VivekTalwarGitte> Hello Everyone , I'm Vivek Talwar 1st year computer science graduate at IIIT Hyderabad, India , I'm very much interested in contributing to mlpack
< zoq> VivekTalwarGitte: Hello there, in case you search for a starting point, checkout our community page - https://www.mlpack.org/community.html
< VivekTalwarGitte> thanks
< VivekTalwarGitte> Is it compulsory to contribute in C++ only or we can contribute in python bindings as well
< VivekTalwarGitte> ?
< VivekTalwarGitte> I am referring this to get started in python
< zoq> VivekTalwarGitte: If you like to contribute a new method or extend an exsisting method, you need to do that in C++; the Python bindings always use the C++ implementation.
< VivekTalwarGitte> let me get my hands dirty with some starting modules and work around with basics and than think of how I can contribute to the current methods
< VivekTalwarGitte> or propose a new one altogether in C++
< zoq> Sounds good, let us konw if there is anything we can clarify.
< zoq> AakashkaushikGit: Got the simple network working, I'll create a bigger network and compare it with the current implementation.
< shrit[m]> vivektalwar13071999 you can add some examples in Python in the example repository
< zoq> A first test shows that the boost:variant approach is slightly -> boost::variant 70.1904s : vtable 70.2215s
< zoq> faster
< rcurtin> zoq: interesting; is that the average over three trials?
< zoq> 5, I'll open a PR with some results tomorrow.
< zoq> If the difference is that marginal, I guess we don't have to stick with the variant approach.
< rcurtin> awesome, interested to see the results
< rcurtin> I guess the other part of the picture is compile time and memory usage
< shrit[m]> that is good to here, the difference is very marginal 100 ms seconds for boost variant,
< shrit[m]> zoq thanks for creating the results, also a big thanks for aakash-kaushik for working on the experiment
< shrit[m]> Also I think we are going to gain a lot of compile time, however I am not sure about memory usage, I do not see any reason that the memory usage increases with vtable
< rcurtin[m]> oh, I meant memory usage during compilation. I doubt boost::visitor usage has any runtime memory issues