nbis-wrapper-js 0.0.1

package/libnbis/nbis_x86-64_linux/man/man1/cjpegl.1

@@ -0,0 +1,234 @@
+.\" @(#)cjpegl.1 2008/10/02 NIST
+.\" I Image Group
+.\" Craig Watson and Michael D. Garris
+.\"
+.TH CJPEGL 1G "02 October 2008" "NIST" "NBIS Reference Manual"
+.SH NAME
+cjpegl \- compresses a grayscale or color image using Lossless
+JPEG (JPEGL).
+.SH SYNOPSIS
+.B cjpegl
+.I <outext>
+.I <image file>
+.br
+.RS
+[\fB-raw_in \fIw\fR,\fIh\fR,\fId\fR,[\fIppi\fR]
+.RS 3
+[\fB-nonintrlv\fR]
+.br
+[\fB-YCbCr \fIH0\fR,\fIV0\fR:\fIH1\fR,\fIV1\fR:\fIH2\fR,\fIV2\fR]]
+.RE
+[\fIcomment file\fR]
+.SH DESCRIPTION
+.B Cjpegl
+takes as input a file containing an uncompressed grayscale or color
+image.  Two possible input file formats are accepted, NIST IHead
+files and raw pixmap files.  If a raw pixmap file is to be compressed,
+then its image attributes must be provided on the command line as well.
+Once read into memory, the grayscale or color pixmap is then
+compressed using Lossless JPEG (JPEGL).
+The JPEGL results are then written to an output file.
+
+The color components of RGB pixels in a raw pixmap file may
+be interleaved or non-interleaved.  By default, \fBcjpegl\fR
+assumes interleaved color pixels.  In fact \fBcjpegl\fR's internal
+encoder requires non-interleaved components planes; therefore,
+interleaved pixmaps are automatically converted prior to encoding
+and results are stored accordingly.
+(See INTERLEAVE OPTIONS below.)
+
+\fBCjpegl\fR also supports the compression of raw pixmap files
+containing YCbCr images with potentially downsampled component planes.
+By default, this utility assumes no downsampling of component planes.
+(See YCbCr OPTIONS below.)  Regarding color pixmaps, the NIST IHead
+file format only supports interleaved RGB images.
+
+.SH OPTIONS
+All switch names may be abbreviated; for example,
+\fB-raw_in\fR may be written \fB-r\fR.
+.TP
+.I <outext>
+the extension of the compressed output file.
+To construct the output filename, \fBcjpegl\fR takes the
+input filename and replaces its extension with the one
+specified here.
+.TP
+.I <image file>
+the input file, either an IHead file or raw pixmap file,
+containing the grayscale or color image to be compressed.
+.TP
+\fB-raw_in \fIw\fR,\fIh\fR,\fId\fR,[\fIppi\fR]
+the attributes of the input image.  This option must
+be included on the command line if the input is a
+raw pixmap file.
+.br
+.RS
+.TP
+.I w
+the pixel width of the pixmap
+.TP
+.I h
+the pixel height of the pixmap
+.TP
+.I d
+the pixel depth of the pixmap
+.TP
+.I ppi
+the optional scan resolution of the image in integer units of
+pixels per inch.
+.RE
+.TP
+.B -nonintrlv
+specifies that the color components in an \fIinput\fR raw pixmap file
+image are non-interleaved and stored in separate component planes.
+(See INTERLEAVE OPTIONS below.)
+.TP
+\fB-YCbCr \fIH0\fR,\fIV0\fR:\fIH1\fR,\fIV1\fR:\fIH2\fR,\fIV2
+denotes an \fIinput\fR raw pixmap file containing a YCbCr colorspace image
+and whether any component planes have been \fIpreviously\fR downsampled.
+H,V factors all set to 1 represent no downsampling.
+(See YCbCr Options below.)
+.TP
+.I comment file
+an optional user-supplied ASCII comment file.  (See COMMENT
+OPTIONS below.)
+.TP
+\fB-version
+\fRPrint ANSI/NIST stardand and NBIS software version.
+
+.SH INTERLEAVE OPTIONS
+The color components of RGB pixels in a raw pixmap file may
+be interleaved or non-interleaved.  Color components are interleaved
+when a pixel's (R)ed, (G)reen, and (B)lue components are sequentially
+adjacent in the image byte stream, ie. RGBRGBRGB... .  If the color
+components are non-interleaved, then all (R)ed components in the
+image are sequentially adjacent in the image byte stream, followed
+by all (G)reen components, and then lastly followed by all (B)lue
+components.  Each complete sequence of color components is called
+a \fIplane\fR.  The utilities \fBintr2not\fR and \fBnot2intr\fR
+convert between interleaved and non-interleaved color components.
+By default, \fBcjpegl\fR assumes interleaved
+color components, and all color IHead images must be
+interleaved.  Note that \fBcjpegl\fR's internal encoder requires
+non-interleaved component planes; therefore, interleaved pixmaps
+are automatically converted prior to encoding and results are
+stored accordingly.
+
+.SH YCbCr OPTIONS
+\fBCjpegl\fR compresses color images with 3 components
+per pixel, including RGB and YCbCr colorspaces.  A common compression
+technique for YCbCr images is to downsample the Cb & Cr component
+planes.
+\fBCjpegl\fR supports a limited range of YCbCr downsampling
+schemes that are represented by a list of component plane factors.
+These factors together represent downsampling ratios relative to
+each other.  The comma-separated list of factor pairs correspond to
+the Y, Cb, and
+Cr component planes respectively.  The first value in a factor
+pair represents the downsampling of that particular component plane
+in the X-dimension, while the second represents the Y-dimension.
+Compression ratios for a particular component plane are calculated
+by dividing the maximum component factors in the list by the current
+component's factors.  These integer factors are limited
+between 1 and 4.  H,V factors all set to 1 represent
+no downsampling.  For complete details, \fBcjpegl\fR implements
+the downsampling and interleaving schemes described in the
+following reference:
+
+.RS
+W.B. Pennebaker and J.L. Mitchell, "JPEG: Still Image Compression
+Standard," Appendix A - "ISO DIS 10918-1 Requirements and Guidelines,"
+Van Nostrand Reinhold, NY, 1993, pp. A1-A4.
+.RE
+
+For example the option specification:
+
+.RS
+-YCbCr 4,4:2,2:1,1
+.RE
+
+represents a YCbCr image with non-downsampled Y component plane
+(4,4 are the largest X and Y factors listed); the Cb component
+plane is downsampled in X and Y by a factor of 2
+(maximum factors 4 divided by current factors 2); and the Cr component
+plane is downsampled in X and Y by a factor of 4 (maximum factors 4 divided
+by current factors 1).  Note that downsampling component planes
+is a form of \fIlossy\fR compression,  so while \fBcjpegl\fR
+enables the image byte stream associated with an input YCbCr
+image to be reconstructed perfectly, if any of
+its component planes were previously downsampled, then image
+loss has already taken place.  The utility \fBrgb2ycc\fR converts
+an RGB image to the YCbCr colorspace, and it will conduct component
+plane downsampling as specified.  Note that IHead images can only
+have RGB color components, so YCbCr options only pertain to
+raw pixmap files.
+
+.SH COMMENT OPTIONS
+Upon successful compression, this utility generates and inserts
+in the compressed output file a specially formatted comment block,
+called a NISTCOM.  A NISTCOM is a text-based attribute list comprised
+of (name, value) pairs, one pair per text line.
+The first line of a NISTCOM always has name = "NIST_COM" 
+and its value is always the total number of attributes included in
+the list.  The utility \fBrdjpgcom\fR scans a JPEG compressed file for
+any and all comment blocks.  Once found, the contents of each comment
+block is printed to standard output.  Using this utility, the NISTCOM
+provides easy access to relevant image attributes.  The following is
+an example NISTCOM generated by \fBcjpegl\fR:
+
+.RS
+NIST_COM 11
+.br
+PIX_WIDTH 768
+.br
+PIX_HEIGHT 1024
+.br
+PIX_DEPTH 24
+.br
+PPI -1
+.br
+LOSSY 0
+.br
+NUM_COMPONENTS 3
+.br
+HV_FACTORS 1,1:1,1:1,1
+.br
+INTERLEAVE 0
+.br
+COMPRESSION JPEGL
+.br
+JPEGL_PREDICT 4
+
+.RE
+\fBCjpegl\fR also accepts an optional comment file on the command
+line.  If provided, the contents of this file are also inserted
+into the compressed output file.  If the comment file is a
+NISTCOM attribute list, then its contents are merged with the
+NISTCOM internally generated by \fBcjpegl\fR and a single NISTCOM
+is written to the compressed output file.  Note that \fBcjpegl\fR
+gives precedence to internally generated attribute values.
+If the user provides a non-NISTCOM comment file,
+then the contents of file are stored to a separate comment block in
+the output file.  Using these comment options enables the user
+to store application-specific information in a JPEG file.
+
+.SH EXAMPLES
+From \fItest/imgtools/execs/cjpegl/cjpegl.src\fR:
+.PP
+.RS
+.B % cjpegl jpl face.raw -r 768,1024,24
+.br
+compresses a color face image in a raw pixmap file.
+
+.SH SEE ALSO
+.BR cjpegb (1G),
+.BR djpegl (1G),
+.BR dpyimage (1G),
+.BR intr2not (1G),
+.BR not2intr (1G),
+.BR rdjpgcom (1H),
+.BR rgb2ycc (1G),
+.BR wrjpgcom (1H)
+
+.SH AUTHOR
+NIST/ITL/DIV894/Image Group

