nbis-wrapper-js 0.0.1

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

@@ -0,0 +1,52 @@
+.\" @(#)mlpfeats.1 2008/10/02 NIST
+.\" I Image Group
+.\" Craig I. Watson & C. L. Wilson
+.\"
+.TH MLPFEATS 1B "02 October 2008" "NIST" "NBIS Reference Manual"
+.SH NAME
+mlpfeats \- converts PCASYS formatted feature files into
+the format compatible with the mlp command line function.
+.SH SYNOPSIS
+.B mlpfeats
+.I <feats_file> <class_file> <mlp_feats_file>
+.SH DESCRIPTION
+.B Mlpfeats
+is used to convert a PCASYS formatted feature
+file from the lintran function into the format used by the
+mlp command. PCASYS keeps the feature file and class file in
+separate files and mlp stores them in a single file with
+different header information format. At this point it was decided to
+just convert the format from PCASYS features to mlp features
+file format, any future release may try and resolve this
+problem into a single format.
+.SH OPTIONS
+.TP
+.I <feats_file>
+The PCASYS formatted features file. (Usually the output of
+\fBlintran\fR.)
+.TP
+.I <class_file>
+The PCASYS formatted class file.
+.TP
+.I <mlp_feats_file>
+The MLP features file to be written, containing the PCASYS formatted
+feature and class files merged into a single MLP formatted file.
+.TP
+\fB-version
+\fRPrint ANSI/NIST stardand and NBIS software version.
+
+.SH EXAMPLE(S)
+From \fItest/pcasys/execs/mlpfeats/mlpfeats.src\fR:
+.PP
+.RS
+.B % mlpfeats ../lintran/fv1-9mlp.kls ../../data/oas/fv1-9.cls fv1-9mlp.kls
+.br
+Converts the feature file from the PCASYS file format to the mlp
+data file format (combines class and features into a single file.)
+It is unfortunate that two file formats exist but for now it is
+easier to keep both formats around.
+.SH "SEE ALSO"
+lintran (1B), mlp (1B)
+
+.SH AUTHOR
+NIST/ITL/DIV894/Image Group

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

@@ -0,0 +1,131 @@
+.\" @(#)nfiq.1 2009/01/08 NIST
+.\" I Image Group
+.\" Michael Garris
+.\" Elham Tabassi
+.\" Modified by Joseph Konczal - corrected '-b' to '-d', added record selectors
+.\" JCK added missing '-o', improved explanation of record selection options
+.\"
+.TH NFIQ 1D "08 January 2009" "NIST" "NBIS Reference Manual"
+.SH NAME
+nfiq \- evaluates a fingerprint image and returns a quality value for
+the image on a scale of 1 (highest quality) to 5 (lowest quality).
+When multiple fingerprint images are selected from an ANSI/NIST file,
+the record number and fgp number are printed before the quality value.
+.SH SYNOPSIS
+.B nfiq
+.RB [ \-dv ]
+.RB [ \-raw
+.IR w,h,d[,ppi] ]
+.RB [ \-f
+.IR FGP[:IMP] ]
+.RB [ \-i
+.IE IMP ]
+.RB [ \-n
+.IR IDC ]
+.RB [ \-o ]
+.RB [ \-t
+.IR LRT ]
+.RB [ \-q
+.IR NQM ]
+.RB [ \-r
+.IR rec-sel-in-file ]
+.RB [ \-w
+.IR rec-sel-out-file ]
+.I fing-image-in
+.RI [ ANSI/NIST-out ]
+.SH DESCRIPTION
+.B Nfiq
+takes as input a file containing a fingerprint image. The image file can
+be in ANSI/NIST, NIST IHEAD, or raw format or compressed with WSQ, baseline 
+JPEG, or lossless JPEG compression. \fBNfiq\fR uses the image maps generated by
+\fBmindtct\fR to create a feature vector for the image which is passed to
+an multi-layer perceptron (MLP) neural network.  The MLP NN returns an
+activation value that is used to rank the images quality on a scale of
+1 (highest quality) to 5 (lowest quality).
+
+.SH OPTIONS
+.TP
+\fB-d \fIdefault\fR
+Prints the image quality value (1-5) to standard output.  This is also the default if neither \fB-d\fR nor \fB-v\fR are specified.  When multiple images are present in an ANSI/NIST file, the record number and FGP are printed out before the image quality value.
+.TP
+\fB-v \fIverbose\fR
+Prints all the feature vectors, image quality value (1-5) and neural
+network activiation values (0.0-1.0) to standard output.
+.TP
+\fB-o \fIOld behavior\fR
+Calculate and print values for only the first grayscale fingerprint
+record in an ANSI/NIST file.
+.TP
+\fB-raw \fIraw image\fR
+Calculate the NFIQ score from a raw image file.
+.TP
+Record Selection Options
+The folowing options are used to select particular records from an
+ANSI/NIST file that match the specified characteristics.  Multiple
+specifications for one option are treated as alternatives (logical OR).
+Multiple different types of selectors are all required to be true of a
+particular record in order for it to be selected (logical AND).  See
+.BR record_selector (1F)
+for details.
+\fB-raw \fIattributes\fR
+Specifies that \fIfing-image-in\fR is a raw image file and its attributes are width,height,depth[,ppi].  PPI is assumed to be 500 if omitted.
+.P
+\fB-f \fIfinger position (FGP), and optional impression type (IMP)\fR
+.br
+\fB-i \fIimpression type (IMP)\fR
+.br
+\fB-n \fIimage designation character (IDC) \fR(actually a number from 0 to 255)
+.br
+\fB-t \fIlogical record type (LRT)\fR
+.br
+\fB-q \fINIST fingerprint image quality metric (NQM)\fR
+.br
+\fB-r \fIread selectors from a file\fR
+.br
+\fB-w \fIwrite selectors to a file\fR
+.TP
+.I fing-image-in
+A file containing the input fingerprint image(s) to be evaluated.
+.TP
+.I ANSI/NIST-out
+When the input is an ANSI/NIST file and an output file name is
+specified, the fingerprint quality results will be written into NQM
+fields in the appropriate records in the output file.  Type-4
+fingerprint records, except for latent impressions, will be converted
+to Type-14 in order to allow the addition of an NQM field.  Any NQM
+fields already present will be overwritten with the new results.
+.TP
+\fB-version
+\fRPrint ANSI/NIST stardand and NBIS software version.
+
+.SH EXAMPLES
+.B % nfiq ../../data/a011_02_02.wsq
+.br
+prints the image quality value (1-5) to standard output.
+
+.B % nfiq -v ../../data/a011_02_02.wsq
+.br
+prints all the feature vectors, image quality value (1-5) and neural
+network activiation values (0.0-1.0) to standard output.
+
+.B % nfiq ../../data/a001.an2 a001-nfq.an2
+copies the input file to a001-nf1.an2, adding NQM values where
+appropriate, and converting Type-4 records to Type-14 as required to
+allow for addition of the NQM field.
+
+.B % nfiq -fi:r ../../data/a001.an2
+prints the record number, finger number, and image quality value for
+all rolled index finger records to standard output.
+
+.B % nfiq -raw 320,528,8 ../../data/a011_02.raw
+.br
+prints the image quality value (1-5) for a raw image file with the specified 
+attributes to standard output
+
+.SH SEE ALSO
+.BR mindtct (1C),
+.BR bozorth3 (1E),
+.BR record_selector (1F)
+
+.SH AUTHOR
+NIST/ITL/DIV894/Image Group

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

