-
Notifications
You must be signed in to change notification settings - Fork 303
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
[Diagnostics] Add diagnostics of execution time and periodicity of the controllers and controller_manager #1871
base: master
Are you sure you want to change the base?
[Diagnostics] Add diagnostics of execution time and periodicity of the controllers and controller_manager #1871
Conversation
…ith more information
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I successfully tested the new diagnostics with the demos (synchronous controllers), but as I haven't used them much a note for myself (would have been valid with #1764 already)
- per default, /diagnostics is sent with 1Hz by the Updater, we don't set a different value in the CM's constructor
- diagnostics_updater_ lives in a non RT-thread, and so do also the callback methods.
One comment as we are adding more and more parameters: Would it make sense to use generate_parameter_library also for the CM? I think we can't use it for the per-controller parameters because maps do not work well here, and there is no way to "namespace" parameters with GPL. But for the others?
@christophfroehlich yes, I thought of using the GPL for this, but I wanted to see your opinion here before taking any decision. I'm open to having this |
This PR aims to add diagnostics to the controller_manager and the loaded controllers regarding their periodicity and execution time.
Needs: ros-controls/realtime_tools#192
The diagnostics should kinda look like the following screenshots (The following are only to look at the summary):