OpenCores

URL https://opencores.org/ocsvn/dblclockfft/dblclockfft/trunk

Subversion Repositories dblclockfft

[/] [dblclockfft/] [trunk/] [bench/] [cpp/] [fft_tb.cpp] - Rev 20

Go to most recent revision | Details | Compare with Previous | Blame

Filtering Options

Rev	Log message	Author	Age	Path
19	Added the capability to accumulate bits internal to the FFT, only to drop those extra bits just before the end. This helps to reduce truncation error, and may even drop it by a factor of four (my own measurements).	dgisselq	3547d 11h	/dblclockfft/trunk/bench/cpp/fft_tb.cpp
16	Cleaned up the test bench build scripts, made sure license statements were placed on all files, etc.	dgisselq	3549d 04h	/dblclockfft/trunk/bench/cpp/fft_tb.cpp
14	Found several bugs in the previous version. The biggest were in the qtrstage. Apparently, the qtrstage didn't work before, even though I thought it did. Further, the FFT testbench has been adjusted to place proper values into the fft_tb.dbl file it creates. (I've been testing it by reading this into Octave, and visually inspecting the results--quantitative testing of the fft_tb and ifft_tb are still lacking.) Now, however, if I cascade the forward and reverse together, I seem to get something at least close to the right answer. Close, of course, is relative. I think all that I still struggle with is rounding and truncation errors, hence I'm checking in my changes. The FFT generator was also modified to allow arbitrary length paths in the command line specified path prefix. This has not been tested. A bug was also found in the butterfly, whereby for certain multiply delays the butterfly would be unable to determine whether or not its results were valid. Adding an extra bit to the FIFO address in these cases fixed the problem. This change was encapsulated into the lgdelay() function, and an additional bflydelay function. In my frustration, I modified the fftstage function so that, when it is built, the parameters it is built with are the default parameters. This should only affect testing, by making any testing more realistic, but that may still remain to be seen. Another change was made to the core generator, so that now when a core is generated, the main file now contains a copy of the arguments that were used when the core generator was invoked. This is good for posterity, in case you ever need to ask yourself how I ended up here.	dgisselq	3551d 01h	/dblclockfft/trunk/bench/cpp/fft_tb.cpp
9	Now working on the test bench for the FFT. Currently, the FFT passes all test bench "tests." However, the test bench does not yet accurately report on the success of its work. This remains for future work. Lots of bugs fixed while making this test bench code work. (I should mention, while all test benches currently pass, that doesn't mean that the code works ... yet. I just haven't found the bug that breaks it.)	dgisselq	3557d 06h	/dblclockfft/trunk/bench/cpp/fft_tb.cpp
7	Two sources belonging to the last commit, whose comments go with the last commit, that just didn't make it in time.	dgisselq	3558d 00h	/dblclockfft/trunk/bench/cpp/fft_tb.cpp

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.