[Top][All Lists]

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

[Octave-bug-tracker] [bug #51657] [octave-forge] (signal) gausswin produ

From: Juan Pablo Carbajal
Subject: [Octave-bug-tracker] [bug #51657] [octave-forge] (signal) gausswin produces slightly wrong result
Date: Mon, 11 Dec 2017 16:25:44 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36

Update of bug #51657 (project octave):

              Item Group:       Inaccurate Result => Matlab Compatibility   
                  Status:               Confirmed => In Progress            
             Assigned to:                    None => juanpi                 


Follow-up Comment #5:


To speed up the process you can send patches against the current development
version of signal.

I implemented a fix for the matlab 2017a incompatibility for scalar input. If
their text help says m should be a scalar, their function has a bug!

With the development version you get

octave-gui:1> gausswin(0)
error: gausswin: M must be a positive integer
error: called from
    gausswin at line 35 column 5
octave-gui:1> gausswin(1)
ans =  1
octave-gui:2> gausswin(2)
ans =


I am not sure we want to copy the behavior for the non-scalar input. My guess
is that this is an undesired behavior that they got when introducing automatic
broadcasting. They will probably fix it in the future.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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