Coder Social home page Coder Social logo

invinciblejuggernaut / f1-calendar Goto Github PK

View Code? Open in Web Editor NEW
0.0 1.0 0.0 1.69 MB

An attempt to create an optimized F1 calendar to cut down unnecessary travelling back and forth between continents during a F1 season.

License: MIT License

Python 100.00%
travelling-salesman-problem python f1-season formula1 sports optimisation-algorithms

f1-calendar's Introduction

F1-Calendar

Introduction

F1 is the world's most watched and followed motorsports category. A F1 season comprises of almost a dozen and a half races to be held across almost 10 months over different circuits in different countries. The 2020 calendar comprises of 22 races. In light of recent awarenss about carbon footprint of humans and their activites as a whole, which impacts the planet directly and us indirectly, F1 recently decided to make the sport more "planet-friendly". In 2014, they decided to use hybrid engines which are 50% more efficent than the previous V10s. In 2019, F1 decided to go one step further. They announced their plans to have net zero carbon footprint by 2030.

Technologies/Languages/Libraries

Objective

Inspired by F1's plans, I tried my hands at solving their fixtures issue.
The 2020 season will go on as follows :
  • Melbourne
  • Sakhir
  • Hanoi
  • Shanghai
  • Zandvoort
  • Barcelona
  • Monaco
  • Baku
  • Montreal
  • Le Castellet
  • Spielberg
  • Silverstone
  • Budapest
  • Spa
  • Monza
  • Singapore
  • Sochi
  • Suzuka
  • Austin
  • Mexico City
  • Sao Palio
  • Abu Dhabi

Enclosed below is an map with the markers denoting the race venues spread across the globe.






Distance covered : 111500 kilometres. That's huge ! For comparison, radius of earth is 6371 kilometres.
Do you observe how the season begins in Australia, goes to Middle-East in Bahrain, then again goes in the opposite direction to Vietnam in Asia, then Shangai and then Netherlands only to return to Asia again 10 rounds later !

To emphasise this point, I would like to tell you about the summer break in between the season. It's usually a gap of 3 weeks which takes place during July-August. During this period, no races take place. So, the first half of the season ends by the race at Hungary and then the season again resumes some 3 weeks later at Belgium. According to the original schedule, I have created another map which shows the races in the first half with red indicators and the races after the break with green indicators. This can be achieved by tweaking the code here.


From this, one can see that the races are spread all over the continents. After having some races in Europe in the first half of the season, the competition again returns to Europe in the second half.





This is an attempt to create an optimized F1 calendar to cut down unecessary travelling back and forth between continents during a F1 season.

Results

Personally, I was bewildered by the solutions I got from this program. They seemed too good to be true !
Such a schedule mightn't make a mammoth difference, but definitely would be a good step in the right direction. The optimized calendar turns out to be :
  • Melbourne
  • Singapore
  • Hanoi
  • Shangai
  • Suzuka
  • Abu Dhabi
  • Sakhir
  • Baku
  • Sochi
  • Budapest
  • Spielberg
  • Monza
  • Monaco
  • Le Castellet
  • Barcelona
  • Spa
  • Zandvoort
  • Silverstone
  • Montreal
  • Austin
  • Mexico
  • Sao Paulo


The second map gets altered with striking differences after following this newly obtained order. It is clearly visible that the races follow a more coherent schedule. The races before the halfway point of the seaon are marked with red markers and the others are marked with green markers. Take a look.




Conclusions

Yeah, Abu Dhabi won't be the season finale. It's not the most popular among us anyway. Brazil will get to host the finale and it does produce brilliant races. So, no issues there.
Distance covered : 43703 kilometres That's a 60% decrease in distance covered compared to the original schedule.


This is a work in progress. F1 is a huge sport with huge logistical headaches. It's not just about 20 cars racing around in circles ! There is a lot to consider in terms of marketing, gaining the biggest crowd possible during the events, planning to avoid extreme weather conditions and many other parameters which us, the fans don't concern too much about. Yet, making such changes to the schedule which drastically reduces the carbon footprint and removes Abu Dhabi as the season finale shouldn't hurt anyone and would be a welcome decision among the F1 fandom.

License

MIT License

f1-calendar's People

Contributors

invinciblejuggernaut avatar

Watchers

 avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.