Replies: 1 comment
-
I finally got around to investigating this. Can confirm that this is in fact a bug in the API parser code. The bug is causing the NaN values as well as the incorrect compound shown. No ETA though for when I'll have a fix for it. I'm rather busy at the moment. Just in general, I will not automatically fill in nan values with an assumption for tyre life. The api should remember tyre age over multiple sessions. Therefore, it will often be wrong to assume TyreLife = 1 at the beginning of a stint. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For Canadian GP race session, when we select the fastest laps for each driver. In the
TyreLife
column we have NaNs for 'RUS' and 'NOR'. A suggestion would be to fill NaNs assuming TyreLife as 1 for first lap after pit stopWhen I looked into 'NOR' laps data, on
LapNumber
43, he is onStint
3 onCompound
HARD, but for next lap(LapNumber=44), he is still onStint
3 but onCompound
MEDIUM. Lando had a pit stop on Lap 42 according to the official data here I'm quite confused.Beta Was this translation helpful? Give feedback.
All reactions