-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
adding rate loops where applicable #743
Merged
SteveMacenski
merged 4 commits into
ros-navigation:master
from
SteveMacenski:rate_loops
Jul 29, 2019
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
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 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 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 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
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.
I'm not sure this is safe. At this point in the code, the node isn't spinning yet. If it's not spinning, the ros clock can't advance when
use_sim_time
is active. This could deadlock.It may not be a failure in practice because, last time I checked,
Rate
used the wall clock instead of the ros clock, however that seems like a bug to me and may change. I'd say we should only make this change if we are confident that Rate objects should always use wall clock time and never the simulation clock.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.
From this ticket: https://answers.ros.org/question/319510/rclcpprate-doesnt-use-ros-time-use_sim_time/
I'd venture to say it will not remain that way. However, even if the node hasn't been put in spin, that has never before stopped the ros clock - that's usually been a separate library that can be instantiated separately of even a ros node. I can't think of a reason why the node not yet having called spin would stop the clock.
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.
It's not that way anymore. The clock updates come in as a message on the /clock topic and the node has to spin to process that message and advance the clock
At least, that's the way it was a few months ago.
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.
Got it, OK. I think all 3 need throttling (especially the service caller). I will redo using non-ros clock implementations.
Thanks for the deep look