Hi!
On 07/26/2010 08:02 PM, Eitan Marder-Eppstein wrote:
Cedric and Joel,
It turns out that Josh was right, rospy is writing all debug statements
to log files, even if the log level is not set to debug. I've filed a
ticket against it, which when addressed, should fix these issues. You
can find the ticket here: https://code.ros.org/trac/ros/ticket/2916
This discussion made me wonder, should all logdebug statements be
removed from python nodes which still run in boxturtle and are
frequently called? I'm particularly worried about the performance of a
low-powered robot that runs python nodes and communicates with a master
over a weak wireless link. If I understand it correctly, then every
rospy.logdebug(...) results in a callback of the python node to the
master, which then writes it into its local logfile?
With the fix, the logging level of the nodes can be set through the
launch file and then stays fixed, correct? I had assumed that I should
be able to change the log level with rxloggerlevel, but that's
apparently not the case:
https://code.ros.org/trac/ros/ticket/2927
Of course, if all the log level setup is done through log4cxx then that
functionality is missing in python.
To avoid confusion, would it be possible to display python nodes in
rxloggerlevel nevertheless, with their current fixed log level and a
hint that it can not be changed in python nodes? It might be useful
having this hint in the wiki as well (which I could have missed).
For the future, having changeable logger levels in python nodes would
be nice to have ;)
Cheers,
Armin
--
Armin Hornung Albert-Ludwigs-Universität
www.informatik.uni-freiburg.de/~hornunga Dept. of Computer Science
HornungA@informatik.uni-freiburg.de Humanoid Robots Lab
Tel.: +49 (0)761-203-8010 Georges-Köhler-Allee 79
Fax : +49 (0)761-203-8007 D-79110 Freiburg, Germany