[fprint] Call for testing: UPEK 147e:1001, AES1660, AES1610, AES2501, AES2550, AES2810, AES2660
Vasily Khoruzhick
anarsoul at gmail.com
Thu Feb 11 08:16:33 UTC 2016
- Previous message: [fprint] Call for testing: UPEK 147e:1001, AES1660, AES1610, AES2501, AES2550, AES2810, AES2660
- Next message: [fprint] Call for testing: UPEK 147e:1001, AES1660, AES1610, AES2501, AES2550, AES2810, AES2660
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
I lowered bz3_threshold for 147e:1001, please pull from my github repo
and try again.
On Wed, Feb 10, 2016 at 11:54 PM, Julian Sikorski <belegdol at gmail.com> wrote:
> I did, just to be sure. The enrollment seems to work fine.
>
> Julian
>
> W dniu 11.02.2016 o 08:52, Vasily Khoruzhick pisze:
>> Did you re-enroll your finger(s) with a fixed version?
>>
>> On Wed, Feb 10, 2016 at 11:39 PM, Julian Sikorski <belegdol at gmail.com> wrote:
>>> Hi Vasily,
>>>
>>> it is a bit hard to say as prior to the latest fixes the reader was not
>>> that usable. Having said that, my subjective feeling is that it is
>>> really hard to get a match now. Case in point: I tried this morning a
>>> bunch of times and got 14 mismatches, 1 match and 10 scan retry requests
>>> in between:
>>>
>>> [julas at snowball2 ~]$ fprintd-verify
>>> Using device /net/reactivated/Fprint/Device/0
>>> Listing enrolled fingers:
>>> - #0: right-index-finger
>>> Verify result: verify-retry-scan (not done)
>>> Verify result: verify-no-match (done)
>>> [julas at snowball2 ~]$ fprintd-verify
>>> Using device /net/reactivated/Fprint/Device/0
>>> Listing enrolled fingers:
>>> - #0: right-index-finger
>>> Verify result: verify-retry-scan (not done)
>>> Verify result: verify-no-match (done)
>>> [julas at snowball2 ~]$ fprintd-verify
>>> Using device /net/reactivated/Fprint/Device/0
>>> Listing enrolled fingers:
>>> - #0: right-index-finger
>>> Verify result: verify-retry-scan (not done)
>>> Verify result: verify-no-match (done)
>>> [julas at snowball2 ~]$ fprintd-verify
>>> Using device /net/reactivated/Fprint/Device/0
>>> Listing enrolled fingers:
>>> - #0: right-index-finger
>>> Verify result: verify-retry-scan (not done)
>>> Verify result: verify-no-match (done)
>>> ReleaseDevice failed: Message did not receive a reply (timeout by
>>> message bus)
>>> [julas at snowball2 ~]$ fprintd-verify
>>> Using device /net/reactivated/Fprint/Device/0
>>> Listing enrolled fingers:
>>> - #0: right-index-finger
>>> Verify result: verify-retry-scan (not done)
>>> Verify result: verify-no-match (done)
>>> ReleaseDevice failed: Message did not receive a reply (timeout by
>>> message bus)
>>> [julas at snowball2 ~]$ fprintd-verify
>>> Using device /net/reactivated/Fprint/Device/0
>>> Listing enrolled fingers:
>>> - #0: right-index-finger
>>> Verify result: verify-retry-scan (not done)
>>> Verify result: verify-no-match (done)
>>> [julas at snowball2 ~]$ fprintd-verify
>>> Using device /net/reactivated/Fprint/Device/0
>>> Listing enrolled fingers:
>>> - #0: right-index-finger
>>> Verify result: verify-retry-scan (not done)
>>> Verify result: verify-no-match (done)
>>> [julas at snowball2 ~]$ fprintd-verify
>>> Using device /net/reactivated/Fprint/Device/0
>>> Listing enrolled fingers:
>>> - #0: right-index-finger
>>> Verify result: verify-retry-scan (not done)
>>> Verify result: verify-no-match (done)
>>> ReleaseDevice failed: Message did not receive a reply (timeout by
>>> message bus)
>>> [julas at snowball2 ~]$ fprintd-verify
>>> Using device /net/reactivated/Fprint/Device/0
>>> Listing enrolled fingers:
>>> - #0: right-index-finger
>>> Verify result: verify-retry-scan (not done)
>>> Verify result: verify-no-match (done)
>>> [julas at snowball2 ~]$ fprintd-verify
>>> Using device /net/reactivated/Fprint/Device/0
>>> Listing enrolled fingers:
>>> - #0: right-index-finger
>>> Verify result: verify-no-match (done)
>>> [julas at snowball2 ~]$ fprintd-verify
>>> Using device /net/reactivated/Fprint/Device/0
>>> Listing enrolled fingers:
>>> - #0: right-index-finger
>>> Verify result: verify-no-match (done)
>>> [julas at snowball2 ~]$ fprintd-verify
>>> Using device /net/reactivated/Fprint/Device/0
>>> Listing enrolled fingers:
>>> - #0: right-index-finger
>>> Verify result: verify-no-match (done)
>>> [julas at snowball2 ~]$ fprintd-verify
>>> Using device /net/reactivated/Fprint/Device/0
>>> Listing enrolled fingers:
>>> - #0: right-index-finger
>>> Verify result: verify-no-match (done)
>>> [julas at snowball2 ~]$ fprintd-verify
>>> Using device /net/reactivated/Fprint/Device/0
>>> Listing enrolled fingers:
>>> - #0: right-index-finger
>>> Verify result: verify-retry-scan (not done)
>>> Verify result: verify-no-match (done)
>>> [julas at snowball2 ~]$ fprintd-verify
>>> Using device /net/reactivated/Fprint/Device/0
>>> Listing enrolled fingers:
>>> - #0: right-index-finger
>>> Verify result: verify-match (done)
>>>
>>> I will try to experiment over the weekend and report back
>>>
>>> Best regards,
>>> Julian
>>>
>>> W dniu 10.02.2016 o 23:58, Vasily Khoruzhick pisze:
>>>> Hm, so fixed version has a worse match rate? Could you please play
>>>> with FINGER_REMOVED_THRESHOLD and DIFF_THRESHOLD values in
>>>> libfprint/drivers/upeksonly.c?
>>>> Try 200-400 for FINGER_REMOVED_THRESHOLD and 5-10 for DIFF_THRESHOLD
>>>>
>>>
>
- Previous message: [fprint] Call for testing: UPEK 147e:1001, AES1660, AES1610, AES2501, AES2550, AES2810, AES2660
- Next message: [fprint] Call for testing: UPEK 147e:1001, AES1660, AES1610, AES2501, AES2550, AES2810, AES2660
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the fprint
mailing list