----- Original Message -----
> From: Mike Miller <mtmil...@ieee.org>
> To: Sergei Steshenko <sergst...@yahoo.com>
> Cc: Octave Forge <octave-dev@lists.sourceforge.net>
> Sent: Sunday, July 8, 2012 5:39 PM
> Subject: fix rceps behavior for signals of odd length
>
> On Fri, Jul 6, 2012 at 7:20 PM, Sergei Steshenko <sergst...@yahoo.com>
> wrote:
>> Hello,
>>
>> here is a quick example:
>>
>> "
>> octave:43> [y, xm] = rceps([1 2 3 4]);
>> octave:44> xm
>> xm =
>>
>> 3.98049 3.01913 2.01951 0.98087
>>
>> octave:45> [y, xm] = rceps([1 2 3 4 5]);
>> octave:46> xm
>> xm =
>>
>> 4.9244 3.7654 1.5151
>>
>> octave:47>
>>
>> ".
>>
>> In the second case 'xm' has just 3 elements, though it is supposed
> to have 5.
>
> Hi Sergei, I agree I think this is a bug. Moving to octave-dev list.
>
> Can someone with ML signal toolbox please send back the results of:
>
> [y, xm] = rceps ([1, 2, 3, 4])
> [y, xm] = rceps ([1, 2, 3, 4, 5])
> [y, xm] = rceps ([0])
> [y, xm] = rceps ([1])
>
> Thanks.
> --
> mike
>
Ironically, the file contains built-in test code. For even length input signal
only.
Regards,
Sergei.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev
