nbis-wrapper-js 0.0.1

package/libnbis/nbis_arm64_darwin/man/man1/djpeg.1

@@ -0,0 +1,257 @@
+.TH DJPEG 1H "02 October 2008" "IJG" "NBIS Reference Manual"
+.SH NAME
+djpeg \- decompress a JPEG file to an image file
+.SH SYNOPSIS
+.B djpeg
+[
+.I options
+]
+[
+.I filename
+]
+.LP
+.SH DESCRIPTION
+.LP
+.B djpeg
+decompresses the named JPEG file, or the standard input if no file is named,
+and produces an image file on the standard output.  PBMPLUS (PPM/PGM), BMP,
+GIF, Targa, or RLE (Utah Raster Toolkit) output format can be selected.
+(RLE is supported only if the URT library is available.)
+.SH OPTIONS
+All switch names may be abbreviated; for example,
+.B \-grayscale
+may be written
+.B \-gray
+or
+.BR \-gr .
+Most of the "basic" switches can be abbreviated to as little as one letter.
+Upper and lower case are equivalent (thus
+.B \-BMP
+is the same as
+.BR \-bmp ).
+British spellings are also accepted (e.g.,
+.BR \-greyscale ),
+though for brevity these are not mentioned below.
+.PP
+The basic switches are:
+.TP
+.BI \-colors " N"
+Reduce image to at most N colors.  This reduces the number of colors used in
+the output image, so that it can be displayed on a colormapped display or
+stored in a colormapped file format.  For example, if you have an 8-bit
+display, you'd need to reduce to 256 or fewer colors.
+.TP
+.BI \-quantize " N"
+Same as
+.BR \-colors .
+.B \-colors
+is the recommended name,
+.B \-quantize
+is provided only for backwards compatibility.
+.TP
+.B \-fast
+Select recommended processing options for fast, low quality output.  (The
+default options are chosen for highest quality output.)  Currently, this is
+equivalent to \fB\-dct fast \-nosmooth \-onepass \-dither ordered\fR.
+.TP
+.B \-grayscale
+Force gray-scale output even if JPEG file is color.  Useful for viewing on
+monochrome displays; also,
+.B djpeg
+runs noticeably faster in this mode.
+.TP
+.BI \-scale " M/N"
+Scale the output image by a factor M/N.  Currently the scale factor must be
+1/1, 1/2, 1/4, or 1/8.  Scaling is handy if the image is larger than your
+screen; also,
+.B djpeg
+runs much faster when scaling down the output.
+.TP
+.B \-bmp
+Select BMP output format (Windows flavor).  8-bit colormapped format is
+emitted if
+.B \-colors
+or
+.B \-grayscale
+is specified, or if the JPEG file is gray-scale; otherwise, 24-bit full-color
+format is emitted.
+.TP
+.B \-gif
+Select GIF output format.  Since GIF does not support more than 256 colors,
+.B \-colors 256
+is assumed (unless you specify a smaller number of colors).
+.TP
+.B \-os2
+Select BMP output format (OS/2 1.x flavor).  8-bit colormapped format is
+emitted if
+.B \-colors
+or
+.B \-grayscale
+is specified, or if the JPEG file is gray-scale; otherwise, 24-bit full-color
+format is emitted.
+.TP
+.B \-pnm
+Select PBMPLUS (PPM/PGM) output format (this is the default format).
+PGM is emitted if the JPEG file is gray-scale or if
+.B \-grayscale
+is specified; otherwise PPM is emitted.
+.TP
+.B \-rle
+Select RLE output format.  (Requires URT library.)
+.TP
+.B \-targa
+Select Targa output format.  Gray-scale format is emitted if the JPEG file is
+gray-scale or if
+.B \-grayscale
+is specified; otherwise, colormapped format is emitted if
+.B \-colors
+is specified; otherwise, 24-bit full-color format is emitted.
+.PP
+Switches for advanced users:
+.TP
+.B \-dct int
+Use integer DCT method (default).
+.TP
+.B \-dct fast
+Use fast integer DCT (less accurate).
+.TP
+.B \-dct float
+Use floating-point DCT method.
+The float method is very slightly more accurate than the int method, but is
+much slower unless your machine has very fast floating-point hardware.  Also
+note that results of the floating-point method may vary slightly across
+machines, while the integer methods should give the same results everywhere.
+The fast integer method is much less accurate than the other two.
+.TP
+.B \-dither fs
+Use Floyd-Steinberg dithering in color quantization.
+.TP
+.B \-dither ordered
+Use ordered dithering in color quantization.
+.TP
+.B \-dither none
+Do not use dithering in color quantization.
+By default, Floyd-Steinberg dithering is applied when quantizing colors; this
+is slow but usually produces the best results.  Ordered dither is a compromise
+between speed and quality; no dithering is fast but usually looks awful.  Note
+that these switches have no effect unless color quantization is being done.
+Ordered dither is only available in
+.B \-onepass
+mode.
+.TP
+.BI \-map " file"
+Quantize to the colors used in the specified image file.  This is useful for
+producing multiple files with identical color maps, or for forcing a
+predefined set of colors to be used.  The
+.I file
+must be a GIF or PPM file. This option overrides
+.B \-colors
+and
+.BR \-onepass .
+.TP
+.B \-nosmooth
+Use a faster, lower-quality upsampling routine.
+.TP
+.B \-onepass
+Use one-pass instead of two-pass color quantization.  The one-pass method is
+faster and needs less memory, but it produces a lower-quality image.
+.B \-onepass
+is ignored unless you also say
+.B \-colors
+.IR N .
+Also, the one-pass method is always used for gray-scale output (the two-pass
+method is no improvement then).
+.TP
+.BI \-maxmemory " N"
+Set limit for amount of memory to use in processing large images.  Value is
+in thousands of bytes, or millions of bytes if "M" is attached to the
+number.  For example,
+.B \-max 4m
+selects 4000000 bytes.  If more space is needed, temporary files will be used.
+.TP
+.BI \-outfile " name"
+Send output image to the named file, not to standard output.
+.TP
+.B \-verbose
+Enable debug printout.  More
+.BR \-v 's
+give more output.  Also, version information is printed at startup.
+.TP
+.B \-debug
+Same as
+.BR \-verbose .
+.TP
+\fB-version
+\fRPrint ANSI/NIST stardand and NBIS software version.
+
+.SH EXAMPLES
+.LP
+This example decompresses the JPEG file foo.jpg, quantizes it to
+256 colors, and saves the output in 8-bit BMP format in foo.bmp:
+.IP
+.B djpeg \-colors 256 \-bmp
+.I foo.jpg
+.B >
+.I foo.bmp
+.SH HINTS
+To get a quick preview of an image, use the
+.B \-grayscale
+and/or
+.B \-scale
+switches.
+.B \-grayscale \-scale 1/8
+is the fastest case.
+.PP
+Several options are available that trade off image quality to gain speed.
+.B \-fast
+turns on the recommended settings.
+.PP
+.B \-dct fast
+and/or
+.B \-nosmooth
+gain speed at a small sacrifice in quality.
+When producing a color-quantized image,
+.B \-onepass \-dither ordered
+is fast but much lower quality than the default behavior.
+.B \-dither none
+may give acceptable results in two-pass mode, but is seldom tolerable in
+one-pass mode.
+.PP
+If you are fortunate enough to have very fast floating point hardware,
+\fB\-dct float\fR may be even faster than \fB\-dct fast\fR.  But on most
+machines \fB\-dct float\fR is slower than \fB\-dct int\fR; in this case it is
+not worth using, because its theoretical accuracy advantage is too small to be
+significant in practice.
+.SH ENVIRONMENT
+.TP
+.B JPEGMEM
+If this environment variable is set, its value is the default memory limit.
+The value is specified as described for the
+.B \-maxmemory
+switch.
+.B JPEGMEM
+overrides the default value specified when the program was compiled, and
+itself is overridden by an explicit
+.BR \-maxmemory .
+.SH SEE ALSO
+.BR cjpeg (1H),
+.BR jpegtran (1H),
+.BR rdjpgcom (1H),
+.BR wrjpgcom (1H)
+.br
+.BR ppm (5),
+.BR pgm (5)
+.br
+Wallace, Gregory K.  "The JPEG Still Picture Compression Standard",
+Communications of the ACM, April 1991 (vol. 34, no. 4), pp. 30-44.
+.SH AUTHOR
+Independent JPEG Group
+.SH BUGS
+Arithmetic coding is not supported for legal reasons.
+.PP
+To avoid the Unisys LZW patent,
+.B djpeg
+produces uncompressed GIF files.  These are larger than they should be, but
+are readable by standard GIF decoders.
+.PP
+Still not as fast as we'd like.

