Envision Racing
Can your data-science skills help Envision Racing, take home even more trophies?
@kaggle.pavan9065_envision_racing
Can your data-science skills help Envision Racing, take home even more trophies?
@kaggle.pavan9065_envision_racing
In the heat of a Formula E race, teams need fast access to insights that can help drivers make split-second decisions and cross the finish line first. Can your data-science skills help Envision Racing, one of the founding teams in the championship, take home even more trophies?
To do so, you will have to build a machine learning model that predicts the Envision Racing drivers’ lap times for the all-important qualifying sessions that determine what position they start the race in. Winning races involve a combination of both a driver’s skills and data analytics. To help the team you’ll need to consider several factors that affect performance during a session, including weather, track conditions, and a driver’s familiarity with the track.
Genpact, a leading professional services firm that focuses on digital transformation, is collaborating with Envision Racing, a Formula E racing team and digital hackathon platform MachineHack, a brainchild of Analytics India Magazine, is launching ‘Dare in Reality’.’ This two-week hackathon allows data science professionals, machine learning engineers, artificial intelligence practitioners, and other tech enthusiasts to showcase their skills, impress the judges, and stand a chance to win exciting cash prizes.
Genpact (NYSE: G) is a global professional services firm that makes business transformation real, driving digital-led innovation and digitally-enabled intelligent operations for our clients.
test.csv - 420 rows x 25 columns(Includes target column as LAP_TIME)
submission.csv -Please check the Evaluation section for more details on how to generate a valid submission.
The challenge is to predict the LAP_TIME for the qualifying groups of locations 6, 7 and 8.
Knowledge and Skills
CREATE TABLE submission (
"lap" BIGINT,
"time" VARCHAR
);CREATE TABLE test (
"number" BIGINT,
"n__driver_number" BIGINT -- DRIVER NUMBER,
"n__lap_number" BIGINT -- LAP NUMBER,
"lap_time" VARCHAR,
"n__lap_improvement" BIGINT -- LAP IMPROVEMENT,
"n__crossing_finish_line_in_pit" VARCHAR -- CROSSING FINISH LINE IN PIT,
"n__s1" VARCHAR -- S1,
"n__s1_improvement" BIGINT -- S1 IMPROVEMENT,
"n__s2" VARCHAR -- S2,
"n__s2_improvement" BIGINT -- S2 IMPROVEMENT,
"n__s3" VARCHAR -- S3,
"n__s3_improvement" BIGINT -- S3 IMPROVEMENT,
"n__kph" DOUBLE -- KPH,
"n__elapsed" VARCHAR -- ELAPSED,
"n__hour" VARCHAR -- HOUR,
"s1_large" VARCHAR,
"s2_large" VARCHAR,
"s3_large" VARCHAR,
"driver_name" VARCHAR,
"pit_time" VARCHAR,
"group" DOUBLE,
"team" VARCHAR,
"power" DOUBLE,
"location" VARCHAR,
"event" VARCHAR
);CREATE TABLE test_weather (
"time_utc_seconds" BIGINT,
"time_utc_str" VARCHAR,
"air_temp" BIGINT,
"track_temp" BIGINT,
"humidity" BIGINT,
"pressure" BIGINT,
"wind_speed" BIGINT,
"wind_direction" BIGINT,
"rain" BIGINT,
"location" VARCHAR,
"events" VARCHAR
);CREATE TABLE train (
"number" BIGINT,
"n__driver_number" BIGINT -- DRIVER NUMBER,
"n__lap_number" BIGINT -- LAP NUMBER,
"lap_time" BIGINT,
"n__lap_improvement" BIGINT -- LAP IMPROVEMENT,
"n__crossing_finish_line_in_pit" VARCHAR -- CROSSING FINISH LINE IN PIT,
"n__s1" VARCHAR -- S1,
"n__s1_improvement" BIGINT -- S1 IMPROVEMENT,
"n__s2" VARCHAR -- S2,
"n__s2_improvement" BIGINT -- S2 IMPROVEMENT,
"n__s3" VARCHAR -- S3,
"n__s3_improvement" BIGINT -- S3 IMPROVEMENT,
"n__kph" DOUBLE -- KPH,
"n__elapsed" VARCHAR -- ELAPSED,
"n__hour" VARCHAR -- HOUR,
"s1_large" VARCHAR,
"s2_large" VARCHAR,
"s3_large" VARCHAR,
"driver_name" VARCHAR,
"pit_time" VARCHAR,
"group" DOUBLE,
"team" VARCHAR,
"power" DOUBLE,
"location" VARCHAR,
"event" VARCHAR
);CREATE TABLE train_weather (
"time_utc_seconds" BIGINT,
"time_utc_str" VARCHAR,
"air_temp" DOUBLE,
"track_temp" DOUBLE,
"humidity" BIGINT,
"pressure" DOUBLE,
"wind_speed" DOUBLE,
"wind_direction" BIGINT,
"rain" BIGINT,
"location" VARCHAR,
"event" VARCHAR
);Anyone who has the link will be able to view this.