We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Original report (archived issue) by Carlos Agüero (Bitbucket: caguero, GitHub: caguero).
There's a constant flow of log information:
[ INFO] [1530898335.354347581, 5.500000000]: 0: 0.0414236 / 0.000165695 [ INFO] [1530898335.855024332, 6.3167fc3ec4555094a7bbd76a87b675a9e5e2d065]: 0: 0.0414236 / 0.000165695 [ INFO] [1530898335.891886977, 6.037000000]: Command timeout! [ INFO] [1530898336.357305769, 6.501000000]: 0: 0.0414236 / 0.000
that deviates the attention from other errors or sporadic log info. We should avoid continuous log messages.
We could either play with the log level or remove these calls to ROS_INFO_STREAM_THROTTLE() in usv_gazebo_thrust_plugin.cc.
ROS_INFO_STREAM_THROTTLE()
usv_gazebo_thrust_plugin.cc
The text was updated successfully, but these errors were encountered:
Original comment by Carlos Agüero (Bitbucket: caguero, GitHub: caguero).
Sorry, something went wrong.
Original comment by Brian Bingham (Bitbucket: brian_bingham).
Agree - this is left over from dev.
Solved in some of the plugin refactors.
No branches or pull requests
Original report (archived issue) by Carlos Agüero (Bitbucket: caguero, GitHub: caguero).
There's a constant flow of log information:
that deviates the attention from other errors or sporadic log info. We should avoid continuous log messages.
We could either play with the log level or remove these calls to
ROS_INFO_STREAM_THROTTLE()
inusv_gazebo_thrust_plugin.cc
.The text was updated successfully, but these errors were encountered: