The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Two things.
First, please create a ticket for this on the SMACH trac here: https://kforge.ros.org/smach/trac/newticket
Second, if you want to just change all of the SMACH loginfo calls to logdebug in an overlay, you can just modify line 44 of executive_smach/smach_ros/src/__init__.py and replace "rospy.loginfo" with "rospy.logdebug".
| | 2 | No.2 Revision |
Two things.
First, please create a ticket for this on the SMACH trac here: https://kforge.ros.org/smach/trac/newticket
Second, if you want to just change all of the SMACH loginfo calls to logdebug in an overlay, you can just modify line 44 of executive_smach/smach_ros/src/__init__.py and replace "rospy.loginfo" with "rospy.logdebug".
As @joq points out, there's no easy way to switch python logger levels at runtime. Because of this, we made it so that this information is reported at the info level because more often than not we wanted to see the information, but not all of the minute "debug" logging output that you would see in Python.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
