In the preprocessing track, original metadata for the input images will be invalid for the output images. What is the protocol for providing output metadata?
Do not output revised metadata for the preprocessed images. • The document “Executable Calling Signatures for FRVT 2006”, version dated January 18, 2006, states in section “Parameter Files” that “the precise content of the Parameter files has not been determined”. Also, all attribute names in the example in Figure B are lowercase, but in Table B, some are capitalized. Please provide an example parameter file in the final format. A: The parameter file format in the 18 January 2006 version of the document “Executable Calling Signatures for FRVT 2006” was intended to be final. I forgot to delete “the precise content of the Parameter files has not been determined”. The example parameter file that we use in the post “Example Parameter File for FRVT 2006” under FRGC v2 Announcements on the bbs. Attribute names are lower case in all of our parameter files. Element names are upper case. Originally, the attribute names were lower case in the document, however they could have been inadvertently
Do not output revised metadata for the preprocessed images. 113. The document “Executable Calling Signatures for FRVT 2006”, version dated January 18, 2006, states in section “Parameter Files” that “the precise content of the Parameter files has not been determined”. Also, all attribute names in the example in Figure B are lowercase, but in Table B, some are capitalized. Please provide an example parameter file in the final format. A: The parameter file format in the 18 January 2006 version of the document “Executable Calling Signatures for FRVT 2006” was intended to be final. I forgot to delete “the precise content of the Parameter files has not been determined”. The example parameter file that we use in the post Example Parameter File for FRVT 2006 under FRGC v2 Announcements on the bbs. Attribute names are lower case in all of our parameter files. Element names are upper case. Originally, the attribute names were lower case in the document, however they could have been inadvertently
Related Questions
- In the preprocessing track, original metadata for the input images will be invalid for the output images. What is the protocol for providing output metadata?
- The API Specification states, "If the output images are rotated relative to the input, OUTPUT_ROTATED should be set to TRUE." Is this required or optional?
- My input images were 4-bpp (or 1-, 8-, or 16-bpp) images. Why does the output movie use the less-optimal 24-bpp format?
