Re: [Discuss-gnuradio] GNURadio PER encoder/decoder

[Martin Braun (CEL)]

On Sun, Aug 12, 2012 at 01:28:03PM -0400, Marcus D. Leech wrote:
> <rant>
> [...]
> Where do we draw the line as to what consitutes a "reasonable" thing
> to be done inside the Gnu Radio framework, and something that
>   is best done elsewhere?  Modern operating systems, like Linux have
> a rich palette of IPC mechanisms that are specifically designed to
>   facilitate functional decomposition, and yet I continue to see
> people wanting to stuff everything into the Gnu Radio framework.
> Gnu Radio
>   is developing an increasingly-well-deserved reputation as
> "bloatware", precisely because we tend to entertain the notion that
> "if it starts
>   or ends as a radio(-like) signal, then we're your one-stop-shop".
> </rant>

Yay, a rant leading to a discussion! What a fabulous way to return back
to work.

GNU Radio, as we all know, is really not that specific to baseband
processing. Its main assets are the block structure (which makes it
modular) and the scheduler, as well as the richness of core blocks
(including gr-digital, gr-filter etc.).

Adding blocks (in particular, to your own module) therefore does not
make it bloated: the core stays lean and mean, and the fringes become
more diverse.

So, I'm all for it (by 'it' I mean writing whatever you want in GNU
Radio). At some point, a developer will realize that the
block-and-stream structure really won't help, and that's when you
connect something else via IPC. But a packet encoder might suit the GNU
Radio structure just fine.

MB

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

Dipl.-Ing. Martin Braun
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

pgp9jtaui8c_u.pgp
Description: PGP signature