00:35 < rcurtin> Suryo: there's no page or word limit, but if the proposal is excessively long we are not guaranteed to read every word of it :)

00:50 < jeffin> Memory leakes in jenkins mean..??

00:51 < rcurtin> jeffin: they mean that there was a memory bug found in that PR

00:52 < jeffin> Umm, what could be a good reason, could you give an example for one.?

00:54 < rcurtin> I thought Jenkins generally said what the issue was, but you're right, it's not particularly helpful

00:54 < rcurtin> so try compiling with -DDEBUG=ON (that's part of the CMake configuration)

00:54 < rcurtin> and then building mlpack_test, and then you could use valgrind directly, i.e.

00:54 < rcurtin> valgrind --leak-check=full bin/mlpack_test -t LoadSaveTest/MalformedCSVTest

00:55 < rcurtin> and that should be helpful at figuring out where the problem might be :)

00:55 < jeffin> Ohh thanks a ton :-)

00:59 < jeffin> Rcurtin : would you be free to take a look at my gsoc proposal and just briefly tell if any big blunder is there or not

01:00 < rcurtin> no time at the moment, but maybe in the upcoming weeks

01:01 < rcurtin> too many PRs to try and review :)

01:01 < jeffin> Sure, I wont pester you much

01:01 < rcurtin> no worries---I help as I'm able to :)

01:01 < jeffin> Carry on , good luck

01:05 < rcurtin> thanks

01:36 < mrkeremyilmaz> \HELP

02:14 < jeffin> Rcurtin : please terminate the job in memory check pipe line...my code takes 3 hours it would just waste memory..i would check locally what the issue is just like you quoted then submit for check in jenkins

02:16 < rcurtin> sounds good, let me do that now

02:17 < rcurtin> I cancelled #1145, should I also cancel #1146?

02:17 < rcurtin> http://ci.mlpack.org/job/pull-requests%20mlpack%20memory/

02:17 < rcurtin> it looks like both were different versions of your PR

02:17 < jeffin> Yes cancel it

02:17 < jeffin> Too

02:17 < jeffin> No issues...i would do a fresh one later this afternoon

02:20 < rcurtin> sounds good

04:30 < mulx10> rcurtin, jeffin: I happen to know the issue you are facing. It happened with my PR #1756 as well. If load_and_save test is edited, jenkins executes `LoadSaveTest`. One of the test namely `CaseTest` blocks because data::LoadARFF gets stuck in an infinite loop when the file it is looking for is not found (it terminates after 180 mins). I opened an issue #1791 and proposed a PR #1793 for the same . Once the PR gets merged then the memory c

04:32 < jeffin> Mulx10 : yup i figured out it too after seeing your pr , I commented out the test and then ran a mem check and it was fine ,

04:32 < mulx10> Once the PR gets merged then the memory checks wont fail.

04:36 < jeffin> Cool

04:37 < mulx10> I repeated the message because somehow it got cut. :)

04:38 < jeffin> Haha :) no issues

11:54 < Viserion> Anyone for help in building support for normalization in cf?

12:13 < zoq> Viserion: Did you see my last message?

12:13 < Viserion> No, sorry.

12:15 < zoq> Viserion: http://mlpack.org/irc/

12:16 < Viserion> Yah I fixed that

12:17 < Viserion> But I don't see why this pops up?

12:18 < Viserion> In file included from /home/viserion/MLPACK/build/src/mlpack/bindings/python/generate_pyx_cf.cpp:34:0: /home/viserion/MLPACK/src/mlpack/methods/cf/cf_main.cpp: In function ‘void AssembleFactorizerType(const string&, const string&, arma::mat&, size_t)’: /home/viserion/MLPACK/src/mlpack/methods/cf/cf_main.cpp:399:95: error: no matching function for call to ‘PerformAction(arma::mat&, const size_t&, const size_t&, const double&)

12:19 < zoq> Is this part of your fork?

12:20 < Viserion> PerformAction<NMFPolicy, CombinedNormalization>(dataset, rank, maxIterations, minResidue);

12:20 < whoKnows> can anybody help me out how I can use mlpack in dev c++

12:21 < zoq> Viserion: Did you update your fork (github)?

12:22 < zoq> whoKnows: http://mlpack.org/docs/mlpack-git/doxygen/build.html should be helpful.

12:22 < zoq> whoKnows: If you like to contribute I would clone the github master branch.

12:54 < Viserion> Yah all chqnges r in there

12:55 < Viserion> @zoq

13:40 < ShikharJ> rcurtin: Are you there?

13:51 < rcurtin> ShikharJ: yep, I'm here now

13:52 < ShikharJ> I just wanted your opinion on https://github.com/mlpack/mlpack/pull/1777

13:53 < rcurtin> sure, let me look

13:53 < rcurtin> it was on my list but hadn't gotten to it quite yet

13:54 < ShikharJ> rcurtin: Yeah, even I've found the daily load to be quite on the high side these days.

13:54 < rcurtin> I started using a Github project board to manage what I was working on, but I'm not sure it's really working very much better than what I did before (which was just a giant list of flagged emails from issues that I wanted to do something with)

13:55 < rcurtin> yesterday the 'needs review' category had like 17 in it, 'needs implementation' had 8, 'needs response' had 6, 'waiting on activity' had like 15

13:55 < rcurtin> so I think I need to rework the categories. the way it currently is doesn't seem to be helping me prioritize and foucs

13:55 < rcurtin> focus*

13:55 < rcurtin> March is always crazy though with GSoC :)

13:56 < ShikharJ> Yeah, though we can't rush either :)

13:56 < rcurtin> the actual summer itself has always seemed to be less work (except for that year where I stupidly thought that mentoring 5 students was something I could do...)

13:56 < ShikharJ> I kind of wish it was like this throughout the year, imagine the amount of work we could get done and things we could explore.

13:57 < rcurtin> that's true but my inbox would be really scary year-round :(

13:57 < ShikharJ> Oh yes, most definitely.

17:40 < Viserion> @zoq yes it is updated

17:46 < mulx10> Hello everyone, I am Mehul Kumar Nirala third year undergraduate in the department of Computer Science at IIT Kharagpur. I congratulate MLPACK for being accepted in Google Summer of Code 2019. I have been working on NLP for the past one year as Course Project and on Reinforcement learning as a self-project. I want to take up String Processing Utilities. I have started contributing to mlpack. I am currently building up small necessary

17:47 < mulx10> I am currently building up small necessary packages that would help me implement String Processing Utilities. A sincere thanks to all the mentors and the contributors for the support I received.

17:47 < rcurtin> mulx10: hey there; thanks for the contributions you've made and bug you've fixed so far---it's definitely helpful :)

17:49 < mulx10> rcurtin: Thanks.

20:28 < gauravcr7rm> zoq: Hello sir , currently i am working on the neat project and i remember you once mentioned that one of the task to be done here is to figure out a way for fast add/remove of nodes from the graph.

20:30 < gauravcr7rm> zoq: Can i implement it using GRAPH X cross over technique which dont need sorting or other things but for that we have to figure out a way for speciating. Can you please give a comment here which can help me. Thanks in advance.

21:44 < abdullah_> hi

22:40 < zoq> gauravcr7rm: Are you talking about: http://www.cs.bham.ac.uk/~wbl/biblio/gecco2004/LBP040.pdf ?