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

[BUG] Duplicate lap times in source data for GRO incorrectly handled in 2020 Round 4 #612

Open
theOehrly opened this issue Jul 9, 2024 · 0 comments
Labels
bug Something isn't working
Milestone

Comments

@theOehrly
Copy link
Owner

Describe the issue:

The source data for the 2020 Round 4 race (British GP) contains some duplicate lap times for GRO (car 8) around lap 14 and 15.
More preicesly, the lap time for lap 14 is received again after the lap time for lap 15 was already received and the lap count had been increased. The lap time for lap 15 is then received again a few seconds later.
This should cause the correct value to be set for lap 15, but the value of the lap time for lap 15 is greater than 150 seconds and therefore ignored by the timing parser (see #473). Therefore, the value of lap 14 is used for both lap 14 and 15, resulting in a subsequent timing integrity error.

Potentially related as well: #404

Reproduce the code example:

import fastf1

session = fastf1.get_session(2020, 4, 'R')
session.load()

Error message:

core           INFO 	Loading data for British Grand Prix - Race [v3.5.0.dev2]
_api           INFO 	Fetching session info data...
_api           INFO 	Fetching driver list...
_api           INFO 	Fetching session status data...
_api           INFO 	Fetching lap count data...
_api           INFO 	Fetching track status data...
_api           INFO 	Fetching timing data...
_api           INFO 	Parsing timing data...
_api        WARNING 	Driver  4: Ignoring late data for a previously processed lap.The data may contain errors (previous: 35; current 36)
_api        WARNING 	Driver  8: Encountered 1 timing integrity error(s) near lap(s): [15].
This might be a bug and should be reported.
_api        WARNING 	Skipping lap alignment (no suitable lap)!
_api           INFO 	Fetching timing app data...
core           INFO 	Processing timing data...
_api           INFO 	Fetching car data...
_api           INFO 	Parsing car data...
_api           INFO 	Fetching position data...
_api           INFO 	Parsing position data...
_api        WARNING 	Driver 241: Position data is incomplete!
_api        WARNING 	Driver 242: Position data is incomplete!
_api        WARNING 	Driver 243: Position data is incomplete!
_api           INFO 	Fetching weather data...
_api           INFO 	Fetching race control messages...
core           INFO 	Finished loading data for 20 drivers: ['44', '33', '16', '3', '4', '31', '10', '23', '18', '5', '77', '63', '55', '99', '6', '8', '7', '26', '20', '27']
@theOehrly theOehrly added the bug Something isn't working label Jul 9, 2024
@theOehrly theOehrly added this to the future milestone Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant