-
Notifications
You must be signed in to change notification settings - Fork 206
Use timer #114
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
Merged
Merged
Use timer #114
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
732497b
use ros2 timer instead of custom logic
Karsten1987 532a233
maintain double precision for period
Karsten1987 c7efe7b
style and documentation touchups
Karsten1987 18f5c77
re-introduce force_update
Karsten1987 15dba7f
fix flake8
Karsten1987 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Did the timer refactoring make it necessary to drop force_update (in python and c++)?
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.
the update function didn't really do anything if the period wasn't exceeded yet. So I believe it doesn't make sense to have a
force_updatefunction, which basically then just calls update.If you wanted to force an update, you could always just call
updateon your diagnostic updater instanceThere 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.
My understanding of the original implementation was, that
force_update()will always update, butupdate()will only callforce_update()when the period was exceeded. See https://github.com/ros/diagnostics/blob/ros2-devel/diagnostic_updater/diagnostic_updater/_diagnostic_updater.py#L254-L255This would mean that the two methods indeed have a different behavior. Calling
update()with twice the configured rate will still only send updates in the configrued rate, callingforce_update()with twice the configured rate will actually send updates with twice the configured rate.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 think I see what you mean. In 18f5c77 I have re-introduced the
force_updatemethod to make it more explicit. The result of this is that theupdatefunction becomes private to avoid any confusion.