|
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: Hi, 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 = 0.0439369336234074 0.0439369336234074 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: <http://savannah.gnu.org/bugs/?51657> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |