Dlib VS Qt

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.

Qt mono repo : .. you could check out all submodules and simply use CMake to exactly achieve this. A mono repo also means that if I only use qtbase and declarative, I would need to have all submodules in there? - No

For e.g. if you’re writing a framework, you need to interface with Cocoa on MacOS to draw windows, which only provides an Objective C or Swift interface. You can look at the Qt source code and see how they do it: https://github.com/qt/qtbase/tree/067b53864112c084587fa9a507eb4bde3d50a6e1/src/plugins/platforms/cocoa

That's because Qt 6 wholeheartedly converted to CMake for you. (At least it is better than qmake.) In order to support this Qt has this large battery of CMake files [1]. Qt is of course a clear outlier, but you can't expect the same level of support from every other library you want. My points about "anything exotic" still stand.

[1] https://github.com/qt/qtbase/tree/dev/cmake

What are you talking about? Qt has GTK theme support built-in: https://github.com/qt/qtbase/tree/dev/src/plugins/platformthemes/gtk3

This looks like the Qt bug solved by this commit: https://github.com/qt/qtbase/commit/acaabc9108dfe75530960cf8e3ec4f3602cd82e0

Yeah, I'm sure it's completely unheard of. Oh except that it took me all of a couple minutes to find an example of that exact thing in one of the largest, most commonly used C++ frameworks out there.

I don't see any connect in https://github.com/qt/qtbase/blob/dev/src/corelib/tools/qsharedpointer_impl.h, and QPointer isn't a QObject (though I don't know if the latter is actually necessary for signal-slots). One (unreliable) way to test is to see if a QPointer fails to be nulled out when the QObject is blocked by a QSignalBlocker. Alternatively I'd set a data breakpoint on a QPointer and try it out. But I don't have the time right now.