Skip to content
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

Crossing Line Detection needs to end early #4

Open
TheAngryRaven opened this issue May 24, 2023 · 1 comment
Open

Crossing Line Detection needs to end early #4

TheAngryRaven opened this issue May 24, 2023 · 1 comment
Labels
enhancement New feature or request Library Work for the public library

Comments

@TheAngryRaven
Copy link
Owner

Problem

Currently we begin the crossing detection pretty far out due to the possibility of slow GPS updates.

Description

Memory constraints are really hitting some devices, we must find a way to reduce the buffer size down from the 500 data-points we are currently trying to save. The problem is we need to make sure this step in memory reduction doesn't hurt the reliability of detecting when the driver has cross a sector line.

Proposed Solution

  1. Once crossing process has started, save the current driver "line side"
  2. Once driver has passed the line, STOP LOGGING
    a. Ignoring if the driver is ON the line, lets get one more point ACROSS the line.
@TheAngryRaven
Copy link
Owner Author

Buffersize seems to be fine when shorter, need to investigate what happens when say, waiting for a race to start.

Ending the crossing algo early seems to cause an annoyance where it re-starts the crossing procedure, kind of a pain to figure out how to stop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Library Work for the public library
Projects
None yet
Development

No branches or pull requests

1 participant