[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #41480] image package :normxcorr2 yields diffe

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #41480] image package :normxcorr2 yields different result from matlab
Date: Thu, 06 Feb 2014 14:01:08 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36

Update of bug #41480 (project octave):

                Category:                    None => Octave Forge Package   
              Item Group:                    None => Incorrect Result       
                 Release:                   3.6.4 => other                  
                 Summary: normxcorr2 yields different result from matlab =>
image package :normxcorr2 yields different result from matlab


Follow-up Comment #1:

Thanks for reporting and clarifying your bug report over what you had posted
to the mailing list. On the list it seemed like you were suggesting that
xcorr2 is wrong, but perhaps it's the normxcorr2 function in the image package
that needs tweaking.

As Carnë said on the mailing list, the xcorr2 function in Matlab has no
options, those are Octave extensions to have feature parity with the xcorr

Perhaps this bug should be addressed by changing normxcorr2, and leaving
xcorr2 as it is now. If xcorr2 (..., "coeff") is equivalent to xcorr (...,
"coeff"), then it should be normxcorr2 that is fixed to be Matlab compatible
if that's what's happening here.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]