We are using sourceAFIS for fingerprint matching/verification. Our prospective customer want fingerprint matching score in percentage format. AFAIK for sourceAFIS, verification score can be from 0 to infinity. Please suggest if there is any way to convert score value to percentage.
Suppose, we have to perform 1:1 verification in batch mode. So, there will be 1000 1:1 matching for a batch of 1000 fingerprints. We are employing parallel/multi threading technique to lessen the total verification time, also fingerprints are stored in RAM. We have observed that in 1 second we are able to verify 30 fingerpritns only. PC configuration: Intel Core i5 3.2 GHz, 4 GB RAM, 200 GB HDD. Do you think the performance figure is ok?
We have to scan inked fingerprint from paper, to verify it against registered fingerprints. We are getting very low matching score (around 30-45). Please suggest some technique (if any) to get moderate/high matching score.
Regards
Tanim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert,
We are using sourceAFIS for fingerprint matching/verification. Our prospective customer want fingerprint matching score in percentage format. AFAIK for sourceAFIS, verification score can be from 0 to infinity. Please suggest if there is any way to convert score value to percentage.
Suppose, we have to perform 1:1 verification in batch mode. So, there will be 1000 1:1 matching for a batch of 1000 fingerprints. We are employing parallel/multi threading technique to lessen the total verification time, also fingerprints are stored in RAM. We have observed that in 1 second we are able to verify 30 fingerpritns only. PC configuration: Intel Core i5 3.2 GHz, 4 GB RAM, 200 GB HDD. Do you think the performance figure is ok?
We have to scan inked fingerprint from paper, to verify it against registered fingerprints. We are getting very low matching score (around 30-45). Please suggest some technique (if any) to get moderate/high matching score.
Regards
Tanim
This is not supported by SourceAFIS. You could hack database analyzer to do that, but it's non-trivial.
SourceAFIS wasn't designed for such use case. There's considerable overhead in setting up matching.
SourceAFIS doesn't handle ink scans very well. It would take some work to make it able to do that.