I have played with the identify/verify, makes sense what you guys said. My concern now is, it limits me to doing identification and verification within the GT-511C3, which was how it was designed.
Filling the sensor DB with stored template might be cumbersome (it is likely I would have templates that run into hundreds).
My thought now is to know the algorithm that was used by the device to do verifiy/identify so it can also be done outside the device (say, in a remote server).
Or come up with another algorithm that might do that.
In both cases, is it feasible? and is it something we - all of us (: could attempt?
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
I have played with the identify/verify, makes sense what you guys said. My concern now is, it limits me to doing identification and verification within the GT-511C3, which was how it was designed.
Filling the sensor DB with stored template might be cumbersome (it is likely I would have templates that run into hundreds).
My thought now is to know the algorithm that was used by the device to do verifiy/identify so it can also be done outside the device (say, in a remote server).
Or come up with another algorithm that might do that.
In both cases, is it feasible? and is it something we - all of us (: could attempt?