January 10, 2010: A supplement to the IREX I evaluation has been released. The document has two roles. First is to summarize the performance of iris recognition algorithms submitted to NIST since the September 2009 release of the main IREX results, NIST Interagency Report 7629. Second is to give an expanded quantification on the effect of JPEG 2000 compression to iris images.
October 30, 2009: IREX Executive Summary [0.5MB]
October 30, 2009: IREX Report [22MB]
October 30, 2009: IREX Report [zip] [14MB]
January 10, 2010: IREX Supplement I [12MB]
January 10, 2010: IREX Supplement I [zip] [6MB]
October 30, 2009: IREX Appendices [zip] [40MB]
October 30, 2009: The IREX I report, NIST Interagency Report 7629 has been revised as described on page 14 of the report.
September 15, 2008: A number of new entries in an updated FAQ.
September 15, 2008: A set of validation images has been released as zip and gzipped tar. The URL is available to IREX08 participants only, via a request to email@example.com. Validation is the process of checking that our linking and execution of your software gives identical results to your execution given the same input data. The validation process requires you to compile validation.c, and to link that to produce an application. This application reads the set of images, generates IREX 08 records and templates, and then matches them. An IREX 08 submission can be considered valid only when your output is identical to ours.
September 11, 2008: The API has been updated. The change made yesterday was a poor fix to the problem. So that change has been reversed, and instead a value of 0 on Table 6 Line 6 now indicates a failure to process the input image. See this and one new entry FAQ. The current IREX conops document is IREX08_conops_API_v11.pdf.
September 10, 2008: The API has been updated: Line 22 of the Table 6 can now have value 0. This indicates a failure to process the input image. See the new FAQ entry. The current IREX conops document is IREX08_conops_API_v10.pdf.
September 8, 2008: The API has been updated to optionally allow production of enrollment- and verification-specific templates. Also a bug on Line 18 of the Table 6 record has been fixed. This and other issues are addressed in the updated FAQ.
September 2, 2008: After a request from a participant, the submission deadline has been extended from September 12 to September 19, 2008.
September 2, 2008: The polar transformation code has been modified to set counterclockwise ordering. The old version used clockwise encoding which is contrary to ISO/IEC 19794-6/2005.
August 28, 2008: NIST requires the IREX SDKs to be encrypted, per these instructions. Our public key must be used.
August 21, 2008: NIST has released an example IREX record of Kind = 1. The purpose is to support testing of parsers.
August 20, 2008: NIST has released an initial implementation of the forward and reverse polar transformation code. The code is intended only as a reference for development purposes. It is open for public comment and may be updated. The code is licensed as follows:This software was developed at the National Institute of Standards and Technology (NIST) by employees of the Federal Government in the course of their official duties. Pursuant to title 17 Section 105 of the United States Code, this software is not subject to copyright protection and is in the public domain. NIST assumes no responsibility whatsoever for its use by other parties, and makes no guarantees, expressed or implied, about its quality, reliability, or any other characteristic.
August 18, 2008: The FAQ has three new entries. One is a major technical issue regarding polar angles.
August 6, 2008: The FAQ has been updated in response to a technical issue regarding NIST vs. vendor specification of polar sampling rates. This prompted a comment to be added to the IREX08 Test Plan. The FAQ also answers questions on NIST software code.
July 25, 2008: NIST gave a brief IREX 08 update to the ISO/IEC 19794-6 standards development committee.
June 20, 2008: Clarified version of IREX08 Test Plan indicates that withdrawal from IREX between July 2 and September 12, 2008 is allowed and will not be noted in the IREX report, but that withdrawal after September 12 will be noted. Also removal of legacy text implying testing will be conducted in two phases: IREX08 will proceed in one phase.
June 11, 2008: With the release of the final IREX08 Test Plan, NIST invites participation in what is likely to be the largest iris recognition test conducted to date. Intended to support credentialing programs based on ISO standardized iris images, the test will commence in Summer 2008 with a view toward making results available ahead of the SC 37 standards meeting in January 2009.
Important dates:2008-JUL-02: Declartion of intention to participate.2008-SEP-12: Deadline for submission of SDK's to NIST.
February 20, 2008: The second draft of the IREX 2008 concept, evaluation plan and API is now available. Comments are requested by March 11 - please see page 2. The schedule has been updated.
February 20, 2008: To be notified of future IREX announcements please send a request email to patrick.grother[at]nist.gov
November 18, 2007: The first draft of the IREX 2008 concept, evaluation plan and API is now available. Comments are welcome, please see page 2.
November 18, 2007: The IREX 2008 test is designed to measure the accuracy, interoperability of rectilinear and polar iris images formatted according to the ISO/IEC 19794-6 standard, under JPEG and JPEG 2000 compression.
NIST intends to publish the results of the IREX 2008 evaluation before the end of 2008.
May 30, 2008: The NIST public key for encryption of all software send to NIST is as follows. Use of this key is required. NIST does not accept responsiblity for any unencrypted software sent to NIST.pub 1024D/856B9B28 2008-05-28 Key fingerprint = 846E 7008 996A E912 974C F8D7 1C7A 0F22 856B 9B28 uid IREX Test Liaison (IREX Test Liaison Key) firstname.lastname@example.org> sub 2048g/5ABA2D90 2008-05-28