readme w e winkler 990226 9a
[ Edited Abowd and Vilhuber, 2005-04-07 ]
This example contains executables (programs) that can be run on a
Itanium running Linux. The original version was for DOS/Windows, and is
still available. Differences between the versions are pointed out
below. If you wish to run on other computers (f.i. Mac OS X), you will
need to recompile the programs (source code is available in
winkler-mt_src.zip, 64-bit clean-code is available from John Abowd or
To use this example, you will need to know how to copy and rename
files, to use a text editor, and to run programs in the Linux or MS-DOS
shell under Windows 95, 98, or NT. Your mileage in the GUI may vary...
See the Tips and Tricks
page for help on working on Linux systems.
to run gdriver
The purpose of the program is to put a standardized address and
name at the end of a file.
The program has three main inputs.
- gives the name of the input file.
- gives the start location and length of the
name field, the start location and length of the address field,
the logical record length (number of column positions) in the input
- name of input file. Make sure that all records
have the same length.
The name standardization subportion has a large number of tables that
need to be present in the directory where gdriver is run:
The address standardization subportion has three
tables that must be present in the directory where gdriver
Also, you need the file initfile.dat
to be present. It has three lines. Each line corresponds to the name of
the appropriate input table in the order above.
A summary output
of the name standardization process.
The summary file
also gives the locations of the standardized components of the address
of the name.
output file. The standardized address is in the first set of
columns after the original main file and the standardized name is in
second set of columns.
Secondary output will occur when names of
Jane and John Smith are processed (in this example, the file will be
Running the standardizer
- Unzip the contents of standardizer-clean-data.zip.
will create a sub-directory called "standardizer". This is the input
data and the auxiliary data.
- Unzip the appropriate
standardizer for your platform according to
the table below.
These will expand into the same subdirectory.
- Ensure all the primary,
data files are present.
- Click on gdriver,
- open a command shell
(Start->Run... and type 'cmd'
followed by ENTER)
- navigate to that
directory ('cd Desktop\standard')
- Run the standardizer by
typing 'gdriver'. You will get
additional diagnostic output that gets lost if you double-click on the
- Analyze the output.
Possibly modify the input files to see if
the standardizer can handle your specific input files.
Compiling from source
Andrey Baliakin has cleaned up some of Bill Winkler's original code.
The source code is known to compile using GCC, your mileage with other
compilers and on other systems may vary. Some problems with addressing
are known on ia64 systems.
- Download and untar the sources
- Edit the makefile. The default compiler is GCC, change the
options to reflect your setup
- Test the binary. You'll want standardizer-clean-data.zip.
This contains all pattern files, and some very simple example data and
configuration files that you can use to see if your compiled version
- Please submit any new platforms not mentioned above to us, so we
can provide them to the wider community.