Algorithm Specifications

Each submitted algorithm must be a Win32 console application with the following list of parameters:

Synopsis:    [nameOfAlgorithm].exe [ndataset] [inputfile] [outputfile]

  • [nameOfAlgorithm].exe

It is the executable name. Format: Win32 console application (.exe)

  • [ndataset]

It is the identification number of the dataset to analyse.
Legend:

1=GreenBit
2=DigitalPersona
3=Orcanthus

  • [inputfile]

A text file with the list of absolute paths of each image to analyse. Each image is in the same format of own training-set.

Exemple of a [inputfile] called GreenBit_test.txt:

...
G:\Works\LivDet2017\Images\GreenBit\0123.png
G:\Works\LivDet2017\Images\GreenBit\1323.png
G:\Works\LivDet2017\Images\GreenBit\0033.png
G:\Works\LivDet2017\Images\GreenBit\0954.png
G:\Works\LivDet2017\Images\GreenBit\2154.png

...

  • [outputfile]

The text file with the output of each processed image, in the same order of inputfile. The output is a posterior probability of the live class given the image, or a degree of “liveness” normalized in the range 0 and 100 (100 is the maximum degree of liveness, 0 means that the image is fake).

Scores [0, 50) classify fingerprint image as "fake" while scores [50,100] classify fingerprint image as "live"

In the case that the algorithm has not been able to process the image, the correspondent output must be -1000 (failure to enroll).

Exemple of a [outputfile] called GreenBit_test_results.txt:

...
100
54
-1000
32
78
...

Each parameter related to the dataset configuration must be set before submission. Each user can configure his algorithm by the training-set available after registration deadline. Only Win32 console applications with the above characteristics will be accepted for the competition.

Participants may publish also the source code of their algorithm, but this is not mandatory.