package/libnbis/nbis_x86-64_linux/man/man1/cmbmcs.1

@@ -0,0 +1,85 @@
+.\" @(#)cmbmcs.1 2008/10/02 NIST
+.\" I Image Group
+.\" G. T. Candela & Craig I. Watson
+.\"
+.TH CMBMCS 1B "02 October 2008" "NIST" "NBIS Reference Manual"
+.SH NAME
+cmbmcs \- combines PCASYS mean/covariance data file pairs.
+.SH SYNOPSIS
+.B cmbmcs
+.I <meanfile_in[meanfile_in...]> <covfile_in[covfile_in...]>
+.I <meanfile_out> <meanfile_out_desc>
+.I <covfile_out> <covfile_out_desc> <ascii_outfiles>
+.SH DESCRIPTION
+.B Cmbmcs
+combines pairs of PCASYS mean vector and covariance matrix
+data files, to produce a mean/covariance pair that is approximately
+the same as would have resulted if all the vectors that were used to
+make the input means and covariances had been given to the meancov
+function in one large set.  So, if the sample covariance matrix needs to
+be made from a large set of vectors, and several processors are
+available, it may be possible to save run time by, first, running
+several simultaneous instances of meancov, each on a subset of the
+vectors, and second, running cmbmcs to combine the means
+and covariances made by the meancov instances.  (Even if only the
+covariance is ultimately needed, i.e. not the mean, it is necessary
+for the meancov instances to compute the means and for cmbmcs to
+use them, to compute the overall covariance.)
+.SH OPTIONS
+.TP
+.I <meanfile_in[meanfile_in...]>
+Input files each containing a mean vector.  These files must be in
+PCASYS "matrix" format, each with first dimension 1 and all having the
+same second dimension. (Usually the output of \fBmeancov\fR.)
+.TP
+.I <covfile_in[covfile_in...]>
+Input files each containing a covariance matrix.  These files must be
+in PCASYS "covariance" format.  The i'th input covariance file goes
+with the i'th input mean file.  These covariances must all have the
+same order, which must be the second dimension of the input mean
+vector files. (Usually the output of \fBmeancov\fR.)
+.TP
+.I <meanfile_out>
+Mean file to be written, in PCASYS "matrix" format.
+.TP
+.I <meanfile_out_desc>
+A string to be written into the mean output files description
+string.  This string can be of any length, but must not contain
+embedded newline characters.  If it contains spaces, tabs, or shell
+metacharacters that are not to be expanded, then it should be quoted.
+To leave the description empty, use '' (two single quotes, i.e.
+single\-quoted empty string).  To let cmbmcs make a description
+(stating that this is a mean vector made by cmbmcs and listing the
+names of the input files), use \- (hyphen).
+.TP
+.I <covfile_out>
+Covariance file to be produced, in PCASYS "covariance" format.  Its
+"number of vectors" field will be set to the sum of the values of that
+field across the input covariances.
+.TP
+.I <covfile_out_desc>
+Description string for output covariance file or - to let cmbmcs make
+the description (as for output mean file description).
+.TP
+.I <ascii_outfiles>
+If y, makes ascii output files; if n, binary.  Binary is recommended,
+unless the output files must be portable across different byte orders
+or floating_point formats.
+.TP
+\fB-version
+\fRPrint ANSI/NIST stardand and NBIS software version.
+
+.SH EXAMPLE(S)
+From \fItest/pcasys/execs/cmbmcs/cmbmcs.src\fR:
+.PP
+.RS
+.B % cmbmcs ../meancov/fv1.men ../meancov/fv2.men \
+../meancov/fv1.cov ../meancov/fv2.cov fv_tst.men - fv_tst.cov - n
+.br
+Combines the mean/covariance files for fv1 and fv2 into a
+mean/covariance set of files.
+.SH "SEE ALSO"
+meancov (1B)
+
+.SH AUTHOR
+NIST/ITL/DIV894/Image Group

