Dlib VS SHOGUN

dlib

The apparent gender estimates from photos are using dlib, and I really ought to get what I'm doing cleaned up in such a way that other people can use it easily.

I really like dlib's code https://github.com/davisking/dlib

Additionally, C++ may be used for extremely high levels of optimization even for cloud-based ML. Dlib and Kaldi are C++ libraries used as dependencies in Python codebases for computer vision and audio processing, for example. So if your application requires you to customize any functions similar to those libraries, then you'll need C++ knowhow.

If you know C++, you don't need anything else. Go and learn APIs for C++ libraries. If you're into DSP, why not study Dlib?.

The data is mostly in this spreadsheet. The apparently facial gender estimates are made with Dlib. The mental health assessments are from Beck's Depression Inventory and the Snaith-Hamilton Pleasure Scale. The graph is made with gnuplot.

The plugin uses dlib library with a very fast HOG detector for both face recognition and detector following the relative examples.

The dlib facial recognition model thinks that I am now a distance of about 0.3 from where I started, which is far enough to start getting many false positive matches, but still within the design intent that different pictures of the same individual will be within 0.6 of each other.

Dlib's face recognition module thinks that I am about 0.25 units away from where I started; its design intent is that distinct individuals will be 0.6 or more apart, although in practice other people start showing up around 0.3.

The function is trying to get the median, which is not defined for an empty set. With this particular implementation, there is an assert for that:

https://github.com/shogun-toolbox/shogun/blob/9b8d85/src/sho...

Unrelatedly, but from the same section:

> Fixes are trivial, access the nth element only after the call being made. Be careful.

Wouldn't the proper fix to do the nth_element for the larget element first (for those cases that don't do that already) and then adjust the end to be the begin + larger_n for the second nth_element call? Otherwise the second call will check [begin + larger_n, end) again for no reason at all.