15:24 < travis-ci> mlpack/mlpack#1486 (master - 42ddcbb : Ryan Curtin): The build was fixed.

15:24 < travis-ci> Change view : https://github.com/mlpack/mlpack/compare/bd6a79a2cb74...42ddcbb292f8

15:24 < travis-ci> Build details : https://travis-ci.org/mlpack/mlpack/builds/155360652

15:31 < travis-ci> mlpack/mlpack#1487 (master - 5617fbc : Ryan Curtin): The build is still failing.

15:31 < travis-ci> Change view : https://github.com/mlpack/mlpack/compare/42ddcbb292f8...5617fbc885c2

15:31 < travis-ci> Build details : https://travis-ci.org/mlpack/mlpack/builds/155361293

15:43 < rcurtin> jenkins-mlpack: hello, are you alive?

15:43 < jenkins-mlpack> rcurtin did you mean me? Unknown command 'hello,'

15:43 < jenkins-mlpack> Use '!jenkins help' to get help!

15:43 < rcurtin> sweet

15:43 < rcurtin> !jenkins help

15:44 < rcurtin> jenkins-mlpack: !jenkins help

15:44 < jenkins-mlpack> rcurtin did you mean me? Unknown command '!jenkins'

15:44 < jenkins-mlpack> Use '!jenkins help' to get help!

15:44 < rcurtin> jenkins-mlpack: status

15:45 < jenkins-mlpack> Project mlpack - git commit test build #2506: ABORTED in 4 min 43 sec: http://masterblaster.mlpack.org/job/mlpack%20-%20git%20commit%20test/2506/

15:45 < jenkins-mlpack> Starting build #2507 for job mlpack - git commit test (previous build: ABORTED -- last SUCCESS #2505 57 min ago)

15:46 < rcurtin> ok, well, if it's only able to do notifications because I don't seem to have permissions set up right, that's good enough for me

15:49 < zoq> jenkins-mlpack: !help

15:49 < jenkins-mlpack> zoq did you mean me? Unknown command '!help'

15:49 < jenkins-mlpack> Use '!jenkins help' to get help!

15:49 < zoq> hm

15:49 < zoq> jenkins-mlpack: help

15:50 < zoq> jenkins-mlpack: health

15:50 < rcurtin> yeah, I checked the logs, when you submit a command, it seems to want to check if you are a valid Jenkins user

15:50 < rcurtin> and since we're not using the same usernames as jenkins here, I think it fails

15:51 < zoq> ah

15:51 < marcus> jenkins-mlpack: health

15:51 < rcurtin> I tried to do that but the nick 'ryan' was taken :)

15:52 < zoq> ah right

15:52 < rcurtin> WARNING: org.acegisecurity.userdetails.UsernameNotFoundException: No such Unix user:

15:52 < rcurtin> I need to restart jenkins, hang on...

15:53 < rcurtin> hm, something is wrong, but I gotta get lunch, back later

15:53 < zoq> okaye, have fun

18:31 < rcurtin> pantsforbirds: in response to your question from a few days ago, yes, one file for definitions and one file for implementation :)

18:32 < pantsforbirds> rcurtin: awesome! i'm really excited to contribute to an open source project

18:32 < rcurtin> :)

18:33 < rcurtin> when you submit a PR, we can go over it and get it merged

18:33 < rcurtin> but be aware, sometimes that process can take a little while and a few revisions :)

18:34 < pantsforbirds> yeah im still reading through the code base trying to make sure i follow the same coding style as you guys

18:34 < rcurtin> there's a wiki page with some more information, have you seen it? let me find a link

18:35 < rcurtin> https://github.com/mlpack/mlpack/wiki/DesignGuidelines

18:35 < rcurtin> the actual style guidelines start about halfway down, but hopefully the whole document is useful

18:40 < pantsforbirds> right i've been reading through it. figured the more i do correctly before the pr the easier it would be on everyoen

18:40 < pantsforbirds> everyone*

18:46 < rcurtin> true, thank you for doing that :)

20:12 < pantsforbirds> rcurtin: what kind of optimizers would you guys be interested in? are you looking for mostly hill climbing methods, or would you be interested in some different heuristic algorithms as well?

20:13 < pantsforbirds> and would root finding algorithms be of interest as well? and if so would i add them to the core/math or core/optimizers?

20:15 < rcurtin> really any optimizer can be useful, and it would be best to put them in core/optimizers

20:15 < rcurtin> if you implement something, we can easily test it with the various machine learning algorithms that we have

20:16 < rcurtin> and see how well it performs

20:19 < pantsforbirds> that actually sounds pretty fun

20:20 < jenkins-mlpack> Project mlpack - nightly matrix build build #1090: STILL FAILING in 2 hr 11 min: http://masterblaster.mlpack.org/job/mlpack%20-%20nightly%20matrix%20build/1090/

21:01 < jenkins-mlpack> Starting build #47 for job mlpack_coverage (previous build: STILL FAILING)

21:01 < jenkins-mlpack> Project mlpack_coverage build #47: STILL FAILING in 15 sec: http://masterblaster.mlpack.org/job/mlpack_coverage/47/