-
Notifications
You must be signed in to change notification settings - Fork 25
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
Target persistence #36
Comments
Hi True Motion probably takes a lot more CPU-power to calculate, when targets has to be corrected |
keesverruijt
added a commit
that referenced
this issue
Oct 12, 2014
Realised that it takes 2.5s for a full revolution of the radar scanner, so normal minimal age is 3 (s). Add control so users can change this between 1 (for testing) and 12 (seems plenty...) Fixes bug #36. # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # # Committer: Kees Verruijt <kees@kees-mbp.verruijt.lan> # # On branch master # Your branch is up-to-date with 'origin/master'. # # Changes to be committed: # modified: src/br24radar_pi.cpp # modified: src/br24radar_pi.h # modified: src/br24radarcontrol.cpp #
keesverruijt
added a commit
that referenced
this issue
Oct 30, 2014
Write a log message for every packet with != 32 scanlines/spokes. This is an attempt to be more robust. Issue #36.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Increase the number of turns a target is drawn before deletion. Now we check if a target echo is present the last three scanner turns before deletion. I've tried six turns with very good result especially for weak targets. Possible the number of turns could be adjustable.
Please consider to exclude the function when scanner range is changed, otherwise the redrawing will take longer time.
The text was updated successfully, but these errors were encountered: