search

feynmanrules / aforge

Automatically exported from code.google.com/p/aforge
0 stars 0 forks source link

AForge.Math.FourierTransform.FFT unhandled exception #156

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Running an FFT on a data sample produces an exception.

What is the expected output? What do you see instead?

I should see the input frequency.

What version of the product are you using?

Latest.

Please provide any additional information below.

I've attached a simple test case.

I create a simple array of complex and attempt to get back the original 
frequency.

Unfortunately I get an exception.

Isolated example attached.

Original issue reported on code.google.com by tgraupm...@gmail.com on 23 Sep 2010 at 5:18

Attachments:

GoogleCodeExporter commented 9 years ago 
This may be a defect, but it is also as documented.

FourierTransform.FFT is documented to only accept arrays of length 2, 4, 8, 16, 
32, 64, 128, 256, 512, 1024, 2048, 4096, 8192, or 16384. The passed array has 
22050 elements, and the exception documented to be throw in such a situation is 
indeed thrown.

Original comment by dales...@gmail.com on 26 Oct 2010 at 1:39

GoogleCodeExporter commented 9 years ago 
If this behavior is documented, then I don't see a defect/bug really. I think 
it is a bug, when people expect something from software, which is not supposed 
to be done and it is documented that it is NOT done.

So, if all happens like it is said in docs, then maximum what this ticket may 
pretend is an Enhancement request, not Defect report.

Original comment by andrew.k...@gmail.com on 27 Oct 2010 at 8:18

GoogleCodeExporter commented 9 years ago

Original comment by andrew.k...@gmail.com on 10 Nov 2010 at 10:35

GoogleCodeExporter commented 9 years ago 
Closing the ticket since it describes a bug, which does not exist. Current 
behavior corresponds to documentation.

Original comment by andrew.k...@gmail.com on 17 Nov 2010 at 3:01