Within the test the following three tasks are carried out:
cd refsys/$version
make test
Or, if you have problem with using the makefile you can run the test "manually":
cd refsys/$version/work
./runtest.tcl polycost/test
makedet.csh polycost/test/results.llk > polycost/test/results.det
eer.csh polycost/test/results.llk
It may be useful to redirect output to a file for later reference. This is done
differently with different shell programs. For example, if you are using C-shell
(csh or tcsh) you can do
make test >& work/polycost/test/test.log
to send all log output from the test to the given file. If you want to see what is
happening while you run the test you can use tee to send output to
file and to the screen:
make test |& tee work/polycost/test/test.log
refsys/$version/work/calib/site/architecture.os/polycost/test
The tag architecture.os can be for instance
i386.Linux or hp700.HP-UX, i.e. the first part indicates
the hardware architecture and the second part indicates the operating system.
You can compare your score file to those for i386.Linux produced
at KTH by typing:
make compare
which runs two simple diff:s, one for the score (results.llk)
file and one for the DET-curve (results.det). If
no differences are reported, then your results are equal to those of
the reference (at least at the score output and DET-curve levels).
cd refsys/$version
tar cvf mySite.myArch.myOS.tar work/polycost/test
gzip mySite.myArch.myOS.tar
-- send mySite.myArch.myOS.tar.gz by email --
Please also include bugfixes, problem reports or comments of any kind.