package/libnbis/nbis_x86-64_linux/man/man1/cropcoeff.1

@@ -0,0 +1,70 @@
+.\" @(#)cropcoeff.1 2008/10/02 NIST
+.\" I Image Group
+.\" Kenneth Ko
+.\"
+.TH CORPCOEFF 1F "03 October 2008" "NIST" "NBIS Reference Manual"
+.SH NAME
+cropcoeff \- Read AN2K/AN2K7 file, and crop each Type-14 record.
+.SH SYNOPSIS
+.B cropcoeff
+.I [option]
+.I <file in>
+.SH DESCRIPTION
+.B CropCoeff
+Extracts the individual fingerprint images from the WSQ compressed slap
+images (left/right hand, thumbs) in ANSI/NIST 2007 Type-14 records into
+individual WSQ files without decompressing/recompressing the slap images.
+The ANSI/NIST 2007 Type-14 record must contain both the WSQ compressed
+slap image and the corresponding segmentation coordinates.  Segmentation
+coordinates are stored in the Type-14 record as defined in the
+ANSI/NIST 2007 specification.
+
+This code is briefly described in the following in the following report
+http://www.mitre.org/work/tech_papers/tech_papers_08/08_0060/index.html
+
+CropCoeff DOES NOT compute segmentation coordinates, it simply uses
+whatever is provided in the Type-14 record.  If no coordinates are
+provided in the Type-14 record CropCoeff does not produce output for
+that slap image.
+
+CropCoeff will move the x,y coordinates of the top-left corner of each
+segmentation box to the nearest factor of 32 pixels.  CropCoeff will move
+any edge that is within 24 pixels of the slap image edge out to
+that image limit. CropCoeff will expand any segmentation box less than 100
+pixels in width or height up to 100 pixels, by equally (when possible) expand
+the corresponding edges of the segmentation box.  The extracted
+fingerprint images do contain some "noise" in the reconstructed image
+around the edges as compared to decompressing the full slap image and
+extracting the same pixels from that reconstructed image.  This is
+caused by "edge wrapping/boundary" conditions in the WSQ algorithm.
+
+The output files from CropCoeff can be decompressed individually with a
+WSQ compliant algorithm.
+
+The output files contain the base name of the input file with a new extension
+containing the finger position (FNG).  For example if the input file is
+file.an2 then the output files would be file.<FNG>.wsq. FNG is assigned a
+value 1-10 corresponding to the finger number for that segmented image.
+The number are defined as 1-R. Thumb, 2-R Index, 3-R. Middle, 4-R. Ring,
+5-R. Little, 6-L. Thumb, 7-L. Index, 8-L. Middle, 9-L. Ring, and 10-L. Little.
+.SH OPTIONS
+.TP
+.I -v L 
+set verbose level of the corp wsq image which "L" is a integer.
+.TP
+.I <file in>
+the ANSI/NIST file to be converted
+.TP
+\fB-version
+\fRPrint ANSI/NIST stardand and NBIS software version.
+
+.SH EXAMPLES
+From \fItest/an2k7/execs/cropcoeff/cropcoeff.src\fR:
+.PP
+.RS
+.B % cropcoeff ../../data/nist.an2
+.PP
+.B % cropcoeff -v 1 ../../data/nist.an2
+
+.SH AUTHOR
+NIST/ITL/DIV894/Image Group

