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/
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Remote host closed the connection]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
favre49 has joined #mlpack
xiaohong has joined #mlpack
< abernauer[m]>
rcurtin: Going to work on #1021 for Fast mks over the holidays.
xiaohong has quit [Ping timeout: 260 seconds]
< favre49>
mlpack.org/irc seems to be a bit off btw, It seems to be a frankenstein off the old website and the new one
< favre49>
The new website is very nice though, I'm liking it :)
< abernauer[m]>
favre49: Persona fan? I noticed your github profile picture.
< favre49>
unfortunately I don't own a console, so I've never actually played the game, but I enjoyed watching the playthroughs and I did watch some of the animation :)
< abernauer[m]>
I need to finish Persona 5 it's on my backlog. I have two of the palaces or dungeons left to finish. It's a good game tim consuming though.
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
favre49 has quit [Remote host closed the connection]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
favre49 has joined #mlpack
< favre49>
rcurtin: Also, did anyone ever work on CMake modernization? I'm interested in learning more about build systems, so if no one has done it I'd like to work on it
favre49 has quit [Remote host closed the connection]
favre49 has joined #mlpack
< favre49>
Ah oops, just noticed you were planning it for this time's GSoC, didn't notice that you had just added it
favre49 has quit [Remote host closed the connection]
< birm[m]1>
favre49: No reason not to work on it anyway :)
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
nakul has joined #mlpack
xiaohong has joined #mlpack
nakul has quit [Remote host closed the connection]
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
keyurk4271 has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
keyurk4271 has quit [Remote host closed the connection]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
KeyurKumbhare[m] has joined #mlpack
KeyurKumbhare[m] is now known as Keyur[m]
< Keyur[m]>
Hello. I'm Keyur and I'm in my second year of engineering. I'm really excited to know about the organisation and contribute. What is the best way to get started?
< ShikharJaiswalGi>
I saw that a PR was opened for the same making use of visitors (https://github.com/mlpack/mlpack/pull/2122). I think the issue is better solved using debug mode assertion semantics for the sake of performance during execution. I believe a lot of our existing use of visitors can also be reduced under such a paradigm.
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
SlackIntegration has quit [Quit: killed]
benpa[m] has quit [Quit: killed]
GitterIntegratio has quit [Quit: killed]
Cadair has quit [Quit: killed]
Nakul[m] has quit [Quit: killed]
jeffinsamGitter[ has quit [Quit: killed]
ryan[m] has quit [Quit: killed]
KimSangYeon-DGU4 has quit [Quit: killed]
benpa-bpulse[m] has quit [Quit: killed]
ryan[m]1 has quit [Quit: killed]
birm[m]1 has quit [Quit: killed]
rcurtin[m] has quit [Quit: killed]
HimanshuPathakGi has quit [Quit: killed]
HimujjalUpadhyay has quit [Quit: killed]
ShikharJaiswalGi has quit [Quit: killed]
abernauer[m] has quit [Quit: killed]
JaskaranKalra[m] has quit [Quit: killed]
zoq[m] has quit [Quit: killed]
ToshalAgrawalGit has quit [Quit: killed]
RyanCurtinGitter has quit [Quit: killed]
bhanukumarGitter has quit [Quit: killed]
jeffin143[m] has quit [Quit: killed]
Sergobot has quit [Quit: killed]
PulkitgeraGitter has quit [Quit: killed]
Keyur[m] has quit [Quit: killed]
DavidGitter[m] has quit [Quit: killed]
funkypopsicle[m] has quit [Quit: killed]
KimSangYeon-DGU[ has quit [Quit: killed]
kiwi24[m] has quit [Quit: killed]
PiyushChaudhariG has quit [Quit: killed]
sreenik[m] has quit [Quit: killed]
xiaohong has joined #mlpack
funkypopsicle[m] has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
GitterIntegratio has joined #mlpack
benpa[m] has joined #mlpack
SlackIntegration has joined #mlpack
Cadair has joined #mlpack
kiwi24[m] has joined #mlpack
PiyushChaudhariG has joined #mlpack
KimSangYeon-DGU[ has joined #mlpack
ryan[m] has joined #mlpack
HimujjalUpadhyay has joined #mlpack
abernauer[m] has joined #mlpack
PulkitgeraGitter has joined #mlpack
birm[m] has joined #mlpack
KimSangYeon-DGU4 has joined #mlpack
Sergobot has joined #mlpack
bhanukumarGitter has joined #mlpack
benpa-bpulse[m] has joined #mlpack
ToshalAgrawalGit has joined #mlpack
DavidGitter[m] has joined #mlpack
ShikharJaiswalGi has joined #mlpack
RyanCurtinGitter has joined #mlpack
rcurtin[m] has joined #mlpack
zoq[m] has joined #mlpack
jeffinsamGitter[ has joined #mlpack
jeffin143[m] has joined #mlpack
ryan[m]1 has joined #mlpack
Keyur[m] has joined #mlpack
JaskaranKalra[m] has joined #mlpack
HimanshuPathakGi has joined #mlpack
birm[m]1 has joined #mlpack
Nakul[m] has joined #mlpack
< rcurtin>
@ShikharJ: I see what you mean, the only problem is that most people will not compile with debug mode assertions, so those errors might not ever be seen
< rcurtin>
maybe the debug mode configuration can be changed somewhat... so, e.g., Log::Debug and any Armadillo assertions are only removed if -DNDEBUG is defined, or something like that
< rcurtin>
(we can then change the default CMake configuration so that -DDEBUG=OFF, like it is now, but add an option -DNDEBUG that specifies whether the -DNDEBUG macro is defined, and leave that off by default except for releases? I dunno, just an idea)
xiaohong has quit [Ping timeout: 260 seconds]
< rcurtin>
feel free to comment in the issue or PR itself; I haven't had a chance to look at the PR that khizirsiddiqui just opened
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
sreenik[m] has joined #mlpack
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
< abernauer[m]>
I think I lost the salary negotiation question on the first interview.
< rcurtin>
abernauer[m]: nothing is ever lost until you have signed a contract :)
xiaohong has joined #mlpack
< abernauer[m]>
That's definitely legally true. I should have delayed that question to a final interview or atleast knowing I would be hired.
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 260 seconds]
< ShikharJaiswalGi>
@rcurtin The debug mode assertions are bound to be controlled at compile time under CMake. My vision is, that people compile and run in execution mode (no assertions enabled) by default, and when that fails, re-compile with a `Debug = ON` flag (which would enable the assertions) with the CMake command, and re-run the program to check for issues in the code. So we preserve performance, and provide the necessary
< ShikharJaiswalGi>
debugging support as well.
< ShikharJaiswalGi>
If my intuition is correct, in this way, we can deploy assertions to every major piece of mlpack API, without having an issue with internally calling visitors. If I'm not wrong, this is also how many computational engines (which have a whole lot more expressions to check internally) keep things in account.
< ShikharJaiswalGi>
Again, this is merely an idea, and I'd appreciate any input on this from the community :)
xiaohong has joined #mlpack
< abernauer[m]>
Nakul: Did you happen to copy and paste some code when you wrote that test which is giving a compiler error?
xiaohong has quit [Ping timeout: 260 seconds]
ImQ009 has quit [Quit: Leaving]
< Nakul[m]>
@abernauer:matrix.org: ya actually by adding template in the whole implementation of softmax i had told change all the affected files , in that way and I messed something so I copied and pasted some old code ...
< Nakul[m]>
I tried all the day ,and will try next as well 😂
< Nakul[m]>
*to
< abernauer[m]>
Yeah probably not a good idea to copy and paste template code without adapting it. I can tell you from my personal experience.
< Nakul[m]>
Yeahhh it was my first experience , will keep in mind next time ...
< Nakul[m]>
Your book was nice but there is toooo muchh tcontent though
< abernauer[m]>
There is probably an issue with the types or conflciting template definitions based on that error. Maybe a syntax error.
< abernauer[m]>
The input operator, >>, is a common source of problems with template code.
< Nakul[m]>
Thanks will try tomorrow ..
xiaohong has joined #mlpack
< abernauer[m]>
I will look at the error some more and see if I can help you figure it out.
< Nakul[m]>
I don't think syntax error as syntax error are highlighted but may be... since highlighter some time work some time not..
< abernauer[m]>
If there is something that doesn't make sense in that explanation I can try and explain it to you.
< rcurtin>
@ShikharJ: that sounds reasonable to me, so long as we document it (maybe an FAQ page on the website or something); we just need users to know that if there is a problem, they should first recompile with debugging symbols :)
< rcurtin>
especially for header-only code like the ANN code, this works, because they just have to recompile their program with debugging symbols, and not the mlpack library itself