Commit 3558cd46 authored by Philip ABBET's avatar Philip ABBET

Add putvein/3

parent f1b34bab
This diff is collapsed.
This diff is collapsed.
.. Copyright (c) 2016 Idiap Research Institute, http://www.idiap.ch/ ..
.. Contact: beat.support@idiap.ch ..
.. ..
.. This file is part of the beat.examples module of the BEAT platform. ..
.. ..
.. Commercial License Usage ..
.. Licensees holding valid commercial BEAT licenses may use this file in ..
.. accordance with the terms contained in a written agreement between you ..
.. and Idiap. For further information contact tto@idiap.ch ..
.. ..
.. Alternatively, this file may be used under the terms of the GNU Affero ..
.. Public License version 3 as published by the Free Software and appearing ..
.. in the file LICENSE.AGPL included in the packaging of this file. ..
.. The BEAT platform is distributed in the hope that it will be useful, but ..
.. WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY ..
.. or FITNESS FOR A PARTICULAR PURPOSE. ..
.. ..
.. You should have received a copy of the GNU Affero Public License along ..
.. with the BEAT platform. If not, see http://www.gnu.org/licenses/. ..
The PUT Vein Database
---------------------
Changelog
=========
* **Version 1**, 10/Feb/2016:
- Initial release
* **Version 2**, 10/Feb/2017:
- Major update to make database compatible with BIOWAVE database toolchains
* **Version 3**, 16/Oct/2017:
- Bugfix: Incorrect usage of the BEAT synchronization mechanism
Description
===========
PUT Vein pattern database consists of 2400 images presenting human vein
patterns. Half of images contains a palmar vein pattern (1200 images) and
another half contains a wrist vein pattern (another 1200 images). Data was
acquired from both hands of 50 students, with means it has a 100 different
patterns for palm and wrist region. Pictures ware taken in 3 series, 4 pictures
each, with at least one week interval between each series. In case of palm
region volunteers were asked to put his/her hand on the device to cover
acquisition window, in way that line below their fingers coincident with its
edge. No additional positioning systems ware used. In case of wrist region only
construction allowing to place palm and wrist in comfortable way was used to
help position a hand.
Original images have **768 x 1024** resolution and are saved as 24-bit bitmap.
Database consist of 2 main sections: hand and wrist, with are further divided
in persons. Each person folder has sub-sections for left and right hand, which
are separated into series.
More information about the original database - `PUT Vein database
<http://biometrics.put.poznan.pl/vein-dataset/>`_.
In order to enable to use the database with BIOWAVE toolchains, this database
implementation converts image to a grey-scale (shape (768, 1024)) and then
rotates images by 270 deg so that vein pattern in wrist images would appear
vertical (wrist's part closer to the palm would appear at the top of the image)
In this implementation we use both - original 50 client x 2 hand data - in the
database clients with IDs between ``1`` and ``50`` - and also - mirrored
file representations (left hand / palm data mirrored to look like right hand
data and vice versa) - clients with IDs between ``51`` and ``100``.
Protocols
=========
Currently (as on 10.02.2017) there are 10x2 protocols, they also match the
protocols in ``bob.bio.vein``:
- ``palm-L_4``,
- ``palm-R_4``,
- ``palm-RL_4``,
- ``palm-LR_4``,
- ``palm-R_BEAT_4``,
- ``palm-L_1``,
- ``palm-R_1``,
- ``palm-RL_1``,
- ``palm-LR_1``,
- ``palm-R_BEAT_1``,
- ``wrist-L_4``,
- ``wrist-R_4``,
- ``wrist-RL_4``,
- ``wrist-LR_4``,
- ``wrist-R_BEAT_4``,
- ``wrist-L_1``,
- ``wrist-R_1``,
- ``wrist-RL_1``,
- ``wrist-LR_1``,
- ``wrist-R_BEAT_1``.
Protocols (except the ``BEAT`` protocols) still contains the original protocol
(``L``, ``R``, ``RL``, ``LR``) data, the difference is, whether each enroll
model is constructed using all 4 hand's images (protocol name ends with ``4``),
or each enroll image is used as a model (corresponding protocol names ends with
``1``).
The original protocols consists of following data, ``world`` purpose dataset
consists of the **same** data, as ``dev`` purpose dataset, so won't be
separately described:
+-------------+-----------------------------------------+-------------------------------------------+
|**protocol** | ``dev`` | ``eval`` |
+-------------+-----------------------------------------+-------------------------------------------+
| L | IDs 1-25, un-mirrored left hand images | IDs 26-50, un-mirrored left hand images |
+-------------+-----------------------------------------+-------------------------------------------+
| R | IDs 1-25, un-mirrored right hand images | IDs 26-50, un-mirrored right hand images |
+-------------+-----------------------------------------+-------------------------------------------+
| RL | IDs 1-50, un-mirrored right hand images |IDs 51-100, mirrored left hand images |
| | |(to represent right hand) |
+-------------+-----------------------------------------+-------------------------------------------+
| LR | IDs 1-50, un-mirrored left hand images |IDs 51-100, mirrored right hand images |
| | |(to represent left hand) |
+-------------+-----------------------------------------+-------------------------------------------+
The new test protocols (ends with ``R_BEAT_1`` and ``R_BEAT_4``) are intended
for use with ``bob.bio.vein`` and ``BEAT`` platform for quick tests, if
necessary. Both protocols consist of such data:
+-------------+---------------------------------------------------------+------------------------------------------------------------+
|**protocol** | ``dev`` | ``eval`` |
+-------------+---------------------------------------------------------+------------------------------------------------------------+
| R_BEAT | IDs ``1``, ``2``, un-mirrored right hand / wrist images | IDs ``26``, ``27``, un-mirrored right hand / wrist images |
+-------------+---------------------------------------------------------+------------------------------------------------------------+
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment