Practice data

[Majd-ui]

How long till I can access the practice data

[walteij]

Wel, I tried getting the practice data using the livetiming, but am getting an error when trying to load it:

Traceback (most recent call last): File "%APPDATA%\Python\Python39\site-packages\fastf1\core.py", line 1407, in _drivers_results_from_ergast data = ergast.fetch_results( File "%APPDATA%\Python\Python39\site-packages\fastf1\ergast.py", line 25, in fetch_results return _parse_ergast(fetch_day(year, gp, day))[0][sel] IndexError: list index out of range Traceback (most recent call last): File "<stdin>", line 1, in <module> File "%APPDATA%\Python\Python39\site-packages\fastf1\core.py", line 1056, in load raise NoLapDataError fastf1.core.NoLapDataError: Failed to load session because the API did not provide any usable data.

[theOehrly]

I'll test it with a recording of FP2.

[markste-in]

Have the same issue

sess = ff1.get_session(2022,1,'FP1')
laps = sess.load()

core           INFO 	Loading data for Bahrain Grand Prix - Practice 1 [v2.2.0]
api            INFO 	Using cached data for driver_info
core          ERROR 	Failed to load data from Ergast API!
Traceback (most recent call last):
  File "/opt/homebrew/Caskroom/miniforge/base/envs/f1alpha/lib/python3.10/site-packages/fastf1/core.py", line 1407, in _drivers_results_from_ergast
    data = ergast.fetch_results(
  File "/opt/homebrew/Caskroom/miniforge/base/envs/f1alpha/lib/python3.10/site-packages/fastf1/ergast.py", line 25, in fetch_results
    return _parse_ergast(fetch_day(year, gp, day))[0][sel]
IndexError: list index out of range

[theOehrly]

core ERROR Failed to load data from Ergast API!
This line is valid. It takes longer until the additional information on Ergast is available after a session than it takes for the timing and telemetry data to be available. The following traceback shouldn't be printed though because the error really is expected here. But all the data except for the session results should still be loaded correctly, and you can work with it.
So this is not really a problem. It looks worse than it is.

[markste-in]

Unfortunately I just get NoneType back.

It also tells me that I cannot use load() with with_telemetry=True

sess = ff1.get_session(2022,1,'FP1')
laps = sess.load(with_telemetry=True)

TypeError: Session.load() got an unexpected keyword argument 'with_telemetry'

load_laps() works even tho it tells me it is depreceated

[theOehrly]

Yes, session.load does not work exactly the same as .load_laps does.
Because .load really does not only load lap timing data but also telemetry, driver lists, results and weather data, I decided that it does not make sense, in terms of api consistency, to then only return the laps data. Therefore, after calling .load, the data can be accessed (as was previously already the case) through the properties session.laps, session.results, session.weather_data and others.
Also, .load now has more keyword arguments to allow finer control over what data should be loaded. These are named differently and all of them default to true.
.load_laps in the latests release only wraps .load to provide backwards compatibility.

[theOehrly]

I'd say it takes 30 to 60 minutes usually

[Majd-ui]

Ok thank you

[walteij]

Data is there :)

[Majd-ui]

yes it is

[markste-in]

Just a simple question ( prob. just doing it wrong): There seems to be no speed / time data or does it take a little longer to process it?

sess = ff1.get_session(2022,1,'FP1')
laps = sess.load()
for d in sess.results.Abbreviation: # or sess.driver
    try:
        sess.laps.pick_driver(d).get_telemetry()
    except Exception as e:
        print(f'{d} : {e}')

VER : 'SessionTime'
SAI : Telemetry does not contain required channels 'Time' and 'Speed'.
MSC : Telemetry does not contain required channels 'Time' and 'Speed'.
HAM : Telemetry does not contain required channels 'Time' and 'Speed'.
OCO : Telemetry does not contain required channels 'Time' and 'Speed'.
HUL : Telemetry does not contain required channels 'Time' and 'Speed'.
ZHO : Telemetry does not contain required channels 'Time' and 'Speed'.
ALB : 'SessionTime'
TSU : Telemetry does not contain required channels 'Time' and 'Speed'.
MAG : Telemetry does not contain required channels 'Time' and 'Speed'.
STR : Telemetry does not contain required channels 'Time' and 'Speed'.
LEC : Telemetry does not contain required channels 'Time' and 'Speed'.
PER : 'SessionTime'
GAS : 'SessionTime'
LAT : Telemetry does not contain required channels 'Time' and 'Speed'.
NOR : Telemetry does not contain required channels 'Time' and 'Speed'.
RIC : Telemetry does not contain required channels 'Time' and 'Speed'.
RUS : Telemetry does not contain required channels 'Time' and 'Speed'.
BOT : Telemetry does not contain required channels 'Time' and 'Speed'.

[theOehrly]

It hasn't changed. get_telemetry should work too. Both have existed since quite some time and are slightly different.

[markste-in]

hmmm... i can't get it to work anymore with get_telemetry. Same code works with get_car_data works 🤔

[theOehrly]

That's weird. I'll have to test it and see why that is the case.
But, if you're code works with get_car_data, you should prefer that over get_telemetry. You will get somewhat better results, because no interpolation of the source data is applied.

[theOehrly]

@markste-in Ok, so this is a bug that occurs when getting telemetry for multiple laps but only in some cases where NaT values exist in the laps data. This bug has to have existed since quite a while. It will be fixed in the next release.

[markste-in]

Yes I used a workaround and did a try/except with a if "Speed" in df.columns