Skip to content
New issue

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

Throttle optimization duration exceeded warning #140

Conversation

efernandez
Copy link
Collaborator

When the optimization exceeds the configured duration, it's likely to happen quite often, so I think it's better to throttle the ROS_WARN message that reports that.

In a future PR we could also try to make the optimization duration available in the diagnostics.

ROS_WARN_STREAM("Optimization exceeded the configured duration by " <<
(optimization_complete - optimization_deadline) << "s");
ROS_WARN_STREAM_THROTTLE(10.0, "Optimization exceeded the configured duration by "
<< (optimization_complete - optimization_deadline) << "s");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spacing looks weird on github

Copy link
Collaborator Author

@efernandez efernandez Feb 10, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, that's actually the spacing I get for those two lines with my clang-format configuration. I have a vim plugin that uses it, so I can run :Autoformat on specific lines.

I can change it if you want.

Although it'd be great if we can have a .clang-format file in the fuse packages. 😃

@svwilliams svwilliams merged commit 123739f into locusrobotics:devel Feb 13, 2020
@efernandez efernandez deleted the throttle_optimization_duration_warning branch March 11, 2020 10:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants