-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add a way for user to judge: "This is not a person" #1124
Comments
Hello 👋 Thank you for taking the time to open this issue with recognize. I know it's frustrating when software I look forward to working with you on this issue |
Mmh, I see your point. A "not a person" category may be in order. |
I have several situations like this:
|
Elaborating on @epoxi's last bullet point, there are many photos in my "unrecognized faces" roll in the wonderful "Memories" app which are simply irrelevant: e.g. some guy in the background of the photo I took of my lovely wife as we enjoyed our vacation in Paris. I will never need to tag that person, and would prefer to archive the recognition so that it doesn't show up in "unrecognized faces", which I treat as my "queue of photos to categorize". To be clear, I'm talking about a case where an actual human face was positively detected, however, the user has decided that for whatever reason it's not relevant to categorize that detected face. |
Describe the feature you'd like to request
I have a lot of faces in the unclustered (NULL) area. Sometimes, some of them get readded to existing clusters, or new shit-clusters are created with them. Often, these are just random faces of passersby in the background or even none-faces.
Here are some examples.
It's totally acceptable for me that the face recognition is not perfect, but I would like to be able to fix the errors manually. And once fixed they should stay fixed.
Describe the solution you'd like
I would like to remove misdetections completely, so I don't have to worry about them being re-clustered.
Describe alternatives you've considered
Adding all NULL faces to an "Unknown" (shit-)cluster. However, this could cause a problem that newly detected faces might get added to this cluster, too.
The text was updated successfully, but these errors were encountered: