| |||||||||||||
Fingerprint recognition using fprintFingerprint recognition using fprintPosted Nov 21, 2007 21:23 UTC (Wed) by socket (guest, #43)Parent article: Fingerprint recognition using fprint
Always good to see more open drivers. So, I'm curious: what's the false positive and false negatives is for these scanners, or the pattern recognition software? I've heard rumors that fingerprints aren't really as unique as once thought, and that two human experts can reasonably disagree on matches, but this is purely anecdotal to me. Anybody got resources on this?
(Log in to post comments)
Fingerprint recognition using fprint Posted Nov 22, 2007 18:39 UTC (Thu) by dsd (guest, #49212) [Link] I don't have any solid references here, but I'll describe some of my experiences using the software with my current range of fingers and thumbs using a few different fingerprint readers: For the sensors which produce big images (UareU 4000 and AES2501), I have not yet seen a false acceptance. You can get false rejections if you put effort into it -- rotating the finger quite significantly or whatever, but really once you have scanned a few fingers and picked up the technique it is unlikely that you will see false rejections on a frequent basis. For the sensors that produce small images (AES4000, AES1610 and UPEKTC), the false rejection rate is quite high. We need to tune the matching algorithms to perform better when comparing fingerprints with less feature points. I have not tested AES1610 or UPEKTC myself, but I did see my *first* false acceptance yesterday with AES4000. I probably have lowered the matching threshold a little too far. In all cases, the drivers will be improved to provide better images, and we should be able to improve upon the fingerprint processing/matching code too. For UPEKTS, the processing is done in hardware, and I have yet to see a false acceptance. False rejections are not common unless you did not scan your finger well during the enrollment process. This is useful because everything is done in hardware so we cannot tweak it :)
|
|||||||||||||