Allow timer rate to be configurable inmessage_lost_talker#679
Open
Allow timer rate to be configurable inmessage_lost_talker#679
message_lost_talker#679Conversation
Signed-off-by: Yadunund <yadunund@gmail.com>
Signed-off-by: Yadunund <yadunund@gmail.com>
Yadunund
requested review from
adityapande-1995,
audrow and
mjeronimo
as code owners
mjcarroll
requested changes
May 5, 2024
Member
mjcarroll
left a comment
mjcarroll
left a comment
There was a problem hiding this comment.
Command line arg looks wrong.
Co-authored-by: Michael Carroll <michael@openrobotics.org> Signed-off-by: Yadu <yadunund@gmail.com>
fujitatomoya
requested changes
May 6, 2024
| std::exit(0); | ||
| } | ||
| timer_period_ = std::chrono::duration_cast<std::chrono::milliseconds>( | ||
| std::chrono::duration<double, std::ratio<1>>(1.0 / timer_rate)); |
Collaborator
There was a problem hiding this comment.
if -r 0, this could generate 0 division exception?
Contributor
|
@Yadunund friendly ping 🧇 |
Member
Author
|
Sorry for the delay. Will have this cleaned up by end of this week |
Co-authored-by: Tomoya Fujita <Tomoya.Fujita@sony.com> Signed-off-by: Alejandro Hernández Cordero <ahcorde@gmail.com>
Co-authored-by: Tomoya Fujita <Tomoya.Fujita@sony.com> Signed-off-by: Alejandro Hernández Cordero <ahcorde@gmail.com>
Signed-off-by: Alejandro Hernandez Cordero <ahcorde@gmail.com>
ahcorde
approved these changes
Oct 6, 2025
Contributor
|
@Yadunund I applied the suggested changes. Do you mind to take a look ? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
By default the talker publishes an 8mB message every 3 seconds. I haven't been able to reproduce any message lost callback triggers with such a low frequency. It helps to increase the publishing rate.
This PR
-rCLI arg tomessage_lost_talkerto configure the timer's period. Default behavior is still the same 3s period.best_effortto increase the probability of dropping a message. -> I can undo this change if needed.