package/libnbis/nbis_arm64_darwin/man/man1/djpegb.1

@@ -0,0 +1,140 @@
+.\" @(#)djpegb.1 2008/10/02 NIST
+.\" I Image Group
+.\" Craig Watson and Michael D. Garris
+.\"
+.TH DJPEGB 1G "02 October 2008" "NIST" "NBIS Reference Manual"
+.SH NAME
+djpegb \- decompresses a Baseline JPEG (JPEGB) grayscale or color image.
+.SH SYNOPSIS
+.B djpegb
+.I <outext>
+.I <image file>
+.RS 7
+[\fB-raw_out\fR [\fB-nonintrlv\fR]]
+
+.SH DESCRIPTION
+.B Djpegb
+takes as input a file containing a Baseline JPEG (JPEGB) compressed
+grayscale or color image.  Once read into memory, the lossy-compressed
+pixmap is decoded and reconstructed using the Independent JPEG Group's
+(IJG) library for Baseline JPEG.  
+
+Upon completion, two different output image file formats are possible,
+a NIST IHead file (the default) or a raw pixmap file (specified by the
+\fB-raw_out\fR flag).  In addition, a specially formatted text
+file, called a NISTCOM, is created with extension ".ncm".  The NISTCOM
+file contains relevant image attributes associated with the decoded
+and reconstructed output image.
+(See NISTCOM OUTPUT below.)
+
+.SH OPTIONS
+All switch names may be abbreviated; for example,
+\fB-raw_out\fR may be written \fB-r\fR.
+.TP
+.I <outext>
+the extension of the decompressed output file.
+To construct the output filename, \fBdjpegb\fR takes the
+input filename and replaces its extension with the one
+specified here.
+.TP
+.I <image file>
+the input JPEGB file to be decompressed.
+.TP
+.B -raw_out
+specifies that the decoded and reconstructed image should be
+stored to a raw pixmap file.
+.TP
+.B -nonintrlv
+specifies that the color components in the reconstructed image should
+be organized into separate component planes.  The \fB-raw_out\fR flag
+must be used with this option, because the IHead format only supports
+interleaved color pixels.  (See INTERLEAVE OPTIONS below.)
+.TP
+\fB-version
+\fRPrint ANSI/NIST stardand and NBIS software version.
+
+.SH INTERLEAVE OPTIONS
+For example, given an RGB image, its color
+components 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, \fBdjpegb\fR uses interleaved
+color component pixels in the reconstructed output image.
+Note that all color IHead images must be interleaved.
+
+.SH NISTCOM OUTPUT
+Upon successful completion, \fBdjpegb\fR, creates a specially
+formatted text file called a NISTCOM file.
+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.  These attributes are collected and merged from two
+different sources to represent the history and condition of
+the resulting reconstructed image.  The first source is from an
+optional NISTCOM comment block inside the JPEGB-encoded input file.
+This comment block can be used to hold user-supplied attributes.
+The JPEGB encoder, \fBcjpegb\fR, by convention inserts one of these
+comment blocks in each compressed output file it creates.
+(The utility \fBrdjpgcom\fR can be used to scan a JPEG file for
+any and all comment blocks.)
+The second source of attributes comes from the decompression
+process itself.  In general, attribute values from this second
+source are given precedence over those from the first.
+
+The NISTCOM output filename is constructed by combining the
+basename of the input JPEGB file with the extension ".ncm".
+By creating the NISTCOM file, relevant attributes associated
+with the decoded and reconstructed image are retained and
+easily accessed.  This is especially useful when dealing with
+raw pixmap files and creating image archives.  The following
+is an example NISTCOM generated by \fBdjpegb\fR:
+
+.RS
+NIST_COM 10
+.br
+PIX_WIDTH 768
+.br
+PIX_HEIGHT 1024
+.br
+PIX_DEPTH 24
+.br
+PPI -1
+.br
+LOSSY 1
+.br
+COLORSPACE RGB
+.br
+NUM_COMPONENTS 3
+.br
+HV_FACTORS 1,1:1,1:1,1
+.br
+INTERLEAVE 1
+
+.SH EXAMPLES
+From \fItest/imgtools/execs/djpegb/djpegb.src\fR:
+.PP
+.RS
+.B % djpegb raw face24.jpb -r
+.br
+decompresses a JPEGB-encoded RGB face image and stores
+the reconstructed image to a raw pixmap file.  Note the
+NISTCOM file, \fBface24.ncm\fR, is also created.
+
+.SH SEE ALSO
+.BR cjpegb (1G),
+.BR dpyimage (1G),
+.BR intr2not (1G),
+.BR jpegtran (1H),
+.BR not2intr (1G),
+.BR rdjpgcom (1H),
+.BR wrjpgcom (1H)
+
+.SH AUTHOR
+NIST/ITL/DIV894/Image Group

