view tests/0003/run-test.sh @ 53:944f05e65a58

Fix what is I think an off-by-one in query and sequence searching.

When taking the mean of the N minimum distances, only consider those
distances which are closer than the infinite/uninitialized distance.

(This renders us potentially vulnerable to an internal consistency
horror where we end up trying to divide by zero.  This is unlikely to be
picked up by unit tests, but might well be by random tests if this is in
fact a problem.)

#! /bin/sh

. ../test-utils.sh

if [ -f testdb ]; then rm -f testdb; fi

${AUDIODB} -d testdb -N

# We could contemplate putting the test feature (and the expected
# query output) under svn control if we trust its binary file
# handling.

# FIXME: endianness!
intstring 1 > testfeature
floatstring 1 >> testfeature

${AUDIODB} -d testdb -I -f testfeature

${AUDIODB} -d testdb -Q point -f testfeature > test-query-output

echo testfeature 1 0 0 > test-expected-query-output

cmp test-query-output test-expected-query-output

# failure cases
${AUDIODB} -d testdb -I && exit 1
${AUDIODB} -d testdb -f testfeature && exit 1
${AUDIODB} -I -f testfeature && exit 1
${AUDIODB} -d testdb -Q notpoint -f testfeature && exit 1
${AUDIODB} -Q point -f testfeature && exit 1

exit 104