@@ -0,0 +1,232 @@
+.\" @(#)nfseg.1 2008/02/13 NIST
+.\" I Image Group
+.\" Craig Watson
+.\" Updated by Joseph Konczal
+.\"
+.TH NFSEG 1A "19 November 2009" "NIST" "NBIS Reference Manual"
+.SH NAME
+nfseg \- Segments multiple finger plain impressions into individual
+fingers or removes white space from single finger rolled/plain impressions
+isolating just the fingerprint portion of the image.
+.SH SYNOPSIS
+\fBnfseg \fI[options] <ANSI/NIST in> [<ANSI/NIST out>]\fR
+.RS 9
+\fB-v
+.br
+\fB-b \fI<BTHR_ADJ>\fR
+.br
+\fB-r
+.br
+\fB-c \fI<COMP_SEG>\fR
+.br
+\fB-R
+.RE
+or
+.br
+\fBnfseg \fI<FGP> <BTHR_ADJ> <ROT_SEARCH> <COMP_SEG> <ROT_SEG> <in file>\fR
+.br
+or
+.br
+.B nfseg -version
+
+.SH DESCRIPTION
+\fBNfseg\fP takes a four finger plain impression fingerprint image
+(FGP finger positions 13 "right hand", 14 "left hand", or 0 "Unknown
+Hand") and segments it into four individual fingerprint images. For
+two-thumb images (FGP 15) \fBnfseg\fR segments the input image into
+two individual flat thumb images (FGP 11 and 12).  For single finger
+images (FGP 1-12) \fBnfseg\fR can be used to isolate the fingerprint
+in the image by removing white space around the fingerprint.
+
+The input image can be in ANSI/NIST format, WSQ compressed format,
+baseline JPEG, or lossless JPEG.  \fBNfseg\fR will output the results
+to WSQ compressed files (.wsq at 5:1 or 15:1 compression ratio),
+lossless JPEG (.jpl) or RAW pixel data (.raw).  \fBNfseg\fR can also
+rotate the segmented image to a vertical position or leave it in its
+original position.  Output filenames are derived from the input
+file name and written into the current working directory. They have an
+underscore and finger number appended to the base name.  If the
+fingerprint is left in its original position all pixels in the image
+outside the fingerprint bounding box are set to white.
+
+If the input is an ANSI/NIST file, the other parameters can be
+determined automatically, or overridden by the user.  The binarization
+threshold will be adjusted for images where the impression type
+inidcates a non-live scan, assuming scanned paper-and-ink, and not
+adjusted for live scan images.  Rotation will default to none.  Also,
+an output file may be specified, which will have any Type-4 images
+converted to Type-14, and the results will be inserted in a SEQ or
+ASEQ field depending on whether the search is unrotated or rotated.
+If an ANSI/NIST output file is specified, output of individual image
+files is normally suppressed, but it can be turned back on by
+specifying the type of compression to use with the -c option.  Output
+files generated in this mode of operation also include an underscore
+and the record number, before the finger number, in order to ensure
+none of the files have the same name.
+
+.SH OPTIONS
+.TP
+\fB-v\fR
+turns on verbose output
+
+.TP
+.I <FGP>
+indicates the finger position of the input image.
+
+.RS
+\fB1-5\fR - right hand rolled impressions
+.br
+\fB6-10\fR - left hand rolled impressions
+.br
+\fB11\fR - right thumb plain impression
+.br
+\fB12\fR - left thumb plain impression
+.br
+\fB13\fR - right hand four finger plain impression (tend to be rotated left of
+vertical)
+.br
+\fB14\fR - left hand four finger plain impression (tend to be rotated right of
+vertical)
+.br
+\fB15\fR - both thumbs plain impression
+.br
+\fB0\fR - unknown hand (for four finger plain impression will search all
+angles and make guess at hand based on rotation angle)
+.br
+
+For segmentation purposes \fB1-12\fR are treated the same. Plain impressions
+\fB13-14\fR are treated similarly, the exception being the angles of rotation
+that are searched for the four fingers. Unknown type \fB00\fR is searched for
+four finger plain impressions over the whole range of angles used in both
+left and right hand images. The algorithm will make a guess at left or right
+hand based on the rotation angle of the fingerprints.
+.RE
+.TP
+\fB-b\fR or \fI<BTHR_ADJ>\fR Adjust binarization threshold to improve
+segmentation of low contrast images.  The \fB-b\fR option overrides
+the automatically determined value based on the impression type in the
+ANSI/NIST input file.
+
+.RS
+\fB0\fR - No threshold adjustment.
+.br
+\fB1\fR - Adjust binarization threshold higher.
+.RE
+.TP
+\fB-r\fR or \fI<ROT_SEARCH>\fR
+Allows user to search the image for rotated fingerprints (ie. 2" data) or
+assume the fingerprints are vertical (ie. 3" data).
+
+.RS
+\fB0\fR - Assume fingerprints are not rotated.
+.br
+\fB1\fR - Assume fingerprints may be rotated in the image.
+.RE
+.TP
+\fB-c\fR or \fI<COMP_SEG>\fR 
+indicates the type of compression for the
+segmented images output, and causes the images to be output even if an
+ANSI/NIST output file is specified.
+
+ansi/.RS
+\fB0\fR - Lossless JPEG
+.br
+\fB1\fR - WSQ 5:1
+.br
+\fB2\fR - WSQ 15:1
+.br
+\fB3\fR - RAW pixel data
+.RE
+.TP
+\fB-R\fR or \fI<ROT_SEG>\fR
+indicates if output image is to be rotated to vertical position.
+
+.RS
+\fB0\fR - Do not rotate
+.br
+\fB1\fR - Rotate to vertical
+.RE
+.TP
+\fB-o \fI<ansi_nist_output_file>\fR 
+indicates an ANSI/NIST output file name to which SEG or ASEG records
+are added, and output of image files is suppressed
+.TP
+\fI<file>\fR or \fI<ansi_nist_file>\fR
+the input file to be segmented.
+
+.TP
+\fB-version
+\fRPrint ANSI/NIST standard and NBIS software version.
+
+.SH NFSEG OUTPUT
+For each output image, \fBnfseg\fR will print a line of text to standard
+output as follows:
+
+.I <filname>
+->
+.I <error flag> <sw> <sh> <sx> <sy> <theta>
+
+.RS
+.I <filename>
+the name of the segmented output file.
+.TP
+.I <error flag>
+a flag set if the segmented image does not meet certain minimum requirements.
+
+.RS
+\fB0\fR - no errors
+.br
+\fB1\fR - segmented image width is less than "FING_WIDTH_MIN" parameter
+in nfseg.h
+.br
+\fB2\fR - segmented image height is less than "FING_HEIGHT_MIN" parameter
+in nfseg.h
+.br
+\fB3\fR - spacing between adjacent fingers was less than "FING_SPACE_MIN"
+parameter in nfseg.h
+.br
+\fB4\fR - spacing between adjacent fingers was more than "FING_SPACE_MAX"
+parameter in nfseg.h
+
+Error flags 3 and 4 usually indicate the image did not segment correctly.
+.SH
+.RS
+.TP
+.I <sw> <sh>
+the width and height of the segmented image file
+
+.TP
+.I <sx> <sy>
+where the center of the segmented image was located at in the original
+four finger plain imression image.
+
+.TP
+.I <theta>
+rotation angle of the fingers in the four finger plain impression image,
+positive values are left of vertical and negative values are right.
+
+.SH EXAMPLES
+From \fItest/nfseg/execs/nfseg/nfseg.src\fR:
+.PP
+.RS
+.B % nfseg 13 1 1 1 0 a011_13.wsq
+.br
+segments the image into four single finger plain images. Creates
+the output files: a011_13_0[2-5].wsq
+
+.SH BUGS
+Ignores segmentation error flags when writing results to an
+ANSI/NIST file.
+
+Perhaps a user defined record should be written telling where the SEG
+or ASEG data came from.
+
+.SH SEE ALSO
+.BR dwsq (1G),
+.BR djpegl (1G),
+.BR an2ktool (1F),
+.BR txt2an2k (1F),
+.BR nfiq (1D)
+
+.SH AUTHOR
+NIST/ITL/DIV894/Image Group

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

@@ -0,0 +1,150 @@
+.\" @(#)not2intr.1 2008/10/02 NIST
+.\" I Image Group
+.\" Craig Watson and Michael D. Garris
+.\"
+.TH NOT2INTR 1G "02 October 2008" "NIST" "NBIS Reference Manual"
+.SH NAME
+not2intr \- converts an image comprised of non-interleaved color
+component planes to an image with interleaved color component
+pixels.
+
+.SH SYNOPSIS
+.B not2intr
+.I <outext>
+.I <image file>
+.I <\fIw\fR,\fIh\fR,\fId\fR,[\fIppi\fR]>
+.RS 9
+[\fB-raw_out\fR]
+.br
+[\fB-YCbCr\fR \fIH0\fR,\fIV0\fR:\fIH1\fR,\fIV1\fR:\fIH2\fR,\fIV2\fR]
+
+.SH DESCRIPTION
+.B Not2intr
+takes as input a raw pixmap file containing an uncompressed image
+comprised of non-interleaved color component planes and converts the image
+to interleaved color component pixels.  This utility requires there be
+three color components in the input image.  Two output file formats are
+possible, a NIST IHead file (the default) or a raw pixmap file
+(specified by the \fB-raw_out\fR option).
+
+For example, the pixels of an RGB color image are interleaved
+when a pixel's R, G, and B 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 utility \fBintr2not\fR converts interleaved
+to non-interleaved color components.
+
+It is possible that the component planes of an input YCbCr image
+have been previously downsampled.  If so, the \fB-YCbCr\fR flag
+must be included on the command line, listing the appropriate component
+plane downsampling factors.  By default, this utility assumes
+no downsampling.  YCbCr image results should always be explicitly
+stored in a raw pixmap file, because the IHead format only supports
+RGB pixels.  (See YCbCr OPTIONS 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 output file.
+To construct the output filename, \fBnot2intr\fR takes the
+input filename and replaces its extension with the one
+specified here.
+.TP
+.I <image file>
+the input raw pixmap file containing the color image to be converted.
+.TP
+<\fIw\fR,\fIh\fR,\fId\fR,[\fIppi\fR]>
+the attributes of the input image in the 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 -raw_out
+specifies that the results should be stored to a raw pixmap file.
+.TP
+\fB-YCbCr\fR \fIH0\fR,\fIV0\fR:\fIH1\fR,\fIV1\fR:\fIH2\fR,\fIV2\fR
+indicates that a YCbCr color image is being input whose
+component planes have been previously downsampled.
+The \fB-raw_out\fR flag should always be used in conjunction with
+this option.
+(See YCbCr Options below.)
+.TP
+\fB-version
+\fRPrint ANSI/NIST stardand and NBIS software version.
+
+.SH YCbCr OPTIONS
+A common compression technique for YCbCr images is to downsample
+the Cb & Cr component planes.
+\fBNot2intr\fR can handle 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, \fBnot2intr\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
+
+indicates that there has been no downsampling of the Y
+component plane (4,4 are the largest X and Y factors listed);
+the Cb component plane has been downsampled in X and Y by a factor of 2
+(maximum factors 4 divided by current factors 2); and the Cr component
+plane has been 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.
+The utility \fBrgb2ycc\fR converts RGB pixmaps to the YCbCr
+colorspace, and it conducts downsampling of the resulting YCbCr
+component planes upon request.
+
+.SH EXAMPLES
+From \fItest/imgtools/execs/not2intr/not2intr.src\fR:
+.PP
+.RS
+.B % not2intr raw face.nin 768,1024,24 -r
+.br
+converts the non-interleaved RGB face image in a
+raw pixmap file into interleaved color pixels.
+
+.SH SEE ALSO
+.BR intr2not (1G),
+.BR rgb2ycc (1G)
+
+.SH AUTHOR
+NIST/ITL/DIV894/Image Group

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

@@ -0,0 +1,55 @@
+.\" @(#)oas2pics.1 2008/10/02 NIST
+.\" I Image Group
+.\" G. T. Candela & Craig I. Watson
+.\"
+.TH OAS2PICS 1B "02 October 2008" "NIST" "NBIS Reference Manual"
+.SH NAME
+oas2pics \- makes pictures of orientation arrays.
+.SH SYNOPSIS
+.B oas2pics
+.I <oasfile> <i_start> <i_finish outpics_dir> <verbose>
+.SH DESCRIPTION
+.B Oas2pics
+reads a specified segment of orientation arrays (oas) from a file,
+and makes IHead raster images depicting the oas.  This can be useful
+for testing whether oas are reasonable, and to find out about their
+characteristics.
+.SH OPTIONS
+.TP
+.I <oasfile>
+A PCASYS "matrix" file containing orientation arrays, with each row being
+one oa.  First dimension is number of oas in the file, and second
+dimension must be 1680 (the dimensionality of one oa). (Usually the
+output of \fBmkoas\fR.)
+.TP
+.I <i_start> <i_finish>
+The program makes pictures of the segment consisting of oas i_start
+through i_finish, numbering starting at 1.
+.TP
+.I <outpics_dir>
+The program makes image files in this directory.  (If the directory
+does not already exist, the program makes it.)  The files will
+have names i.pct where i goes from i_start through i_finish.
+.TP
+.I <verbose>
+If y, the program writes a progress message to stdout for each
+oa it is making a picture of.
+.TP
+\fB-version
+\fRPrint ANSI/NIST stardand and NBIS software version.
+
+.SH EXAMPLE(S)
+From \fItest/pcasys/execs/asc2bin/asc2bin.src\fR:
+.PP
+.RS
+.B % oas2pics ../../data/oas/fv1.oas 1 2 oaspics y
+.br
+Makes a set of images files (IHEAD format) so the user can
+see how the orientation arrays look and compare to the actual
+fingerprint image if desired. The files can be converted to JPEG
+format using the \fBcjegb\fR command.
+.SH "SEE ALSO"
+mkoas (1B), dpyimage (1G), cjpegb (1G)
+
+.SH AUTHOR
+NIST/ITL/DIV894/Image Group