package/libnbis/nbis_arm64_darwin/man/man1/djpegl.1

@@ -0,0 +1,143 @@
+.\" @(#)djpegl.1 2008/10/02 NIST
+.\" I Image Group
+.\" Craig Watson and Michael D. Garris
+.\"
+.TH DJPEGL 1G "02 October 2008" "NIST" "NBIS Reference Manual"
+.SH NAME
+djpegl \- decompresses a Lossless JPEG (JPEGL) grayscale or color image.
+.SH SYNOPSIS
+.B djpegl
+.I <outext>
+.I <image file>
+.RS 7
+[\fB-raw_out\fR [\fB-nonintrlv\fR]]
+
+.SH DESCRIPTION
+.B Djpegl
+takes as input a file containing a Lossless JPEG (JPEGL) compressed
+grayscale or color image.  Once read into memory, the compressed
+pixmap is decoded and reconstructed to its original condition
+prior to compression.
+
+Upon completion, two different output image file formats are possible,
+a NIST IHead file (the default) or a raw pixmap file (specified by the
+\fB-raw_out\fR flag).  In addition, a specially formatted text
+file, called a NISTCOM, is created with extension ".ncm".  The NISTCOM
+file contains relevant image attributes associated with the decoded
+and reconstructed output image.
+(See NISTCOM OUTPUT below.)
+
+.SH OPTIONS
+All switch names may be abbreviated; for example,
+\fB-raw_out\fR may be written \fB-r\fR.
+.TP
+.I <outext>
+the extension of the decompressed output file.
+To construct the output filename, \fBdjpegl\fR takes the
+input filename and replaces its extension with the one
+specified here.
+.TP
+.I <image file>
+the input JPEGL file to be decompressed.
+.TP
+.B -raw_out
+specifies that the decoded and reconstructed image should be
+stored to a raw pixmap file.
+.TP
+.B -nonintrlv
+specifies that the color components in the reconstructed image should
+be organized into separate component planes.  The \fB-raw_out\fR flag
+must be used with this option, because the IHead format only supports
+interleaved color pixels.  (See INTERLEAVE OPTIONS below.)
+.TP
+\fB-version
+\fRPrint ANSI/NIST stardand and NBIS software version.
+
+.SH INTERLEAVE OPTIONS
+For example, given an RGB image, its color
+components 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, \fBdjpegl\fR uses interleaved
+color component pixels in the reconstructed output image.
+Note that all color IHead images must be interleaved.
+
+.SH NISTCOM OUTPUT
+Upon successful completion, \fBdjpegl\fR, creates a specially
+formatted text file called a NISTCOM file.
+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.  These attributes are collected and merged from two
+different sources to represent the history and condition of
+the resulting reconstructed image.  The first source is from an
+optional NISTCOM comment block inside the JPEGL-encoded input file.
+This comment block can be used to hold user-supplied attributes.
+The JPEGL encoder, \fBcjpegl\fR, by convention inserts one of these
+comment blocks in each compressed output file it creates.
+(The utility \fBrdjpgcom\fR can be used to scan a JPEG file for
+any and all comment blocks.)
+The second source of attributes comes from the decompression
+process itself.  In general, attribute values from this second
+source are given precedence over those from the first.
+
+The NISTCOM output filename is constructed by combining the
+basename of the input JPEGL file with the extension ".ncm".
+By creating the NISTCOM file, relevant attributes associated
+with the decoded and reconstructed image are retained and
+easily accessed.  This is especially useful when dealing with
+raw pixmap files and creating image archives.  The following
+is an example NISTCOM generated by \fBdjpegl\fR:
+
+.RS
+NIST_COM 9
+.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 1
+
+.SH EXAMPLES
+From \fItest/imgtools/execs/djpegl/djpegl.src\fR:
+.RS
+.PP
+.B % djpegl raw finger.jpl -r
+.br
+decompresses a JPEGL-encoded grayscale fingerprint image and stores
+the reconstructed image to a raw pixmap file.  Note the
+NISTCOM file, \fBfinger.ncm\fR, is also created.
+.PP
+.B % djpegl raw face.jpl -r
+.br
+decompresses a JPEGL-encoded RGB face image and stores
+the reconstructed image to a raw pixmap file.  Note the
+NISTCOM file, \fBface.ncm\fR, is also created.
+
+.SH SEE ALSO
+.BR cjpegl (1G),
+.BR dpyimage (1G),
+.BR intr2not (1G),
+.BR not2intr (1G),
+.BR rdjpgcom (1H),
+.BR wrjpgcom (1H)
+
+.SH AUTHOR
+NIST/ITL/DIV894/Image Group

