Debug output within a launch file
How do I enable debugging output (ROS_DEBUG) for a node within a launch file?
How do I enable debugging output (ROS_DEBUG) for a node within a launch file?
The previous answer is incomplete. Setting output="screen"
in the launch file will show INFO messages and above, not DEBUG output.
For that, you can set the ROS console configuration.
The rxconsole
package allows dynamic setting and resetting of DEBUG output. The "Levels" button near the lower right corner can set each C++ logger to any level. (It has no effect on Python loggers.)
Just set output="screen"
in the launch file as mentioned below. I prefer rqt_console over the screen. It's much easier to filter and even pause the output.
In the node definition, you can set the output to screen:
<node pkg="amcl" type="amcl" name="amcl" output="screen">
for example. That will get the output pushed to your console.
You can also often find the information you're looking for through the rxconsole program. It's nice for separating the output from the many nodes that are launched, as well as displaying based on severity (warnings, errors, debugs).
Please start posting anonymously - your entry will be published after you log in or create a new account.
Asked: 2011-03-31 06:38:12 -0500
Seen: 14,997 times
Last updated: Apr 01 '11
No launch-prefix for includes?
Docker container acutronicrobotics/gym-gazebo2 installed, what to do next?
Cannot locate launch node of type + Can't locate node
gdb: Any way to debug a segfault in a ROS node?
see full launchfile from top tier one
Extracting output data from launch file node
Running turtlebot on a roomba, launch file?