NILKANTHABAG / repository

PUBG-EDA-Hackathon

PUBG Data Description In a PUBG game, up to 100 players start in each match (matchId). Players can be on teams (groupId) which get ranked at the end of the game (winPlacePerc) based on how many other teams are still alive when they are eliminated. In game, players can pick up different munitions, revive downed-but-not-out (knocked) teammates, drive vehicles, swim, run, shoot, and experience all of the consequences -- such as falling too far or running themselves over and eliminating themselves. You are provided with a large number of anonymized PUBG game stats, formatted so that each row contains one player's post-game stats. The data comes from matches of all types: solos, duos, squads, and custom; there is no guarantee of there being 100 players per match, nor at most 4 players per group. File descriptions data.csv - 151MB Data fields DBNOs - Number of enemy players knocked. assists - Number of enemy players this player damaged that were killed by teammates. boosts - Number of boost items used. damageDealt - Total damage dealt. Note: Self inflicted damage is subtracted. headshotKills - Number of enemy players killed with headshots. heals - Number of healing items used. Id - Player’s Id killPlace - Ranking in match of number of enemy players killed. killPoints - Kills-based external ranking of players. (Think of this as an Elo ranking where only kills matter.) If there is a value other than -1 in rankPoints, then any 0 in killPoints should be treated as a “None”. killStreaks - Max number of enemy players killed in a short amount of time. kills - Number of enemy players killed. longestKill - Longest distance between player and player killed at time of death. This may be misleading, as downing a player and driving away may lead to a large longestKill stat. matchDuration - Duration of match in seconds. matchId - ID to identify matches. There are no matches that are in both the training and testing set. matchType - String identifying the game mode that the data comes from. The standard modes are “solo”, “duo”, “squad”, “solo-fpp”, “duo-fpp”, and “squad-fpp”; other modes are from events or custom matches. rankPoints - Elo-like ranking of players. This ranking is inconsistent and is being deprecated in the API’s next version, so use with caution. Value of -1 takes the place of “None”. revives - Number of times this player revived teammates. rideDistance - Total distance traveled in vehicles measured in meters. roadKills - Number of kills while in a vehicle. swimDistance - Total distance traveled by swimming measured in meters. teamKills - Number of times this player killed a teammate. vehicleDestroys - Number of vehicles destroyed. walkDistance - Total distance traveled on foot measured in meters. weaponsAcquired - Number of weapons picked up. winPoints - Win-based external ranking of players. (Think of this as an Elo ranking where only winning matters.) If there is a value other than -1 in rankPoints, then any 0 in winPoints should be treated as a “None”. groupId - ID to identify a group within a match. If the same group of players plays in different matches, they will have a different groupId each time. numGroups - Number of groups we have data for in the match. maxPlace - Worst placement we have data for in the match. This may not match with numGroups, as sometimes the data skips over placements. winPlacePerc - The target of prediction. This is a percentile winning placement, where 1 corresponds to 1st place, and 0 corresponds to last place in the match. It is calculated off of maxPlace, not numGroups, so it is possible to have missing chunks in a match. Link-https://www.kaggle.com/c/pubg-finish-placement-prediction/