package/libnbis/nbis_arm64_darwin/man/man1/djpeglsd.1

@@ -0,0 +1,158 @@
+.\" @(#)djpeglsd.1 2008/10/02 NIST
+.\" I Image Group
+.\" Craig Watson and Michael D. Garris
+.\"
+.TH DJPEGLSD 1G "02 October 2008" "NIST" "NBIS Reference Manual"
+.SH NAME
+djpeglsd \- decompresses a grayscale image that was compressed
+using the old Lossless JPEG compression distributed with Special
+Databases 4, 9, 10, and 18. \fBCjpegl\fR should be used in the
+future to Lossless JPEG (JPEGL) compress images.
+.SH SYNOPSIS
+.B djpeglsd
+.I <outext>
+.I <image file>
+.RS 7
+[\fB-sd #\fR] [\fB-raw_out\fR]
+
+.SH DESCRIPTION
+.B Djpeglsd
+takes as input a file containing a grayscale image that was compressed
+with the old Lossless JPEG (JPEGLSD).  Specifically the version that
+is included on the CDROMs with Special Databases 4, 9, 10, and 18.
+Once read into memory, the compressed pixmap is decoded
+and reconstructed to its original condition prior to compression.
+\fBCjpegl\fR should be used for any future Lossless JPEG compression
+of images.
+
+Upon completion, two different output image file formats are possible,
+a NIST IHead file (the default) or a raw pixmap file (specified by the
+\fB-raw_out\fR flag).  In addition, a specially formatted text
+file, called a NISTCOM, is created with extension ".ncm".  The NISTCOM
+file contains relevant image attributes associated with the decoded
+and reconstructed output image. If given a special database number,
+\fBdjpeglsd\fR will put all the important class, sex, age, and file
+history information, that may exist for that database, in the NISTCOM
+file.
+(See NISTCOM OUTPUT below.)
+
+.SH OPTIONS
+All switch names may be abbreviated; for example,
+\fB-raw_out\fR may be written \fB-r\fR.
+.TP
+.I <outext>
+the extension of the decompressed output file.
+To construct the output filename, \fBdjpeglsd\fR takes the
+input filename and replaces its extension with the one
+specified here.
+.TP
+.I <image file>
+the input JPEGLSD file to be decompressed.
+.TP
+.B -sd #
+Specify that the input image is from NIST Special Database #.
+.TP
+.B -raw_out
+specifies that the decoded and reconstructed image should be
+stored to a raw pixmap file.
+.TP
+\fB-version
+\fRPrint ANSI/NIST stardand and NBIS software version.
+
+.SH NISTCOM OUTPUT
+Upon successful completion, \fBdjpeglsd\fR, creates a specially
+formatted text file called a NISTCOM file.
+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. These attributes are collected from information
+about the decompressed image. Detailed attributes are
+collected if the \fI-sd #\fR flag is used.
+
+The NISTCOM output filename is constructed by combining the
+basename of the input JPEGLSD file with the extension ".ncm".
+By creating the NISTCOM file, relevant attributes associated
+with the decoded and reconstructed image are retained and
+easily accessed.  This is especially useful when dealing with
+raw pixmap files and creating image archives.  The following
+are example NISTCOMs generated by \fBdjpeglsd\fR for SD9 and
+SD18 images (The highlighted items are attributes specific to
+that database.):
+
+.RS
+NIST_COM 12
+.br
+.B SD_ID 9
+.br
+.B HISTORY f0000771.pct ac/dm_fpw:20 tape9.n1125012.01 4096x1536
+.br
+.B FING_CLASS W
+.br
+.B SEX f
+.br
+.B SCAN_TYPE i
+.br
+PIX_WIDTH 832
+.br
+PIX_HEIGHT 768
+.br
+PIX_DEPTH 8
+.br
+PPI 500
+.br
+LOSSY 0
+.br
+COLORSPACE GRAY
+.br
+.br
+
+NIST_COM 12
+.br
+.B SD_ID 18
+.br
+.B HISTORY f00117_1.pct
+.br
+.B SEX m
+.br
+.B AGE 26
+.br
+.B FACE_POS f
+.br
+PIX_WIDTH 592
+.br
+PIX_HEIGHT 448
+.br
+PIX_DEPTH 8
+.br
+PPI 500
+.br
+LOSSY 0
+.br
+COLORSPACE GRAY
+.br
+
+.SH EXAMPLES
+From \fItest/imgtools/execs/djpeglsd/djpeglsd.src\fR:
+.RS
+.PP
+.B % djpeglsd raw sd04.old -sd 4  -r
+.br
+.B % djpeglsd raw sd09.old -sd 9  -r
+.br
+.B % djpeglsd raw sd10.old -sd 10 -r
+.br
+.B % djpeglsd raw sd18.old -sd 18 -r
+.br
+decompresses JPEGLSD-encoded images from the Special Databases
+and stores the reconstructed images to a raw pixmap files.  Note the
+NISTCOM files, \fBsd04.ncm\fR, \fBsd09.ncm\fR, \fBsd10.ncm\fR, and
+\fBsd18.ncm\fR, are also created.
+
+.SH SEE ALSO
+.BR cjpegl (1G),
+.BR djpegl (1G),
+.BR dpyimage (1G),
+
+.SH AUTHOR
+NIST/ITL/DIV894/Image Group