package/libnbis/nbis_x86-64_linux/man/man1/cwsq.1

@@ -0,0 +1,145 @@
+.\" @(#)cwsq.1 2008/10/02 NIST
+.\" I Image Group
+.\" Craig Watson and Michael D. Garris
+.\"
+.TH CWSQ 1G "02 October 2008" "NIST" "NBIS Reference Manual"
+.SH NAME
+cwsq \- WSQ compresses grayscale fingerprint images.
+.SH SYNOPSIS
+.B cwsq
+.I <r bitrate>
+.I <outext>
+.I <image file>
+.br
+.RS
+[\fB-raw_in \fIw\fR,\fIh\fR,\fId\fR,[\fIppi\fR]]
+[\fIcomment file\fR]
+.SH DESCRIPTION
+.B Cwsq
+takes as input a file containing an uncompressed grayscale fingerprint
+image.  Two possible input file formats are accepted, NIST IHead files
+and raw pixmap files.  If a raw pixmap file is to be compressed, then
+its image attributes must be provided on the command line as well.
+Once read into memory, the pixmap is \fIlossy\fR compressed
+using Wavelet Scalar Quantization as described in the FBI's Criminal
+Justice Information Services (CJIS) document, "WSQ Gray-scale Fingerprint
+Compressions Specification," Dec. 1997.  The results are then written
+to an output file in a format dictated by this document.  This is
+the only fingerprint compression format accepted by the FBI IAFIS system.
+
+.SH OPTIONS
+All switch names may be abbreviated; for example,
+\fB-raw_in\fR may be written \fB-r\fR.
+.TP
+.I <r bitrate>
+determines the amount of lossy compression.
+.br
+.RS
+Suggested settings:
+.RS 3
+.br
+\fIr bitrate\fR = 2.25 yields around 5:1 compression
+.br
+\fIr bitrate\fR = 0.75 yields around 15:1 compression
+.RE
+.RE
+.TP
+.I <outext>
+the extension of the compressed output file.
+To construct the output filename, \fBcwsq\fR takes the
+input filename and replaces its extension with the one
+specified here.
+.TP
+.I <image file>
+the input file, either an IHead file or raw pixmap file,
+containing the fingerprint image to be compressed.
+.TP
+\fB-raw_in \fIw\fR,\fIh\fR,\fId\fR,[\fIppi\fR]
+the attributes of the input image.  This option must
+be included on the command line if the input is a
+raw pixmap file.
+.br
+.RS
+.TP
+.I w
+the pixel width of the pixmap
+.TP
+.I h
+the pixel height of the pixmap
+.TP
+.I d
+the pixel depth of the pixmap
+.TP
+.I ppi
+the optional scan resolution of the image in integer units of
+pixels per inch.
+.RE
+.TP
+.I comment file
+an optional user-supplied ASCII comment file.  (See COMMENT
+OPTIONS below.)
+.TP
+\fB-version
+\fRPrint ANSI/NIST stardand and NBIS software version.
+
+.SH COMMENT OPTIONS
+Upon successful compression, this utility generates and inserts
+in the compressed output file a specially formatted comment block,
+called a NISTCOM.  A NISTCOM is a text-based attribute list comprised
+of (name, value) pairs, one pair per text line.
+The first line of a NISTCOM always has name = "NIST_COM" 
+and its value is always the total number of attributes included in
+the list.  The utility \fBrdwsqcom\fR scans a WSQ compressed file for
+any and all comment blocks.  Once found, the contents of each comment
+block is printed to standard output.  Using this utility, the NISTCOM
+provides easy access to relevant image attributes.  The following is
+an example NISTCOM generated by \fBcwsq\fR:
+
+.RS
+NIST_COM 9
+.br
+PIX_WIDTH 500
+.br
+PIX_HEIGHT 500
+.br
+PIX_DEPTH 8
+.br
+PPI 500
+.br
+LOSSY 1
+.br
+COLORSPACE GRAY
+.br
+COMPRESSION WSQ
+.br
+WSQ_BITRATE 0.750000
+
+.RE
+\fBCwsq\fR also accepts an optional comment file on the command
+line.  If provided, the contents of this file are also inserted
+into the compressed output file.  If the comment file is a
+NISTCOM attribute list, then its contents are merged with the
+NISTCOM internally generated by \fBcwsq\fR and a single NISTCOM
+is written to the compressed output file.  Note that \fBcwsq\fR
+gives precedence to internally generated attribute values.
+If the user provides a non-NISTCOM comment file,
+then the contents of file are stored to a separate comment block in
+the output file.  Using these comment options enables the user
+to store application-specific information in a WSQ file.
+
+.SH EXAMPLES
+From \fItest/imgtools/execs/cwsq/cwsq.src\fR:
+.PP
+.RS
+.B % cwsq .75 wsq finger.raw -r 500,500,8,500
+.br
+compresses a raw fingerprint pixmap.
+
+.SH SEE ALSO
+.BR dpyimage (1G),
+.BR dwsq (1G),
+.BR rdwsqcom (1G),
+.BR wrwsqcom (1G)
+
+.SH AUTHOR
+NIST/ITL/DIV894/Image Group

package/libnbis/nbis_x86-64_linux/man/man1/datainfo.1

@@ -0,0 +1,59 @@
+.\" @(#)datainfo.1 2008/10/02 NIST
+.\" I Image Group
+.\" G. T. Candela & Craig I. Watson
+.\"
+.TH DATAINFO 1B "02 October 2008" "NIST" "NBIS Reference Manual"
+.SH NAME
+datainfo \- shows the header information of a PCASYS data file.
+.SH SYNOPSIS
+.B datainfo
+.I <datafile>
+.SH DESCRIPTION
+.B Datainfo
+reads the header information from a PCASYS data file and writes a
+short report of this information to the standard output.
+
+The file must be in one of the official PCASYS
+data file formats, which are "matrix" (matrix of floating point
+numbers), "covariance" (covariance matrix of floating point numbers,
+with only the nonstrict lower triangle stored since a covariance
+matrix is symmetric), and "classes" (classes, represented as
+unsigned characters, which are thought of as being integers in the
+range 0 through 255).  PCASYS data files come in these three types,
+and can be either "ascii" or "binary", so there are really 6 types
+in all.
+
+Datainfo reports the description string of the data file,
+its type (matrix, etc.), whether it is ascii or binary, and then
+some final information specific to the file type: if matrix,
+the two dimensions; if covariance, the order (of the symmetric
+covariance matrix, i.e. the number that both dimensions equal) and
+the number of input vectors used to make the covariance; if classes,
+the number of elements.
+
+.SH OPTIONS
+.TP
+.I <datafile>
+Data file whose header information is to be reported.
+.TP
+\fB-version
+\fRPrint ANSI/NIST stardand and NBIS software version.
+
+.SH EXAMPLE(S)
+From \fItest/pcasys/execs/datainfo/datainfo.src\fR:
+.PP
+.RS
+.B % datainfo ../../data/oas/fv1-9.cls >& fv1-9cls.dat
+.PP
+.B % datainfo ../../data/oas/fv1.oas >& fv1oas.dat
+.PP
+.B % datainfo ../meancov/fv1-9.cov >& fv1-9cov.dat
+.br
+Prints out the file header information for the various types
+of files, class (fv1-9.cls), orientation arrays (fv1.oas),
+and covariance (fv1-9.cov).
+.SH "SEE ALSO"
+chgdesc (1B)
+
+.SH AUTHOR
+NIST/ITL/DIV894/Image Group

