Matias De lellis
Matias De lellis
Hi @escoand > OK, and what do you think of the other way around? Saving the XMP data to the files? As I told you in another issue, I guess...
Yeah .. I saw it and thought exactly the same. :grimacing: Maybe next week I will try it, and take ideas .. :wink:
Hi @escoand Thank you for the link. I had read it like so many others. :joy: This particular article makes a very good comparison between detectors. It may seem that...
Ok.. It was hard to find them, but the workflow is this.. :sweat_smile: 1. Go tho the `persons` tab 2. Click on `Scan the collection looking for faces` button. ...
p.s.: Do not analyze the database or the tools used yet.
Hi @escoand > One extra point: digiKam creates EXIF/XMP tags and keywords. This could be search for by any software and would be a nice solution additional to the information...
Hi @stalker314314 I was playing with this (using foreach(), count() outside of for(), array_push(), array_merge(), references), but I not found great improvements.. :disappointed: I only found one small detail... https://github.com/matiasdelellis/facerecognition/blob/71c8238ba534e572fa9c26942078cab0ba9b2660/lib/BackgroundJob/Tasks/CreateClustersTask.php#L210...
I seen it, but since use pre-increment (++i) there, I thought it worked like this... which is incorrect.. :disappointed: I think I remember that before, the behavior of the for()...
Well... 73% of the time, it is due to the calculation of the Euclidean distance.  To analyze it yourself: * https://mike42.me/blog/2018-06-how-i-made-my-php-code-run-100-times-faster We can add another table where keep the...
> https://github.com/davisking/dlib/blob/ae406bf4c119c3f6bfc8992a6bbf54d4f579fad5/tools/python/src/face_recognition.cpp#L252 Wow, Soooo easy.. :sweat_smile: > Now, if that doesn't put us below 5 mins ballpark for ~20000 images...let's "cache":) > This DB would have 400M rows for 20.000...