Comments on the Logging architecture in gnuradio

Suggestion for future improvement : I would love to be able to enable
logging on a module by module basis in python for gnuradio. Right now, I
see that many modules take a --verbose option but that’s it. It is all
or
nothing.

It would be great to have a unified logging framework (that works across
python and c++) so logging can be configured in one place and shows up
in a
unified stream (file). It should be possible to set logging levels (
FINE,
FINER, FINEST etc. ) to control the amount of logging.

I was actually a bit surprised not to see such a thing given the
maturity
of the code base.

(I know you are going to ask me to volunteer to do it :slight_smile: but perhaps an
effort is already under way?)

Regards,

On Mon, Mar 4, 2013 at 3:55 PM, M. Ranganathan [email protected] wrote:

I was actually a bit surprised not to see such a thing given the maturity of
M. Ranganathan
Funny you should ask. A new gr-logger was put into master/next /just/
this morning. If you build the Doxygen manually locally (after
updating your local checkout), there is a new “Related Pages” for
“Logging.”

It’s new, so it’s not widely used. It’s very simple to use from inside
a gr_block, but there’s some setup to do elsewhere. I’m still thinking
of ways to make this as simple to use and ubiquitous throughout our
code as possible. But this is an excellent start, I feel.

Tom

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