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/
< GauravGhati[m]> Hey everyone, I was thinking to open a new issue for the result of static code analysis report, there are a lot of small errors and warnings which will be easy for the beginners to solve.
< GauravGhati[m]> Also, I was considering to host the HTML format report on GitHub pages, so that everyone can look at errors and bugs and can work on them.
< GauravGhati[m]> so, should i open one?
< GauravGhati[m]> Here is static code analysis report in HTML format - <https://gauravghati.github.io/StaticCodeAnalysisReport/>
< Anmol2001Gitter[> @zoq thanks for clarifying : )
ImQ009 has joined #mlpack
< zoq> GauravGhati[m]: Almost all of the errors are false postive e.g. "Such expressions using the ',' operator are dangerous. Make sure the expression is correct."
< zoq> GauravGhati[m]: So let's filter them out first.
< GauravGhati[m]> okay, should i filter it manually?
< rcurtin[m]> Manish Kausik H that sounds like a nice addition, feel free!
< rcurtin[m]> Gaurav Ghati looks nice!
< zoq> GauravGhati[m]: If you can filter the issues out that would be great, I don't think there is a filter option.
< zoq> There are more false positive issues, but I can go over the list before we open an issue.
< zoq> We just should make sure the issues listed are all valid.
< rcurtin[m]> Agreed, there are some on that list that would be very hard to change (like the mlpack_main.hpp issue)
< rcurtin[m]> in fact, for that one, having one `testName` per translation unit was exactly the desired goal :)
hrs84 has joined #mlpack
hrs84 has left #mlpack []
PrateekGuptaGitt has joined #mlpack
< PrateekGuptaGitt> hello everyone myself Prateek gupta from IIT kanpur btech 2nd year i am interested in contributing in open source,can anyone help me to figure out where to start
< zoq> PrateekGuptaGitt: Hello there, the community page - https://www.mlpack.org/community.html has some pointers for how to get started.
< zoq> https://www.mlpack.org/gsoc.html might be interesting as well
jerianjer has joined #mlpack
< GauravGhati[m]> zoq sure, I'll try to filter all and then let you know.
UmarJ has joined #mlpack
< rcurtin[m]> huh, my "hard drive" failure was actually an incorrect diagnosis; it seems that this was a thermal issue---when I thought that the system was hanging because of some I/O operations that were failing, actually what was happening was that the processor was exceeding temperature thresholds and throttling itself severely
< rcurtin[m]> I took off the heatsink and sure enough there were exposed bits of the processor with no thermal compound on them...
UmarJ has quit [Quit: UmarJ]
UmarJ has joined #mlpack
< zoq> Interesting, but doesn't that mean the problem was there from the beginning or does termal compound expiry?
< rcurtin[m]> It must go bad after long enough... this had never been a problem before now even though I was basically doing `make -j8` all day long 😃
< zoq> Hm, how old is your system?
< rcurtin[m]> about 9 years, from 2011
< rcurtin[m]> or I guess 10 now? 😃
< zoq> long time
< rcurtin[m]> yeah, pretty happy with the life I got out of it. I guess I could keep it going but I already ordered parts for a new system :)
< rcurtin[m]> I'll probably just turn it into a Jenkins build slave
< zoq> haha, the new system AMD or Intel?
< rcurtin[m]> Intel actually, for two reasons: (1) the Intel processors have interesting AVX512 instructions (2) the AMD processors are completely sold out 🤣
< zoq> Yeah, I can see the reason to go with AVX.
ImQ009 has quit [Quit: Leaving]
UmarJ has quit [Ping timeout: 260 seconds]
UmarJ has joined #mlpack