[Octave-patch-tracker] [patch #7999] Further adjustments to fftfilt after changeset for bug 37297

[Mike Miller]

Update of patch #7999 (project octave):

                  Status:                    None => In Progress            
             Assigned to:                    None => mtmiller               

    _______________________________________________________

Follow-up Comment #5:

True, I should have kept that N for the FFT size to differentiate from the
argument n.

Yes, we could address the performance tradeoff either in the docstring or with
a warning, but do we know that some threshold that we identify will be the
same across different hardware?

I'd be more inclined to add a note to the docstring with something general
like "Certain values of @var{n} may result in much worse performance than
others.  If you are unsure how to specify the value of @var{n}, use the
two-argument form or use the filter function instead."

I saw the messages on the mailing list about the failing tests, feel free to
open another patch tracker item about that one.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/patch/?7999>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/