Kids identification shows as 95% but just due to baseball cap (see face 7 out of 995) not the same kids #30

Open
opened 2026-02-04 15:39:56 -05:00 by noam · 2 comments
Collaborator
No description provided.
Collaborator

Hi @noam ,

when identifying a person, try as much as possible to identify the faces that are frontal facing . with both eyes visible and open, with a mouth and nose.
It's hard for the face recognition when a face is in a profile, with eyes closed, ...
In Auto-Match , profile faces should be matched manually if they actually are a match.
The button Run Auto-Match shouldn't auto-match profile faces and low quality faces.

Hi @noam , when identifying a person, try as much as possible to identify the faces that are frontal facing . with both eyes visible and open, with a mouth and nose. It's hard for the face recognition when a face is in a profile, with eyes closed, ... In Auto-Match , profile faces should be matched manually if they actually are a match. The button Run Auto-Match shouldn't auto-match profile faces and low quality faces.
Author
Collaborator

i am a bit confuse about this message : "In Auto-Match , profile faces should be matched manually if they actually are a match.
The button Run Auto-Match shouldn't auto-match profile faces and low quality faces."

my concern is not about me understanding and working better with the system - i can realize that together with you. however, once we will start having users using it, we cant really tell them - do this or dont do that. does this make sense ? we need to have something which is either bullet proof, or something that can be easily fixed. i would rather to have less auto matches and than the user adding them manualy than the other way around that the user need to remove them from the automatch manual

i am a bit confuse about this message : "In Auto-Match , profile faces should be matched manually if they actually are a match. The button Run Auto-Match shouldn't auto-match profile faces and low quality faces." my concern is not about me understanding and working better with the system - i can realize that together with you. however, once we will start having users using it, we cant really tell them - do this or dont do that. does this make sense ? we need to have something which is either bullet proof, or something that can be easily fixed. i would rather to have less auto matches and than the user adding them manualy than the other way around that the user need to remove them from the automatch manual
Sign in to join this conversation.
No Label
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ilia/punimtag#30
No description provided.