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

Problem of relative data's accuracy #197

Open
NekoDisc opened this issue Mar 20, 2019 · 2 comments

Comments

@NekoDisc
Copy link

@NekoDisc NekoDisc commented Mar 20, 2019

SIMRacingApps's relative data has not enough accuracy.
In the worst case, it is near twice as time as ingame blackbox.
I hope that SIMRacingApps has more correctly relative data.

relative

@jfgilliam

This comment has been minimized.

Copy link
Contributor

@jfgilliam jfgilliam commented Mar 20, 2019

@NekoDisc

This comment has been minimized.

Copy link
Author

@NekoDisc NekoDisc commented Mar 21, 2019

I have an idea that perhaps relative's accuracy improve than now, but I have no confidence to explaining well in English.
However, I will try anyway.

  1. Make the checkpoints based on a distance from the control line.
    Divide the track every N meters and numbering it.
  2. Record the session time(not lap time) when passing every checkpoints about every cars.
  3. Compare a latest checkpoint time which has same number based on the car behind.
  4. Perhaps this logic need to override the checkpoint time which the car already passed If the car too slow.

Example:
relative
Car3 running at 310m
Car1-3, Use check point 3, 0.17
Car2-3, Use check point 3, 0.08
Car3-4, Use check point 2, -0.05
Car3-5, Use check point 2, -0.10

This idea has the problem that the large track like the Nordschleife need too many checkpoints.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.