You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During acceptance testing of #360@peteflorence and I found that one of the fusion server scripts was failing due to not being properly initialization as a ROS node. Most of those Python scripts need to have a
rospy.init_node('node_name_here', anonymous=True)
call added somewhere early in their execution. (anonymous is optional but probably makes sense for those scripts?)
The text was updated successfully, but these errors were encountered:
On Wed, Jan 30, 2019 at 3:08 PM Greg Izatt ***@***.***> wrote:
During acceptance testing of #360
<#360> @peteflorence
<https://github.com/peteflorence> and I found that one of the fusion
server scripts was failing due to not being properly initialization as a
ROS node. Most of those Python scripts need to have a
rospy.init_node('node_name_here', anonymous=True)
call added somewhere early in their execution. (*anonymous* is optional
but probably makes sense for those scripts?)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#361>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AFYQqGRCzYjF4k7jchlD9CUG1WfiiEtvks5vIfvLgaJpZM4aa9-w>
.
During acceptance testing of #360 @peteflorence and I found that one of the fusion server scripts was failing due to not being properly initialization as a ROS node. Most of those Python scripts need to have a
rospy.init_node('node_name_here', anonymous=True)
call added somewhere early in their execution. (anonymous is optional but probably makes sense for those scripts?)
The text was updated successfully, but these errors were encountered: