[Top][All Lists]

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

[Octave-bug-tracker] [bug #53094] findpeaks fails to find peaks in some

From: Avinoam Kalma
Subject: [Octave-bug-tracker] [bug #53094] findpeaks fails to find peaks in some cases
Date: Fri, 9 Feb 2018 00:35:00 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Follow-up Comment #2, bug #53094 (project octave):

Using Octave ver. 4.2.1 with signal ver. 1.3.2 On Windows, I get

data = [3.7157e+03 3.7494e+03 3.9494e+03 4.3736e+03 5.1826e+03 6.8833e+03
1.2315e+04 5.0602e+04 1.7847e+03 5.4324e+03 4.9405e+04 1.6456e+04 8.1962e+03
5.8239e+03 4.7297e+03 4.1464e+03 3.8383e+03]; 
>> [i, p] = findpeaks(data)
i = [](1x0)
p = [](0x1)

Using findpeaks from
https://sourceforge.net/p/octave/signal/ci/default/tree/inst/findpeaks.m I

>> [i, p] = findpeaks_new(data)
i =

   50602   49405

p =

    8   11

so the version from sf fixed the bug.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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