Page History

...

• In each of the two images (live face and ID image), there should be only one face, clearly visible.

  • If that is not the case, e.g. if there is no face or there are two or more faces, you can use visage|SDK to detect this and report an error.

  • The ID image should be cropped so that the ID is occupying most of the image.

• visage|SDK face tracking API will be used to detect the face in each image.

• visage|SDK face recognition API will then be used to generate a numerical descriptor for each of the two faces, to compare the two numerical descriptors to each other and return a measure of their similarity.

• the face first need to be located:

  • To locate the face, you can use detection (for a single image) or tracking (for a series of images from a camera feed).

    • See function VisageSDK::VisageTracker::track() or VisageFeaturesDetector::detectFacialFeatures().

  • Each of these functions returns the number of faces in the image - if there is not exactly one face you may report an error or take other action.

  • Furthermore, these functions return the FaceData structure, containing the face location.

  • Note: the ID image should be cropped so that the ID is occupying most of the image (if the face on the ID is too small relative to the whole image it might not be detected).

• The next step is to extract a face descriptor from each image. The descriptor is an array of short integers that describes the face - similar faces will have similar descriptors.

  • From the previous step you have one FaceData structure for the ID image and one FaceData structure for the live image.

  • Pass each image with its corresponding FaceData to the function VisageFaceRecognition::extractDescriptor().

• Pass the two descriptors to the function VisageFaceRecognition::descriptorsSimilarity() to compare the two descriptors to each other and obtain the measure of their similarity. This is a float value between 0 (no similarity) and 1 (perfect similarity).

• If the similarity is greater than a chosen threshold, consider that the live face matches the ID face.

  • By choosing the threshold, you control the trade-off between False Positives and False Negatives:

    • If the threshold is very high, there will be virtually no False Positives, i.e. the system will never declare a correct match when in reality the live person is not the person in the ID.

    • However, with a very high threshold a False Negative may happen more often - not matching a person who really is the same as in the ID, resulting in an alert that will need to be handled in an appropriate way (probably requiring human intervention).

    • Conversely, with a very low threshold, such “false alert” will virtually never be raised, but the system may then fail to detect True Negatives - the cases when the live person really does not match the ID.

    • There is no “correct” threshold, because it depends on the priority of a specific application. If the priority is to avoid false alerts, threshold may be lower; if the priority is to avoid undetected non-matches then the threshold should be higher

  visage|SDK provides functions to do all the above steps, but you need to use these functions to program the integrated application

  • • .

...