Say I want to create an energy detect block that takes a certain number
of input samples, measures the (signal) power and compares it against a
threshold. Only if the power exceeds the threshold, the block has to
make the decision that some genuine signal is being received and then
move only those samples to the next block for further processing.
So if power > threshold, send all the samples as is to the next block.
In this case the block behaves as a sync block.
But if power < threshold, the block has to flush the data and wait for
the next set of samples. (I’m not sure what type of block fits the bill
here)
Either way, i wanted to know how to get the same block to behave in two
different ways in terms of the number of items that it outputs.
If our squelch blocks don’t suffice, and you do need to implement your
own, you’d use a general gr::block.
M
I looked at the squelch block and source code. I probably need to make
my own block because my algorithm is slightly different. I am buffering
up data coming in through a USRP and sliding a window over it to
calculate power in each window.
And I did get as far as deciding that the gr::block is the one to use.
I’m coding in python by the way, using gr_modtool, so the equivalent
would be gr.basic block if I’m not mistaken.
My question is this and I find that this often throws me off:
Do I need to completely leave out the forecast and consume functions
here because the number of output items is not really related to the
number of input items?
Will something like this in the work function work do you think? (Not in
any specific programming language):
while input_items:
buffer = in[0][buffer length] #this buffer is just an empty array i
create.
slide window, do whatever i need to do
if power < threshold:
do nothing (how do i implement this sort of thing? Will a simple
break statement work?)
else:
identify the number of windows that gave power > threshold and
return that many windows worth of items
update buffer
Thanks for your help
Anil
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.