After rescan with "force update" I have a lot of unconfirmed faces in the database so I look for persons with unconfirmed faces in People view and use Face Manager to confirm or reject faces. That would be very efficient way of dealing with unconfirmed faces however I noticed that very often the faces I confirm or reject keeps reappearing after saving changes in Face Manager.
I am attaching debug log from session where I:
- Started IMatch
- Went to People view and choose a person with many unconfirmed faces
- Set the filter to hide versions and to exclude photos not in the "finished" category where I put photos with all faces assigned and confirmed
- Started Face Manager and displayed unconfirmed faces
- Made sure the Face Manager is set to only work on files in the current scope
- Confirmed two faces belonging to files n1998-018-05.jpg and n2005--025-29.jpg
- Saved the changes in Face Manager and waited for IMatch to process the changes
- Closed and reopened Face Manager only to find both faces are still in unconfirmed state
Same happens if I reject faces - often I reject a lot of faces only to find that most of them reappear in Face Manager again.
I have seen something similar. Try running iMatch Diagnostics and see if they correct/change the face data.
https://www.photools.com/community/index.php?topic=10299.0
Also check the rejected and trained faces for the persons involved.
Rejecting or training too much may reduce the performance of the AI.
I understand that training too much can affect performance however how can I avoid rejecting too much? Shouldn't I reject all unconfirmed faces I see in Face Manager that don't belong to a given person?
Rejecting a person assignment means: "Not this person". This is to be used sparingly.
Usually you assign the correct person (if known) or if you are not interested in the face, you either set it to ignore or just delete the unneeded face annotation.