[Discuss-gnuradio] Modulation/Demodulation Blocks' Function details

2012-08-09 Thread Frederick Lee
Hi GNURadio community, I'm looking into how the modulation and demodulation blocks work. Specifically the BPSK mod and demod blocks. Here is a list of the files I looked through and the location: generic_mod_demod.py - */gr-digital/python modulation_utils.py - */gr-digital/python bpsk.py -

Re: [Discuss-gnuradio] Modulation/Demodulation Blocks' Function details

2012-08-09 Thread Christian Gagneraud
On 09/08/12 18:55, Frederick Lee wrote: Hi GNURadio community, I'm looking into how the modulation and demodulation blocks work. Specifically the BPSK mod and demod blocks. Here is a list of the files I looked through and the location: generic_mod_demod.py - */gr-digital/python

Re: [Discuss-gnuradio] Modulation/Demodulation Blocks' Function details

2012-08-09 Thread Frederick Lee
Swig stuff are python bindings to C or C++ code. So in your example pfb_clock_sync_ccf() has been coded in C++, and _digital_swig.pfb_clock_sync_ccf() is the generated python wrapper to access the C++ pfb_clock_sync_ccf() from a python script. The C++ code is in include/ and lib/, swig bindings