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/
surfza2004 has joined #mlpack
surfza2004 has quit [Quit: Leaving]
< kartikdutt18Gitt>
Hi @zoq, what changes should I implement in #2163 ?
< kartikdutt18Gitt>
Hi everyone, I am seeking reviews for the PR #2163, any suggestions are welcome. Thanks.
< PrinceGuptaGitte>
Hi everyone, I'm trying to contribute to mlpack. Are there any issues I can help with.
< kartikdutt18Gitt>
Hi @prince776, this might be useful https://www.mlpack.org/gsoc.html to get started. You can also see issue page on mlpack repo and select "good-first-issues".
< PrinceGuptaGitte>
Thanks, good-first-issues is what I was looking for. I have read gsoc and community page already.
< PrinceGuptaGitte>
Hi, I am working on issue #2084 , I have done it for data::load() aspect but for that I had to build it 3-4 times and each time it takes a lot of time. Is there a better way to work? Like building specific files separately to main build ?
< HimanshuPathakGi>
Use -DBUILD_CLI_EXECUTABLES=OFF -DBUILD_PYTHON_BINDINGS=OFF -DBUILD_JULIA_BINDINGS=OFF while using cmake
< kartikdutt18Gitt>
@prince776 you can build certain files rather building everython
< PrinceGuptaGitte>
oh thanks I'll try it
< kartikdutt18Gitt>
Everything, like make test -j2
< HimanshuPathakGi>
Python binding helps us to use mlpack in python
< kartikdutt18Gitt>
Yes as @himanshupathak21061998 pointed certain things aren't necessary for certain issues and we can use make to disable them.
< PrinceGuptaGitte>
make: Nothing to be done for 'load_impl.hpp'. , it didn't build it
< kartikdutt18Gitt>
Only certia
< kartikdutt18Gitt>
only certain files/ folders can be built that way.
< HimanshuPathakGi>
Hey zoq I think we should add this as warning in documentation for doing a faster build or anything else
< HimanshuPathakGi>
@prince776
< PrinceGuptaGitte>
Sorry if I'm asking too much questions(I'm kindda new to this env) but how do I build a certain file say load_impl.hpp after making changes to it
< HimanshuPathakGi>
You need to specify target for this
< kartikdutt18Gitt>
Not an issue @prince776 , Ask as many as needed, people here are happy to help 😊.
< PrinceGuptaGitte>
When i specify target like : make load_impl , it says : *** No rule to make target 'load_impl'. Stop.
< kartikdutt18Gitt>
@prince776 I don't think there is build file for that.
< PrinceGuptaGitte>
Apparently whenever I make changes, if i call "sudo make install" in build directory it builds only the changed parts and changes are exhibited.
< PrinceGuptaGitte>
I guess this makes sense
< rcurtin>
oh no, I forgot about the video meet-up. the next one would be tomorrow at 1800 UTC (25 hours from now) though so I'll just send an email now :)
< rcurtin>
mdjordjic: if you prefer, you can open an issue on Github; for the large number of errors you are seeing, it might be easier to manage like that :)
< rcurtin>
up to you though of course
< rcurtin>
also, just a note, it turns out that the datacenter hosting mlpack.org will be closing at the end of February. so I'll have to run it across town to a new datacenter; I think we can keep the downtime to only a couple hours, and maybe we can set up some simple backups to keep various mlpack services online
< rcurtin>
I'll provide a bit more info as we get closer to the move... right now I am still calling different datacenters to see what's available
< rcurtin>
(this is just for mlpack.org, none of the build servers or anything)
< kartikdutt18Gitt>
Hi @rcurtin I finally fixed the benchmarks on #2178, if you get the chance kindly have a look. Thanks.
< rcurtin>
when I have a chance I will, I'm pretty overloaded at the moment. it will take a little while to carefully review the benchmarking code, etc.; benchmarking is not easy to get right :)
< kartikdutt18Gitt>
Sure Thanks, yes it is not that easy, I will try to come up with a graph for the same.Thanks
< rcurtin>
sounds good, thanks
< rcurtin>
I am *really* behind on PRs and mlpack right now, it's a bit overwhelming
< rcurtin>
I've only been able to spare a minute here or there over the past week or two, and next week I'm on vacation... :(
< kartikdutt18Gitt>
I understand, we need more reviewers.
< PrinceGuptaGitte>
Just a while ago "sudo make install" only built the files which were changed(so build process was very fast) but now it started building all files again.
< kartikdutt18Gitt>
Thanks for all help though, personally in pointing out errors in my benchmarking.
< rcurtin>
kartikdutt18Gitt: no problem :)
< rcurtin>
PrinceGuptaGitte: you should only need to do 'make' to rebuild, and CMake will build everything that depends on the files that you changed
< rcurtin>
so, e.g., if you changed src/mlpack/core.hpp, it would need to rebuild just about everything
UmarJ has quit [Quit: UmarJ]
UmarJ has joined #mlpack
< PrinceGuptaGitte>
For issue #2084 (Add manual type specification support to `data::Load()` and `data::Save()`)
< PrinceGuptaGitte>
When we specify extension should the filename given to parameter be still like ("data.csv")?
< PrinceGuptaGitte>
As in what should be the way it will be used :
< rcurtin>
PrinceGuptaGitte: have you seen PR #2135? it's linked to in the issue comments
< PrinceGuptaGitte>
Oh I didn't see that. I'm gonna see it to understand where to proceed and what to do. Thanks for pointing it out
< rcurtin>
what I'm saying is that there is already a PR open, so perhaps it would be better to try and help review and improve that one instead of starting over
ImQ009 has quit [Quit: Leaving]
< birm[m]>
How do we usually reassign stale PRs anyway? The new person probably won't have write access to the author's branch.
< zoq>
birm[m]: No official process in place, if anybody likes to work on a stale PR, just clone the branch (or cherry pick the commits) and open a new PR.