octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #50820] [octave forge] (signal) pwelch incorre


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #50820] [octave forge] (signal) pwelch incorrectly discards DC component
Date: Tue, 9 Oct 2018 11:10:54 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

Follow-up Comment #15, bug #50820 (project octave):

Thanks for the update.

Doesn't fft(X,N) pad X with zeros as needed?  It seems easier to do that than
to insert X into a zero-padded XX array.  That's why I changed the call to use
fft(X,N).

Instead of generating a cell array of colons, you can use indexing like this:


x = reshape (1:60, [10,2,3])  ## 3d array for illustration.
xx = x(start:end,:)  ## all columns in all pages as a 2d array.
reshape (xx, [end-start+1,2,3])  ## IF you need 3d array again.


I was also confused by the subtraction of 3.  It was in the original pwelch.m
from Octave Forge.  Are there any cases where it is needed to avoid generating
a window size that is too large?

What should happen for short vectors?  Is there a minimum size limit that
should be enforced?


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?50820>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

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