-
Notifications
You must be signed in to change notification settings - Fork 351
Allow timer rate to be configurable inmessage_lost_talker
#679
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
base: rolling
Are you sure you want to change the base?
Conversation
Signed-off-by: Yadunund <yadunund@gmail.com>
Signed-off-by: Yadunund <yadunund@gmail.com>
mjcarroll
left a comment
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.
Command line arg looks wrong.
Co-authored-by: Michael Carroll <michael@openrobotics.org> Signed-off-by: Yadu <yadunund@gmail.com>
| std::exit(0); | ||
| } | ||
| timer_period_ = std::chrono::duration_cast<std::chrono::milliseconds>( | ||
| std::chrono::duration<double, std::ratio<1>>(1.0 / timer_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.
if -r 0, this could generate 0 division exception?
|
@Yadunund friendly ping 🧇 |
|
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>
|
@Yadunund I applied the suggested changes. Do you mind to take a look ? |
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.