Integer queries give strange (and presumably wrong) results

[eigenvectorBazuz]

I tested the offline model on some of my data with manually-selected queries and it worked ok. Then I tried it again and got garbage results with tracks valued more or less in (-2,2) (and that's for 480x640 images). Eventually I found out that the cause of this was my specifying the queries as integers rather than floats in the second trial. FYI.