Thu, 27 Nov 2014 16:05:24 +0000 |
Chris Cannam |
More debug output
refactors
|
Thu, 27 Nov 2014 16:05:19 +0000 |
Chris Cannam |
Ah, it's subtler than that -- we have to handle the case where this is not the first matcher as well, if we're to get precisely the same results
refactors
|
Thu, 27 Nov 2014 15:56:12 +0000 |
Chris Cannam |
Fix inconsistency (with Finder) in choice of preference where two costs come out equal
refactors
|
Thu, 27 Nov 2014 15:29:43 +0000 |
Chris Cannam |
Improve error reporting
refactors
|
Thu, 27 Nov 2014 13:02:28 +0000 |
Chris Cannam |
Remove some debug out
refactors
|
Thu, 27 Nov 2014 12:59:28 +0000 |
Chris Cannam |
And remove that printout
refactors
|
Thu, 27 Nov 2014 12:59:23 +0000 |
Chris Cannam |
Fix diagonal handling: there was an implicit fixed diagonal weight of 2 in comparison of diagmin+distance to othermin directly
refactors
|
Thu, 27 Nov 2014 12:57:59 +0000 |
Chris Cannam |
Version which prints out matrix on error
refactors
|
Thu, 27 Nov 2014 12:54:20 +0000 |
Chris Cannam |
Move some functions about
refactors
|
Thu, 27 Nov 2014 12:08:16 +0000 |
Chris Cannam |
Previous commit was a mistake: the ahead-of-time business is in Finder::getExpandDirection. In fact we were failing to swap advance directions in forward path when writing to the "other" finder. This does not actually affect the backward path calculation, but it does mean we can restore the sanity check.
refactors
|
Thu, 27 Nov 2014 11:27:17 +0000 |
Chris Cannam |
Ah, no, of course the advance differs for the forward path (it is based on partial information). But the cost shouldn't.
refactors
|
Thu, 27 Nov 2014 10:53:00 +0000 |
Chris Cannam |
More error checking (check advance as well as cost)
refactors
|
Thu, 27 Nov 2014 10:49:11 +0000 |
Chris Cannam |
Expose diagonal weight as a parameter
refactors
|
Thu, 27 Nov 2014 10:14:07 +0000 |
Chris Cannam |
Error-checking code optional
refactors
|
Thu, 27 Nov 2014 08:13:29 +0000 |
Chris Cannam |
Toward cost checks
refactors
|