NIST has a benchmarking process. It is further explained here.
We need a the code and workflow prepared for the benchmarking to take place.
Technically relevant sections
### API Document
A new [API document](https://pages.nist.gov/frvt/api/FRVT_ongoing_11_api.pdf) has been published. All FRVT APIs reference the supporting [FRVT General Evaluation Specifications](https://pages.nist.gov/frvt/api/FRVT_common.pdf), which includes hardware and operating system environment, software requirements, reporting, and common data structures that support the APIs. [last update: 2021-03-22]
### Validation
An updated [validation package](https://github.com/usnistgov/frvt) has been published. All participants must run their software through the updated validation package prior to submission. The purpose of validation is to ensure consistent algorithm output between your execution and NIST’s execution. **Note:** The provider identifier in the core implementation library must be an appropriate, representative, non-infringing name of the main provider of the software. If the provider identifier is not representative of the submitting organization, NIST reserves the right to reject the submission for testing. [last update: 2020-09-10]
NIST has a benchmarking process. It is further explained here.
We need a the code and workflow prepared for the benchmarking to take place.
Technically relevant sections
### API Document A new [API document](https://pages.nist.gov/frvt/api/FRVT_ongoing_11_api.pdf) has been published. All FRVT APIs reference the supporting [FRVT General Evaluation Specifications](https://pages.nist.gov/frvt/api/FRVT_common.pdf), which includes hardware and operating system environment, software requirements, reporting, and common data structures that support the APIs. [last update: 2021-03-22] ### Validation An updated [validation package](https://github.com/usnistgov/frvt) has been published. All participants must run their software through the updated validation package prior to submission. The purpose of validation is to ensure consistent algorithm output between your execution and NIST’s execution. **Note:** The provider identifier in the core implementation library must be an appropriate, representative, non-infringing name of the main provider of the software. If the provider identifier is not representative of the submitting organization, NIST reserves the right to reject the submission for testing. [last update: 2020-09-10]