Closed AND2797 closed 1 month ago
I'll take a look at the failing tests.
The chained [...][...]
write access is probably responsible for the Pandas warning.
I'm also not sure if we can really set 'Time' to NaT
. That might break getting telemetry data for the crash laps (and I'm not sure if there's a test for that). But we might need to leave the 'Time' as it is and only detect based on 'LapTime' being NaT
and maybe this being the last lap of that driver.
There is a special case in _load_laps_data to create data for drivers crashed in lap1. In that, previously we were assigning
data['Time'].min()
this was the source of the bug.I modified two things: assign time as pd.NaT for crashed drivers.
And while generating the position of drivers for the lap, assign np.NaN to drivers who have NaT/NaN times.