generating .npy files

[TahirJanjua]

I have been working with this code repository very recently after going through the paper "Learning features for offline handwritten signature verification using deep convolutional neural networks by Luiz G. Hafemann, Robert Sabourin ,LuizS.Oliveira". The problem I am facing is that how can I generate .npy files placed in the data/ directory of this project, so that we might verify any other user defined signature image other than "some_signature.png". The aim behind asking is that a user defined image can be used for signature verification since the code "example.py" actually compared the .npy files at the time of testing.
My question might sound as I am new to this field.
Thanking you in anticipation.
Best Regards
Tahir

[luizgh]

Hello Tahir. In this repository we released the code / trained models for extracting features for signatures, and not the code for performing classification. In the example.py, the comparison to the .npy files is just to make sure that the results you obtain is the same as the results I obtained. It is not classifying the signature of the user.

For actual classification, the simplest approach is computing the distance (in feature space) between a query signature and a reference. This is easy to implement (see the jupyter notebook example), but not very powerful. Most commonly, people train "Writer-dependent classifiers" (one binary classifier for each user). You may find it useful to read more about this topic in these papers:

https://arxiv.org/abs/1507.07909
https://arxiv.org/abs/1705.05787

[TahirJanjua]

Thank you so much for your guidance . I shall be following the links you send and implementing what you suggested .I have found your repository very helpful.  Best RegardsTahir  Sent from Yahoo Mail on Android On Tue, 8 Jan 2019 at 11:39 pm, Luiz Gustavo Hafemann<notifications@github.com> wrote: Hello Tahir. In this repository we released the code / trained models for extracting features for signatures, and not the code for performing classification. In the example.py, the comparison to the .npy files is just to make sure that the results you obtain is the same as the results I obtained. It is not classifying the signature of the user. For actual classification, the simplest approach is computing the distance (in feature space) between a query signature and a reference. This is easy to implement (see the jupyter notebook example), but not very powerful. Most commonly, people train "Writer-dependent classifiers" (one binary classifier for each user). You may find it useful to read more about this topic in these papers: https://arxiv.org/abs/1507.07909 https://arxiv.org/abs/1705.05787 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.