NavRegression

This directory contains Stuart's navigation regression perl scripts,
modified to perform an A-B comparison between two versions of
StingerNavPC. This regression tool can be used to validate any
position engine changes (i.e. changes to PF task in Stinger, or
related changes in the NM task) to make sure that nothing has been
broken.

To run the regression tool, check out NavRegression to a Linux machine
that has access to the engineering server proton.eng.trimble.com via
the NFS mount /net/proton.

Edit the script compareAB.pl to specify the location of the reference
and test versions of StingerNavPC, as well as recently compiled
versions of t01 and viewdat.

Then run the following command:

  perl compareAB.pl list.txt > doit.sh; ./doit.sh

The file list.txt contains a list of all the regression files. You can
also run the command

  perl compareAB.pl veryshortlist.txt > doit.sh; ./doit.sh

to test whether the regression system is set up correctly. The file
veryshortlist.txt contains only one file from the regression
system. Similarly, you can create your own text file containing a list
of T02 files to analyze. 

On some platforms, you may need to first run the commands
  touch doit.sh
  chmod u+x doit.sh
so that the doit.sh file is executable, before running the perl script
described above.

If you create a set of new files that you find useful in developing a
new set of software, please contact Stuart Riley, and provide him with
the files to put into his NavRegression database.

If you change the path pointing to the t01 project or viewdat, make
sure you remember to change the paths in all of the perl files, not
just compareAB.pl.

When you run the regression system, the best way to run it is to use a
clean checkout of StingerNavPC as the "base" version of StingerNavPC,
and then apply your edits to the same clean checkout to create the
"test" version of StingerNavPC. This method ensures that any
differences in the results between base and test are *definitely* due
to the changes you introduced. It is often useful to use a local
source control system such as git, hg or bzr to create two branches --
one base branch and one test branch, in the same StingerNavPC
directory for the base and test versions of StingerNavPC.

To look at the results, look at the files:
  0002-Results/Auto/index.html
  0002-Results/SBAS/index.html
  0002-Results/SBASPlus/index.html
  0002-Results/SBASPlusWithSBASObs/index.html

Some links in the generated index.html files are dead links -- they
point to locations that don't exist. They are relative paths to
Stuart's original NavRegression directory. Stuart's original scripts
are located in
  /net/proton/mnt/data_drive/NavRegression/
This directory can also be viewed at:
  http://proton.eng.trimble.com/Kalman/
The top level script in that directory is doit.pl.

TODO: Generate the links to point to Stuart's NavRegression database
instead of local relative paths.