annotate tests/0011/run-test.sh @ 473:b2fd8113d8bc api-inversion

const declarations for some API arguments. This should make it slightly clearer whose responsibility (the user's) it is to manage the memory pointed to by the corresponding arguments. Suggested by Chris Cannam.
author mas01cr
date Tue, 06 Jan 2009 16:27:01 +0000
parents fe4dc39b2dd7
children
rev   line source
mas01cr@252 1 #! /bin/bash
mas01cr@82 2
mas01cr@82 3 . ../test-utils.sh
mas01cr@82 4
mas01cr@82 5 if [ -f testdb ]; then rm -f testdb; fi
mas01cr@82 6
mas01cr@82 7 ${AUDIODB} -d testdb -N
mas01cr@82 8
mas01cr@82 9 intstring 2 > testfeature
mas01cr@82 10 floatstring 0 0.5 >> testfeature
mas01cr@82 11 floatstring 0.5 0 >> testfeature
mas01cr@82 12
mas01cr@82 13 ${AUDIODB} -d testdb -I -f testfeature
mas01cr@82 14
mas01cr@82 15 # sequence queries require L2NORM
mas01cr@82 16 ${AUDIODB} -d testdb -L
mas01cr@82 17
mas01cr@82 18 echo "query point (0.0,0.5)"
mas01cr@82 19 intstring 2 > testquery
mas01cr@82 20 floatstring 0 0.5 >> testquery
mas01cr@82 21
mas01cr@82 22 ${AUDIODB} -d testdb -Q sequence -l 1 -f testquery > testoutput
mas01cr@82 23 echo testfeature 1 0 0 > test-expected-output
mas01cr@82 24 cmp testoutput test-expected-output
mas01cr@82 25 ${AUDIODB} -d testdb -Q sequence -l 1 -f testquery -n 1 > testoutput
mas01cr@82 26 echo testfeature 0 0 0 > test-expected-output
mas01cr@82 27 cmp testoutput test-expected-output
mas01cr@82 28
mas01cr@82 29 echo "query point (0.5,0.0)"
mas01cr@82 30 intstring 2 > testquery
mas01cr@82 31 floatstring 0.5 0 >> testquery
mas01cr@82 32
mas01cr@82 33 ${AUDIODB} -d testdb -Q sequence -l 1 -f testquery > testoutput
mas01cr@82 34 echo testfeature 1 0 1 > test-expected-output
mas01cr@82 35 cmp testoutput test-expected-output
mas01cr@82 36 ${AUDIODB} -d testdb -Q sequence -l 1 -f testquery -n 1 > testoutput
mas01cr@82 37 echo testfeature 0 0 1 > test-expected-output
mas01cr@82 38 cmp testoutput test-expected-output
mas01cr@82 39
mas01cr@82 40 exit 104