So I reacquainted myself with the hierarchical implementation again,
and you're correct that it doesn't support oversampling.
Looking at the regular version it seems that the main thing required
to support oversampling would be that the logic determining which
input samples go into which filter, a
Hi,
> For example for 13e6 GSM band I can extract all channels by setting
> Channels parameter of the channelizer to 65 (13e6/0.2e6).
> Then I can get output signal that is sampled with 4*gsm_symbol_rate by
> setting oversampling to 65/12.
>
> It would be great to have something like this in your
Thanks Ben for the answer.
Regarding the last question, I want to clarify a bit what I meant.
Regular polyphase channelizer have oversample_rate option that lets you
set oversampling so you can get output sample rates:
input_samp_rate/number_of_channels * oversample_rate
where oversample_rate =
Thanks Ben for the answer.
Regarding the last question, I want to clarify a bit what I meant.
Regular polyphase channelizer have oversample_rate option that lets you
set oversampling so you can get output sample rates:
input_samp_rate/number_of_channels * oversample_rate
where oversample_rate =
The algorithm should be identical in the hierarchical case. The only
difference is that because the hierarchical implementation splits the
logic over several signal processing blocks, GNURadio is able to
easily parallelize the implementation. The n_filterbanks parameter is
just the number of filt
Hi all,
Recently I did simple benchmark of hierarchical polyphase channelizer
block (written by Ben Reynwar according to git blame) vs regular
polyphase channelizer block. It seems that hierarchical version is 2-3
times faster.
The documentation of the hierachical polyphase channelizer seems to b
