preparing 6.0.0 code...

Sat Jan 6 16:53:30 GMT 2018

The main integration and improvements of new face recognition algorithms in
6.0.0 branch is now complete and ready to use.

The default algorithm is DNN (deep neural network => deep learning => IA).

In face scan dialog, in advanced tab, we have a new option where
recognition algorithm can be selected.

- lpbh : older one present on 5.x based on OpenCV (
https://docs.opencv.org/2.4/modules/contrib/doc/facerec/facerec_tutorial.html#local-binary-patterns-histograms
)
- fisherfaces : OpenCV based (
https://docs.opencv.org/2.4/modules/contrib/doc/facerec/facerec_tutorial.html#fisherfaces
)
- eigenfaces : OpenCV based (
https://docs.opencv.org/2.4/modules/contrib/doc/facerec/facerec_tutorial.html#eigenfaces
)
- dnn : dlib based (
http://blog.dlib.net/2017/02/high-quality-face-recognition-with-deep.html)

I'm not yet satisfied by DNN. I'm not started to compare the algorithm with
a clean database. In all cases, we must detect all faces, not tagged. After
that, we need to train the faces with names, else the recognition will not
work. As i know, at least with lpbh algorithm, we need at least 6 images
tagged with same name to see a recognition result while scanning. To have a
clean compare result, for each algorithm to use, we need a clear database.

The student working on this project while summer 2017 report to me that in
all cases the best algorithms are :

1 DNN.
2 eigenfaces.
3 fisherfaces.
4 lpbh.

The goal is to use the best one at end.

Gilles Caulier

2018-01-04 13:18 GMT+01:00 Gilles Caulier <caulier.gilles at gmail.com>:

> The 6.0.0 git branch is created in remote :
>
> [gilles at localhost digikam.master]$ git branch -a
> * master
>   remotes/origin/HEAD -> origin/master
>   remotes/origin/development/0.10
>   remotes/origin/development/0.8
>   remotes/origin/development/0.8.x
>   remotes/origin/development/0.9.x
>   remotes/origin/development/1.2
>   remotes/origin/development/1.3
>   remotes/origin/development/3.0.0
>   remotes/origin/development/6.0.0           <
> =============================
>   remotes/origin/development/balooport
>   remotes/origin/development/bug309058
>   remotes/origin/development/cmakecleanup
>   remotes/origin/development/externaltools
>   remotes/origin/development/frameworks
>   remotes/origin/development/garbagecollection
>   remotes/origin/development/hupnp
>   remotes/origin/development/imagemetadatacache
>   remotes/origin/development/kde3
>   remotes/origin/development/photolayoutseditor
>   remotes/origin/development/sql2.0
>   remotes/origin/development/usbimport
>   remotes/origin/gsoc11-clone
>   remotes/origin/gsoc11-presentation
>   remotes/origin/gsoc13-editorcanvas
>   remotes/origin/gsoc13-imgqsort
>   remotes/origin/gsoc13-localadj
>   remotes/origin/gsoc13-tagmngr
>   remotes/origin/gsoc13-thumbbar-mv
>   remotes/origin/gsoc13-videow
>   remotes/origin/gsoc14-greyc
>   remotes/origin/gsoc14-kipibqm
>   remotes/origin/gsoc14-qaccess
>   remotes/origin/gsoc15-advmetadata
>   remotes/origin/gsoc15-kio-drop
>   remotes/origin/gsoc16-mysql
>   remotes/origin/gsoc16-red-eye
>   remotes/origin/gsoc17-db-sep
>   remotes/origin/gsoc17-dlna
>   remotes/origin/gsoc17-face-mngmnt
>   remotes/origin/gsoc17-healing
>   remotes/origin/master
>
> This one is based on gsoc17-face-mngmnt sync with master today morning.
>
> The remotes/origin/development/6.0.0 must be used to put next 6.0.0 new
> code and must be sync with master until 5.x serie will be completed.
>
> Best
>
> Gilles Caulier
>
> 2018-01-04 12:24 GMT+01:00 Gilles Caulier <caulier.gilles at gmail.com>:
>
>> The branch gsoc17-face-mngmnt is now sync with master and compile and
>> link properly.
>>
>> I will create a new 6.0.0 branch based on the gsoc17-face-mngmnt branch
>> for future main development.
>>
>> Gilles Caulier
>>
>> 2018-01-03 19:57 GMT+01:00 Maik Qualmann <metzpinguin at gmail.com>:
>>
>>> Gilles, and everyone else a Happy New Year. Yes, I'm looking forward to
>>> feedback on MySQL - but only positive. ((:-)) No, seriously, I know that
>>> there
>>> will be problems. Currently I only use MySQL for testing and it is
>>> running
>>> really well here. It is important that we write in the release note that
>>> the
>>> core DB with the migration tool should be copied into a new DB and
>>> should be
>>> started with a new created thumbnail and face DB.
>>>
>>> Maik
>>>
>>> Am Mittwoch, 3. Januar 2018, 18:10:50 CET schrieb Gilles Caulier:
>>> > Hi all,
>>> >
>>> > In first, i hope an happy new year to all.
>>> >
>>> > 1/ I currently revival the face management git branch written while
>>> summer
>>> > 2017 by the student working on AI engine to recognize faces. The code
>>> is
>>> > sync with master, but do not compile yet. I will fix it.
>>> >
>>> > 2/ Important point : this code do not compile with OpenCV 2.x. It
>>> require
>>> > OpenCV 3.1. This want mean that digiKam 6.0.0 will drop OpenCV 2.x
>>> support
>>> > definitively.
>>> >
>>> > 3/ when faces management branch will be fixed, I would to create a new
>>> one
>>> > dedicated to 6.0.0 release and let's master for the 5.x series, as
>>> > certainly a new 5.9.0 will be published few weeks ago 5.8.0, as
>>> > maintenance, until 6.0.0 code will be stabilized.
>>> >
>>> > 4/ The clone tool : this one still not very unusable for 5.8.0. I
>>> recommend
>>> > to disable this option in editor for the moment, until zoom support and
>>> > brushes size preview over canvas is not implemented.
>>> >
>>> > 5/ I do know yet when 5.8.0 will be released, as i don't receive a new
>>> > response from Nicolas to create the whole tarball. Also Maik, want
>>> > certainly receive more feedback about Mysql support as i can see
>>> recently
>>> > in bugzilla.
>>> >
>>> > Best
>>> >
>>> > Gilles Caulier
>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20180106/0d249ed4/attachment.html>