-
Notifications
You must be signed in to change notification settings - Fork 269
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
Acoustic comms : Packet collision timeout #1755
Conversation
Signed-off-by: Aditya <aditya050995@gmail.com>
Signed-off-by: Aditya <aditya050995@gmail.com>
Signed-off-by: Aditya <aditya050995@gmail.com>
Codecov Report
@@ Coverage Diff @@
## gz-sim7 #1755 +/- ##
========================================
Coverage 64.19% 64.20%
========================================
Files 336 336
Lines 26830 26853 +23
========================================
+ Hits 17224 17241 +17
- Misses 9606 9612 +6
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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.
LGTM, but I don't follow what phenomena we are trying to model here.
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.
Seems reasonable to me. However, I would encourage us to actually allow users to set a "bit-rate" so that the packet collision also depends on the length of the packet. I don't believe this is too much extra work but would lead to a much more realistic
and usable model.
Signed-off-by: Aditya <aditya050995@gmail.com>
Signed-off-by: Aditya <aditya050995@gmail.com>
I'm pretty sure this is not breaking ABI, but the ABI checker is failing weirdly. |
ABI checker is having some issues at the moment. |
🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸
🎉 New feature
Summary
This PR adds a new tag
<collision_time_interval>
to the acoustic comms plugin. If an address endpoint receives two data packets within that time interval, the second one will be dropped. The timeout value defaults to zero, so no packets are ever dropped if the tag is unspecified.The time must be in seconds.
Test it
Added an integration test using
acoustic_comms_packet_collision.sdf
. If multiple packets are sent during a 1 second time interval, they will be dropped. In the test, I send 3 packets, and only the first one of them is received.Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining
Signed-off-by
messages.🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