Dunsin O

I am using NetBeans IDE for development. After I cloned the project from bitcucket and imported the project I noticed it had to download some dependencies at first build. At the moment the matching algorithm works fine but I'm concerned about the total time it takes to execute - I observe an average run time of 6-7 secs for 1:1 matching. Below is my code: /* * To change this license header, choose License Headers in Project Properties. * To change this template file, choose Tools | Templates * and...

ok thanks

" SourceAFIS can match single probe against a database of candidates at the speed of 16,000 fingerprints per second per core on decent processor according to my tests." Wow. what I did was clone the project from Bitbucket, import as a project to NetBeans and write a Java APP with a main class. See my code: /* * To change this license header, choose License Headers in Project Properties. * To change this template file, choose Tools | Templates * and open the template in the editor. */ package com.machinezoo.sourceafis;...

But then one more thing, you talked about wait time. I observe (using Netbeans) an average run time of 6-7 secs for 1:1 matching

Great suggestion there @robert-vazan I think this is what I'd do. I store just A SINGLE impression as you explained here - "If you want to keep the 3 views, perhaps you should only check the 2nd and 3rd view only if the first view matches with some minimum score (maybe 10+). " But I would ensure I capture 2 or 3 times and ensure a good similarity score before saving just one. Thus matching would be way faster

"Why are you collecting 3 impressions of each finger? Is the sensor small? If so, can you use a sensor that is large enough? If some of the impressions are of lower quality, it is better to enroll the best one instead of enrolling and matching all three." Hmm.. good question. Well I got this concept from the type of enrollment used by Digital Persona 4500 SDK - they capture up to 3 or 4 times I guess to ensure different possible positions,angles, and finger placements matches "Do you know the finger...

"Why are you collecting 3 impressions of each finger? Is the sensor small? If so, can you use a sensor that is large enough? If some of the impressions are of lower quality, it is better to enroll the best one instead of enrolling and matching all three." Hmm.. good question. Well I got this concept from the type of enrollment used by Digital Persona 4500 SDK - they capture up to 3 or 4 times I guess to ensure different possible positons,angles, and finger placements matches "Do you know the finger...

The SourceAFIS projects is a very great library to start with on Fingerprint Recognition. I have implemented (using java) the 1:1 matching and it works fine. Nonetheless, a use case came up - capturing up to 3 images of per finger for three fingers - thumb, index and middle finger for both hands. So this implies that when I’m performing a match test for a particular user, I’m verifying the probe image against 3 fingerprint images * (3 fingers * 2 hands) which is a total of18 candidate fingerprint...