nextcloud / nextcloud/recognize
Manually/automatically re-run clustering on rejected faces
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 699
- Forks
- 68
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 5
Description
Describe the feature you'd like to request
Last year, I added a few thousand photos to Memories over a few days. Recognize eventually churned through most of them and did a pretty good job of recognizing faces and tagging people. However, just a few weeks ago, I discovered the Unassigned faces page and there are so many photos and faces that remain unassigned. I spent a couple of hours assigning faces to ones that Recognize had already clustered together (most of which had a name assigned to them). I then assumed that Recognize would incrementally re-run clustering on rejected faces given the new information I provided by manually assigning a few. However, this does not seem to be the case.
Describe the solution you'd like
I would like a way to have Recognize re-run clustering on rejected faces given new stimuli (such as some rejected faces being manually assigned by the user). This would help me cut down on the number of unassigned faces I have.
I did come across https://github.com/nextcloud/recognize/issues/951 which says that clustering does grab a portion of rejected faces during the clustering of new faces. However, if I am not actively adding new photos, then this does not occur.
Describe alternatives you've considered
I've tried manually running clustering using occ but, as mentioned above, this will only work with new photos that have not yet been clustered. I'm hoping for a way to make the manual assignment of faces a new stimulus for attempting to cluster previously rejected faces.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how clustering is invoked through occ and compare the current behavior with issue #951. Trace how manually assigned faces become new clustering input, then define done as a way to re-run clustering on previously rejected faces without requiring new photos.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- machine-learning, php
- Domain
- backend, machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100