Replies: 2 comments 2 replies
This is a good sign. 0 queued files means everything that should have been processed was processed. 0 Scheduled background jobs means, nothing is currently scheduled to be done. Also good, since there is nothing queued to be processed.
This is a bit unfortunate as it seems you have too few face photos for clustering to kick in -- unless you have a lot of clustered faces already? |
|
Hi! Thanks for your reply. Unfortunately, it seems that any pictures I added since I installed recognize have not yet been processed. I can see that, since a) they're not showing up in the existing people categories and b) they're not showing up as "unassigned faces". How could that be? |
Uh oh!
There was an error while loading. Please reload this page.
Hi. I'm running recognize on my docker installation of nextcloud using docker-compose. The compose file also launches a dedicated cron image that runs the same nextcloud image as the "app", as suggested by the docker-compose yaml in nextcloud docker (https://github.com/nextcloud/docker/blob/master/.examples/docker-compose/with-nginx-proxy/mariadb/fpm/docker-compose.yml).
My understanding was the this cronjob takes care of launching all scheduled jobs. I couldn't find anywhere in the recognize settings to set these background jobs up, so I was under the impression this takes place under the hood. Now, I'm not seeing any background jobs scheduled for recognize after I installed it. In fact, I have the following message shown in the admin settings for recognize:
FYI I have added several more images to classify and cluster since I ran the initial detection. I did the initial setup by running the commands from my "app" container, because I wanted to do "factory reset":
occ recognize:clear-background-jobs
occ recognize:reset-face-clusters
occ recognize:reset-faces
occ recognize:classify
occ recognize:cluster-faces
Thanks for the app btw, I'm very happy to use it!
All reactions