package/libnbis/nbis_x86-64_linux/man/man1/diffbyts.1

@@ -0,0 +1,71 @@
+.\" @(#)diffbyts.1 2008/10/02 NIST
+.\" I Image Group
+.\" Craig Watson
+.\"
+.TH DIFFBYTS 1G "02 October 2008" "NIST" "NBIS Reference Manual"
+.SH NAME
+diffbyts \- takes two binary data files and compares them byte
+for byte, compiling a cumulative histogram of differences.
+.SH SYNOPSIS
+.B diffbyts
+.I <file1>
+.I <file2>
+
+.SH DESCRIPTION
+.B Diffbyts
+takes as input two binary files of equal length and compares the
+contents between the two files byte for byte.  The differences
+between corresponding pairs of bytes are accumulated into a histogram,
+where each bin in the histogram represents the integer difference
+between the byte pairs.  Therefore, the first bin in the histogram
+contains the count of all those byte pairs that are exactly the same
+(a difference of 0); the next bin contains the count of all those
+byte pairs that are different by exactly 1; and so on.
+
+Upon completion, this utility prints a formatted report of the
+accumulated histogram to standard output.  Each difference
+bin in the histogram is listed on separate line in the report
+and formatted at follows:
+
+.RS
+d[\fIb\fR] = \fIc\fR : \fIp\fR
+.RE
+.br
+where
+.br
+.RS
+.TP
+.I b
+is the current bin's byte pair difference.
+.TP
+.I c
+is the number of corresponding byte pairs with difference
+equal to \fIb\fR.
+.TP
+.I p
+is the cumulative percentage of corresponding pairs of bytes
+counted in all the bins up to and including the current bin.
+.RE
+
+.SH OPTIONS
+.TP
+.I <file1>
+a binary file to be compared byte for byte to \fIfile2\fR.
+.TP
+.I <file2>
+a binary file to be compared byte for byte to \fIfile1\fR.
+.TP
+\fB-version
+\fRPrint ANSI/NIST stardand and NBIS software version.
+
+.SH EXAMPLES
+From \fItest/imgtools/execs/diffbyts/diffbyts.src\fR:
+.RS
+.PP
+.B % diffbyts ../../data/finger/gray/raw/finger.raw ../dwsq/finger.raw > finger.hst
+.br
+compiles and stores a byte-difference histogram reporting
+the amount of image degradation due to lossy WSQ compression.
+
+.SH AUTHOR
+NIST/ITL/DIV894/Image Group

package/libnbis/nbis_x86-64_linux/man/man1/djp2k.1

@@ -0,0 +1,21 @@
+.\" @(#)djp2k1 2008/10/02 NIST
+.\" I Image Group
+.\" Kenneth Ko
+.\"
+.TH DJP2K 1G "20 May 2009" "NIST" "NBIS Reference Manual"
+.SH NAME
+djp2k \- Decompress a JPEG2000 image into either pnm or raw image format. This is based on the j2k_to_image application implemented in the OPENJPEG library.
+.br
+.SH DESCRIPTION
+.B Djp2k
+takes as input a file containing an JPEG2000 fingerprint image, decompresses it to either pnm or raw image format, and writes to a new file.  This is an implementation of the JPEG 2000 standard for decompression of image files.  Go to \fIhttp://www.openjpeg.org\fR for the full details on how to use the application.
+
+.SH SEE ALSO
+.BR cjp2k (1G),
+.BR dpyimage (1G),
+.BR dwsq (1G),
+.BR rdwsqcom (1G),
+.BR wrwsqcom (1G)
+
+.SH AUTHOR
+NIST/ITL/DIV894/Image Group