02:15 < travis-ci> mlpack/ensmallen#90 (ensmallen-1.13.0 - 2b9bdea : Ryan Curtin): The build passed.

02:15 < travis-ci> Change view : https://github.com/mlpack/ensmallen/compare/2b71ec742e81^...2b9bdeae7d7b

02:15 < travis-ci> Build details : https://travis-ci.org/mlpack/ensmallen/builds/479691142

03:41 < ShikharJ> Hmm, interesting, today I complete my first year of working with mlpack :)

03:55 < rcurtin> ShikharJ: happy mlpack anniversary! It seems like it has been a good year :)

04:01 < ShikharJ> rcurtin: Yeah, learned a lot. Personally, it was one of the most productive and fruitful years of my life.

04:15 < rcurtin> :)

04:16 < rcurtin> well hopefully this year can be as good also (assuming that productivity == good which is not always true :))

04:17 < rcurtin> I'm gonna head to bed

04:18 < rcurtin> but I did notice that the travis build on xenial takes only 30-40 minutes (or at least it did for this trial) so that is a really nice improvement

04:18 < rcurtin> probably compile speed improvements via a newer gcc version or something

04:22 < KimSangYeon-DGU> ShikharJ: Congratulations! :)

05:46 < niteya> rcurtin: Can you review my PR #1632

08:36 < bg2404> Hi, I'm a beginner. I well-versed with C++ and have a little background in machine learning. I want to contribute to mlpack. Can someone help me in getting started?

08:42 < jenkins-mlpack2> Project docker mlpack nightly build build #188: STILL UNSTABLE in 3 hr 28 min: http://ci.mlpack.org/job/docker%20mlpack%20nightly%20build/188/

12:33 < zoq> bg2404: Hello there, https://www.mlpack.org/involved.html and https://www.mlpack.org/gsoc.html should be helpful, let me know if I should clarify anything.

13:22 < nick123456789> Hi all. I have a question regarding the use of the DBSCAN class. I have an application where I repeatedly want to cluster datapoints from maesurements. For this I have a pointer of type DBSCAN on which I call `Cluster` whenever I get a new measurement. This yields very unexpected clustering, however. When I instantiate a new DBSCAN object whenever I want to process a measurement, the clustering makes much more sense. Is there an

16:14 < jenkins-mlpack2> Project mlpack - git commit test build #84: UNSTABLE in 1 hr 2 min: http://ci.mlpack.org/job/mlpack%20-%20git%20commit%20test/84/

16:47 < rcurtin> zoq: nice workaround!

20:16 < KimSangYeon-DGU> Hi rcurtin! I have a question. :)

20:16 < KimSangYeon-DGU> about "Fix/Change Windows installer #1642"

20:19 < rcurtin> sure, go ahead

20:19 < KimSangYeon-DGU> .appveyor.yml that I wrote can extract git version from gitversion.hpp

20:20 < KimSangYeon-DGU> However, the git version is a string like "mlpack git-abcd120"

20:20 < rcurtin> right, that's what we should use as the version number

20:20 < KimSangYeon-DGU> To apply it to WiX, it should be 'x.x.x.x' format.

20:21 < KimSangYeon-DGU> Yes

20:22 < rcurtin> ugh, I see, we are required to do this with x.x.x.x format

20:22 < KimSangYeon-DGU> So, I don't know how to convert "mlpack git-abcd123" to 'x.x.x.x' format (x is integer)

20:22 < KimSangYeon-DGU> Yes Yes

20:23 < KimSangYeon-DGU> https://github.com/mlpack/mlpack/issues/1506#issuecomment-453413242

20:23 < rcurtin> I'm fine using just the x.x.x extracted from src/mlpack/core/util/version.hpp, but we should see if there is some other field where we can put the git revision

20:24 < rcurtin> so that it's clear to a user if they have installed an actual release or a git version

20:24 < KimSangYeon-DGU> Okay

20:25 < rcurtin> I'm not very familiar with WiX so I don't know what set of options are available

20:27 < rcurtin> maybe we can change the "Name" in this case or something from 'mlpack' to 'mlpack git-abcd123'

20:27 < KimSangYeon-DGU> I checked and The version of WiX can't use string.

20:27 < KimSangYeon-DGU> Ah~

20:27 < KimSangYeon-DGU> Okay!! I got it.

20:28 < rcurtin> sounds good---maybe there is something better than "Name", that was just the first idea I came up with :)

20:28 < rcurtin> I think you know I am not a Windows user, so I'm happy to defer to what you think is best here

20:29 < KimSangYeon-DGU> Okay. :)

20:34 < KimSangYeon-DGU> I'll check if there is something better than the idea. :)

20:50 < rcurtin> sounds good, thanks for your hard work :)

21:27 < ShikharJ> KimSangYeon-DGU: Thanks!

21:29 < KimSangYeon-DGU> It's my pleasure to work with you. :)