03:57 <jjb[m]> ryan tested the PR using the example in the issue ticket. Works splendidly. Need to remove two debug lines.

03:57 <jjb[m]> <https://github.com/mlpack/mlpack/issues/3021#issuecomment-921435072>

10:21 <jonpsy[m]> welcome Ashutosh Kumar

10:21 <AshutoshKumar[m]> Thanks

10:21 <jonpsy[m]> Would you like to introduce yourself?

10:22 <AshutoshKumar[m]> ok

10:22 <AshutoshKumar[m]> So I am Final Year BTech Student at MNNIT Allahabad

10:22 <AshutoshKumar[m]> CSE

10:22 <AshutoshKumar[m]> I have interest in Deep Learning, BlockChain

10:23 <AshutoshKumar[m]> I begining with open source and would like to start with mlpack because it aligns with my interests

10:23 <jonpsy[m]> Have a look at [CONTRIBUTING.md](https://github.com/mlpack/mlpack/blob/master/CONTRIBUTING.md)

10:24 <jonpsy[m]> also, today we have a meet. So feel free to join and ask your question

10:24 <jonpsy[m]> * also, I guess today we

10:24 <AshutoshKumar[m]> Sure

11:00 <jonpsy[m]> zoq: Remember the rocket injector notebook ? Tried running today, had a runtime error + the notebook was loading indefinetely and there's a good chance it's leaking memory. Let's talk about it in meet

14:59 <zoq[m]1> <jonpsy[m]> "zoq: Remember the rocket..." <- Hm, I tested it like a week ago, worked fine.

15:00 <rcurtin[m]> ahh, unfortunately I have an in-person company meetup over lunch today so I won't be able to make the video chat :(

15:01 <zoq[m]1> I have a clash with another meeting as well, not sure I can make it today.

15:02 <shrit[m]> Same here

15:07 <zoq[m]1> <zoq[m]1> "Hm, I tested it like a week ago,..." <- Looks like some problem with the sos kernel, will take a closer look. Why do you think there is a memory issue?

15:12 <jonpsy[m]> because when i tested memory hit 2.1 GB / 2\

15:12 <jonpsy[m]> s/\/ GB./

15:13 <zoq[m]1> jonpsy[m]: I think this is what I see locally as well, that it hits 2GB quite fast.

15:13 <jonpsy[m]> yeah, but i dont recall that happening previously

15:13 <jonpsy[m]> <zoq[m]1> "Looks like some problem with the..." <- so this error was "waiting for something" in runtime which never finished executing. Smells like memory leak

15:15 <zoq[m]1> jonpsy[m]: This could be anything.

15:16 <zoq[m]1> this is what I get

15:16 <jonpsy[m]> tracemalloc

15:16 <jonpsy[m]> yeah

15:16 <jonpsy[m]> "coroutine 'ZMQSocketChannel.get_msg' was never awaited" this is what i meant by "waiting".

15:17 <zoq[m]1> Sure, but this is more like some strange issue with the sos kernel, nothing on the ens/mlpack side.

15:17 <jonpsy[m]> that's true, because we hadn't faced this before

15:18 <zoq[m]1> At least we don't allocate any memory here, we just include a header file.

15:18 <jonpsy[m]> that, and i also wanted to talk about the "Python-C" utils in our examples repo. Should we ditch them for SoS, the extra code we write to manipulate our data and send to Python is super cumbersome

15:18 <jonpsy[m]> that block of code really feels out of place

15:19 <zoq[m]1> If you like you can update the notebooks, but having the python bindings allows us to run the notebooks outside a notebook env.

15:23 <jonpsy[m]> True, but I guess we should consider the effort vs reward ratio

15:25 <jonpsy[m]> Python's C-API is very error prone, and formatting C++ data to be compatible for Python C-API makes it kinda hard to grasp, given it isn't even related to the actual code.

15:27 <zoq[m]1> True, in some cases, the Python-C API is not as clean, as I said we can have both worlds, if you like to move all the python code into the sos kernel, go for it.

15:28 <zoq[m]1> But at least at this point I don't see a reason to remove the existing utils, maybe we can remove them later if we found a better way.

15:29 <jonpsy[m]> I guess, we can make current utils "depreceated"

15:29 <jonpsy[m]> and encourage future dev's to use SoS kernel, as for the existing which use utils, we could provide an additional code block doing it in SoS kernel.

15:29 <zoq[m]1> and just say you have to run everything in a notebook?

15:30 <jonpsy[m]> Ah, I see. So only for the notebooks then

15:31 <zoq[m]1> I mean I'm fine to say you have to use a notebook, but it would be nice to run the examples outside a notebook as well.

15:32 <jonpsy[m]> I see your point now. So, you're saying users should get plots even in the cpp examples. Correct?

15:32 <zoq[m]1> I guess, we could also say, you have to run the python script separately.

15:33 <jonpsy[m]> > I see your point now. So, you're saying users should get plots even in the cpp examples. Correct?

15:33 <jonpsy[m]> have i gotten it correct?

15:34 <zoq[m]1> yes

15:35 <jonpsy[m]> Okay, so for the notebook we should prefer SoS kernel for plots. But for existing cpp examples, we can go with whats currently there

16:31 <zoq[m]1> Hello everyone, mlpack video meet in about 30 minutes, see https://www.mlpack.org/community.html for more details. Some of us can't make it today, but you can use the zoom room anyway.