discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] how to use FFT without grc block


From: Marcus Müller
Subject: Re: [Discuss-gnuradio] how to use FFT without grc block
Date: Thu, 23 Jan 2014 20:57:03 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yes, you can. Look into the gr-fft module documentation in the doxygen
docs.
Alternatively, you can simply link against FFTW [1] yourself and use
the FFT algorithms; gr-fft is a wrapper for that functionality
offering simplification and ease of use. But if an FFT is all that
you're after, going directly for FFTW might be the best choice; if you
need something non-standard such as 2D-FFT (or higher dimensions),
real-only transforms, sliced/strided, hundreds of transforms at
once... use FFTW. If you just want an N-Point FFT and are linking
against GR anyway, use gr-fft.

Greetings,
Marcus

[1] Fastest Fourier Transform in the West, http://www.fftw.org/

On 23.01.2014 20:17, Nasi wrote:
> Hi all,
> 
> I know there is an FFT block in gnuradio 3.7. I want to create a cc
> file and add some gnuradio classes there. Can I use FFT without
> .grc file without using blocks, just as a c++ function?
> 
> 
> 
> 
> 
> _______________________________________________ Discuss-gnuradio
> mailing list address@hidden 
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS4XQPAAoJEAFxB7BbsDrLyfEIAJLH45hnH5DpkMpU/bV4s3Pl
2IXkAzZYJ1+JzotL0s9I4FMoQiwWe3t1ICzcP7U1p/kcZbA4nXaZ+JnTdLrQLGTG
9+G7vWDsNYtsxmxzDScFPsxzathATbM5k0VDqXoDf1sPd1RMP0TyOZ0hl9E+tugK
HWvZcLjwEUdNoW/ZdHA8DVohXS05qF9doeF5vQI33ftUq9iWEaXCAYM3r/Vudbi0
OcwyloLhdaKw47qiclLvlKUfI8va8YbknSB0WU2laiIK59qsl/87bd6K01jfAyWf
QZgbYJ8SoRtr9to04iW4DUjaX59PESJhSZYnpf8ZEhXcKw8i+kM0c7lPC9mnCww=
=vK/B
-----END PGP SIGNATURE-----



reply via email to

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