[Digikam-devel] libkface

[Gilles Caulier]

Can you run Recognize tool into valgrind to see if memory leak is detected ?

Do you use last code from libkface that is review a lots recently,
which use revision number 3.1.0 ?

best

Gilles caulier

2014-06-23 1:00 GMT+02:00 Tobias Leupold <tobias.leupold at web.de>:
> The face detection part I added to the KPA code can be found on
> https://github.com/l3u/kphotoalbum/commit/04f6a995237d21990e25d282c78f15abab6d3106
> But this was no problem and was "simply working".
>
> The problems I had -- the exponential processing time growth and the massive
> HD usage -- appeared when I used the "recognize.cpp" program from the libkface
> sources (located in "test/"). I simply did some "./recognize train Name
> image.jpg", and, as said, I got massive performance problems with more than
> about 10 training images (each time, only the face part of the image was used,
> as detected by the routine from my above code, that does the same thing as the
> "recognize.cpp" program from "test/").
>
> So I didn't write recognition code yet ...
>
> Tobias
>
>> There are no more docs than the API docs in the header files. Recognition is
>> a moving target, we have some bugs in digikam here as well.
>>
>> But even if we are unsure about the quality of recognition that is currently
>> available, there's certainly some easier problem, learning is usually
>> pretty fast and, IIRC, of  O(1) complexity.
>>
>> Is your code in git somewhere?
>>
>> Marcel
>
> _______________________________________________
> Digikam-devel mailing list
> Digikam-devel at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-devel