Participation is simple. Fill out an agreement, write your software library conforming to the MINEX III API, confirm your functionality with the validation package, and then submit your software to NIST.
Sign, minex [at] nist.gov (e-mail a scanned copy), and postal mail the original signed evaluation agreement to NIST. If provided, please include the delivery tracking numbers when e-mailing your scanned agreement. Both an e-mail scanned copy andphysical hard copy are required.
Anonymous participation is not allowed.
A new agreement must be received by NIST for each submission version after posting previous results.
No results will be released until a physical agreement has been received.
Your participation status may be made public anytime on or after receipt of a software library submission and a signed agreement.
The required build system for MINEX III is currently CentOS Linux release 7.6.1810. NIST provides a mirror of the digital installation media for this operating system and a list of installed CentOS packages. Failure to build your software library on this operating system may result in delays and unexpected behavior. Use of a consistent operating system enables reproducible research.
Once you have successfully run the validation package, a file will be generated that you must sign, encrypt, and submit to NIST, along with your public key. Instructions will be printed by the validation package.
Do not modify the files generated by the validation package. However, you are highly encouraged to review the generated files.
Do not submit files if the validation package has alerted you of an error.
Testing will be conducted solely by Federal U.S. Government employees at NIST's Gaithersburg, MD location using NIST-owned computer hardware in a secure facility. Test hardware runs in an isolated environment with no access to the Internet.