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/
Agzam has joined #mlpack
Agzam has quit [Client Quit]
Agzam has joined #mlpack
Agzam has quit [Client Quit]
AlanSanchezGitte has joined #mlpack
< AlanSanchezGitte> Hi, hope you all are ok and stay safe during the COVID breakout. I'm Alan Sanchez, a 4th-year student majoring in Applied Math in UASLP, México. I'm pretty new to mlpack since I've worked a bit of ML just using R. I've taken many upper-division courses; two of them are Multivariate Statistics and Time Series. I'm accustomed to Python due to Coding Theory schemes and programs, but I would like to get familiar with
< AlanSanchezGitte> mlpack package. My main programming language is C++, where I've worked in Oriented-object programming. Hope I may learn a lot from you. I'll be trying to help out and keep updated during the GSoC process!
< zoq> AlanSanchezGitte: Welcome, let us know if there is anything that needs clarification, also in case you haven't seen it yet we have a dedicated GSoC page - https://www.mlpack.org/gsoc.html that has some starting pointers.
yfgeng6Gitter[m] has joined #mlpack
< yfgeng6Gitter[m]> Hi everyone. I’m GENG Yunfan, a postgraduate in University of California Irvine and got my bachelor degree in computer science from Chinese University of Hong Kong. Due to the COVID-19, I am currently working as a research intern in Autonomous Driving team of an AI company, Sensetime in China and my duty is to design some decision algorithms. I have taken some ML and deep learning courses so I think I am familiar
< yfgeng6Gitter[m]> with CV, Graph embedding and RL. My intern job right now is relevant with RL and main coding language is c++. As a CS student I can code with python, C/C++. I am new to mlpack and GSoC but I think it will be a good chance for me to learn from the community whether or not I can get into this program. I am looking forward to be able to contribute to the open source communities!
< NippunSharmaGitt> Hey @yfgeng6 welcome to the community. A good way to start can be to build mlpack from source [https://www.mlpack.org/doc/mlpack-git/doxygen/build.html](https://www.mlpack.org/doc/mlpack-git/doxygen/build.html) you can also look at [https://www.mlpack.org/gsoc.html](https://www.mlpack.org/gsoc.html) for more information on GSoC.
< yfgeng6Gitter[m]> Thanks @NippunSharma I have started reading these documents 😏
< NippunSharmaGitt> 👍
< RishabhGargGitte> > `rcurtin (@ryan:ratml.org)` Basically in the tests, we just want to ensure that all the options work as desired, and that reasonable errors are thrown when invalid options are passed. There's no need to test the actual algorithms themselves, as that should be done in the test for the algorithm
< RishabhGargGitte> Thanks. I will try writing a few tests and will ask here if I run into any other issue :)
ruskinmanku has joined #mlpack
ruskinmanku has quit [Quit: Connection closed]
treepruner has joined #mlpack
kartikdutt18[m] has quit [Quit: Idle for 30+ days]
ImQ009 has joined #mlpack
treepruner has quit [Quit: Connection closed]
vansika__ has joined #mlpack
< AvikantSrivasta4> Hey Mayank, welcome to the community
< AvikantSrivasta4> You can follow this link
< AvikantSrivasta4> <https://www.mlpack.org/doc/mlpack-git/doxygen/build.html|https://www.mlpack.org/doc/mlpack-git/doxygen/build.html>
< AvikantSrivasta4> And try to build mlpack from scratch
< jonpsy[m]> Hey again! I've noticed in the codebase, we often leave the job of checkin arg validity to Optimize()/Train() instead of to ctor
< jonpsy[m]> oh and one more, i think ctor delegating is c++11 feature, wouldnt be a cool feature to add? :)
< RishabhGargGitte> Hii, I was skimming through the Decision tree codebase and I realized that we have only a `Classify` function for trees. Does this mean that they are meant only for classification and not for regression ? Or did I overlook something ?
< rcurtin[m]> Rishabh Garg (Gitter) : right, our decision tree implementation is classification only. I think there is an issue open about extending that support to regression too
< RishabhGargGitte> I see. Can you please point me to the issue? Thanks :)
< zoq[m]> <jonpsy[m] "Hey again! I've noticed in the c"> By doing it inside Optimize()/Train() allows the user to modify parameters after object instantiation. This also means I can test different method settings without copying the object and still have a validation.
< jonpsy[m]> Interesting..
< jonpsy[m]> But isn't this possible with ctor validation as well? After instantiation, I can always use setter to change it's value
< jonpsy[m]> + added bonus of class not created on nonsensical args
< zoq[m]> Sure you can change values, but in this case you skip the validation step since you moved it into the ctor, right?
< jonpsy[m]> Hm
< jonpsy[m]> Because say we're calling Train multiple times. It'll do the checks that many times
< jonpsy[m]> Ah, that means id have to put conditions in setters
< jonpsy[m]> Wouldn't that be better tho? The ctor could call the setters as well. There, fixed it!
< zoq[m]> The issue here is that you would have to change the setter interface from int& size() { return size; } to void size(int s) {}. And lose the convince of changing a setting with obj.size() = 3.
< jonpsy[m]> I see
< zoq[m]> If you see a valuable benefit from putting validation into the ctor, please feel free to open an issue for discussion. Nothing is set in stone.
< jonpsy[m]> Thanks! I was wondering, about the mail I sent on adding algorithm or refactoring. What would be better?
< zoq[m]> Both are good maybe they can be combined? I guess depends on what algorithm you would select, if it’s a complex one, better to focus on one thing.
< jonpsy[m]> Glad you think that way ^_^. I want keep the scope lesser to produce a quality gsoc project.
< jonpsy[m]> Perhaps only 1 algo(SPEA )+ refactoring.
< zoq[m]> <jonpsy[m] "Perhaps only 1 algo(SPEA )+ refa"> Might be a solution if you go for it make sure to point out what you are planning to do first.
< jonpsy[m]> Refactoring definitely.
Khaled50 has joined #mlpack
Khaled50 has quit [Client Quit]
< jonpsy[m]> Oleksandr Nikolskyy hi oleskandr, check this out. A good way to start can be to build mlpack from source [https://www.mlpack.org/doc/mlpack-git/doxygen/build.html](https://www.mlpack.org/doc/mlpack-git/doxygen/build.html) you can also look at [https://www.mlpack.org/gsoc.html](https://www.mlpack.org/gsoc.html) for more information on GSoC.
< zoq[m]> > <@_slack_mlpack_U01RJC8AB2M:matrix.org> Hi everyone, I am Oleksandr, just finished my Bachelor of Science in Math & CS at the University of Bonn.
< zoq[m]> > I am looking forward contributing and learning things!
< zoq[m]> Welcome, let us know if you have any questions. Btw. Oleksandr that is a neat name don’t think I heard that one before.
< zoq[m]> <jonpsy[m] "Refactoring definitely. "> Makes sense, yes.
< jonpsy[m]> I'll have to think long and hard for this. I'll create an issue and tag you? We can discuss there :)
< zoq[m]> <jonpsy[m] "I'll have to think long and hard"> Sounds good.
< zoq[m]> > <@_slack_mlpack_U01RJC8AB2M:matrix.org> Thank's! I'll definitely keep in touch.
< zoq[m]> > It's Ukrainian variant of the Greek name Alexander.
< zoq[m]> Ahh, I didn’t knew that, cool.
r0hit2005 has joined #mlpack
r0hit2005 has quit [Client Quit]
ImQ009 has quit [Quit: Leaving]