Wot, no weather?

[GorseddRock]

Hi,

I'm trying to extract weather data for Qualifying sessions and am trying to find out if there is any definitive list of where weather data is present. I am finding that there is a mix of years data available. Extract from my code:

theStrtYr = 2020
interestingEvents = ["conventional","sprint","sprint_shootout","sprint_qualifying"]
  theEndYr = 2025
  for thsYear in range(theStrtYr,theEndYr+1):
      thsSchedule = fastf1.get_event_schedule(thsYear)
      thsSeasonLgth = len(thsSchedule)
      for thsEvent in range (0,thsSeasonLgth):
          if thsSchedule.EventFormat[thsEvent] in interestingEvents:
            thsRoundNo = thsSchedule.RoundNumber[thsEvent]
            thsEventName = thsSchedule.EventName[thsEvent]
            #for each session of this weekend
            for thsSessNo in range(1,5+1):
                try:
                    session = fastf1.get_session(thsYear, thsRoundNo, thsSessNo)
                    thsSessionName = session.name
                    if 'Qual' in session.name:
                        session.load(weather=True)
                        thsResults = session.weather_data.iloc[0:len(session.weather_data),[0,1,4,5,6,7]] `

So for this range I find:
2020: no weather data
2021: complete season of weather data
2022: no weather data
2023: no weather data
2024: complete season
2025: complete season

I'm running on version 3.8.2 of fastf1.

I'm not quite a newbie to python, but happy to accept I've done something stupid, but be gentle with me!

Any suggestions gratefully received!

[theOehrly]

I only looked at some random samples in 2020, 2022 and 2023 just now, but I do also get weather data in those seasons. So this seems to be a problem on your end.

Note that if you run the script as shown above, chances are high that some API server involved will rate-limit you. My rough estimate for the script are multiple thousand requests per hour and servers might not tolerate that. This could be part of your problem.

[GorseddRock]

Thanks for looking - I was worried it was my skills.
I'm surprised about the number of requests you mention, but that's part of my lack of knowledge. I would assume:

Ask for the schedule in this year - 1 query, probaby 24 (or so) events for 6 schedules. So my assumption is six requests?
Then for each event in each season, look at each event: 6 years, 24 events per year, 144 requests..
Then for each sesssion in each event, look to see if it's a qualifying event - 144 events, maybe 5 sessions per event 5 * 144 = , for 6 years is 720 requests.

I think you get the idea: I don't understand how these requests become the number you mention. Can you point me at some resource that would explain, or would you have the time to give an idiots guide to why I am so wrong?

Thanks in advance,

Richard

[theOehrly]

One request for get_event_schedule, one request for get_session and at least ten requests for session.load, if I remember correctly.
But I had missed that you're only calling session.load if it's a qualifying session. Still, the total number will be >1000 on the first run of this script and only lower afterward once data is cached locally.

[mclarenmp4-22]

I'm getting weather for every session since 2018 as far as I have checked

[GorseddRock]

Ok, so that seems to confirm it's me. I'll try harder..... Thanks for your help, both. Richard I'm getting weather for every session since 2018 as far as I have checked — Reply to this email directly, view it on GitHub , or unsubscribe . Triage notifications on the go with GitHub Mobile for iOS or Android . You are receiving this because you authored the thread. Message ID: <theOehrly/Fast-F1/repo-discussions/900/comments/16814965 @ github . com>