Making a custom block with no specific/fixed relationship between input and output rates

Hello everyone,

I have a rather open question for you guys this time. I need to make a
custom block with no specific/fixed relationship between input and
output rates. More precisely, the input(s) to my custom block still come
in a streaming fashion but the output is now bursty and aperiodic in
nature. In other words, my custom block should consume/accept the
input(s) at regular rates but should produce (possibly variable number
of)samples at its output(s) only when it pleases. Therefore, I cannot
derive my class from any of the gr_sync_block, gr_block,
gr_sync_decimator, gr_sync_interpolator parent classes. What other
options do I have in my hand to accomplish this job? Any suggestions?

Thanks,
Yu.

On Tue, Aug 14, 2012 at 08:44:20AM -0700, Zing Yu wrote:

I have a rather open question for you guys this time. I need to make a custom
block with no specific/fixed relationship between input and output rates. More
precisely, the input(s) to my custom block still come in a streaming fashion
but the output is now bursty and aperiodic in nature. In other words, my custom
block should consume/accept the input(s) at regular rates but should produce
(possibly variable number of) samples at its output(s) only when it pleases.
Therefore, I cannot derive my class from any of the gr_sync_block, gr_block,
gr_sync_decimator, gr_sync_interpolator parent classes. What other options do I
have in my hand to accomplish this job? Any suggestions?

You can derive from gr_block. The OFDM detector block does this.

MB


Karlsruhe Institute of Technology (KIT)
Communications Engineering Lab (CEL)

Dipl.-Ing. Martin B.
Research Associate

Kaiserstraße 12
Building 05.01
76131 Karlsruhe

Phone: +49 721 608-43790
Fax: +49 721 608-46071
www.cel.kit.edu

KIT – University of the State of Baden-Württemberg and
National Laboratory of the Helmholtz Association

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs