This article was published as a part of the Data Science Blogathon.
In this article, I am going to cluster some of the popular video games according to their given features. I have done this project while learning about the K-Means Clustering. After reading this article, you can able to:
I am writing this article in such a way that anyone can understand what I am doing. So, take a cup of coffee and read on.
Let’s import the necessary packages. The packages are given below.
Now I read the data using pandas and then do some preprocessing steps on data before feeding the data into the model and gaining insights about the data. The data is in CSV format. You can download the data from my GitHub repo.
data = pd.read_csv("data/video_games.csv")
if you print the top 5 rows in this dataset, the table will look something like this.
From the above images, we can easily notice that there are 9 columns in this data. Those are:
Now, Let’s see if there are any null values available in the dataset. For this, run the below code.
plt.figure(figsize=(10,8))
sns.heatmap(data.isnull(), cmap='magma', yticklabels=False)
if you run this code, the output will look something like the below.
Let’s see the number of null values numerically.
data.isnull().sum()
Woah! there exist so many null values in the dataset. So for better imputation, I am using the KNearestNeighbors algorithm from the fancyimpute package. But before doing that, I want to remove some of the null values:
I also want to drop some columns. release_date and achievements neither matter for searching for a game nor determining the genre. and for now, I am removing the original_price column for simplicity. If you have previously seen the table, the original_price column contains mixed values. Below is the image of 50 unique values of the original_price column.
Just see the image. Some of the games are free and some of them are paid. But there is no way that I can change this column data type. So, I am dropping this column.
data.drop(['release_date', 'achievements', 'original_price'], axis=1, inplace=True)
Now, Let’s drop the null values.
After dropping all the unnecessary rows, now the size of the dataset is (40748, 6). As this is a huge dataset, I have to take a small part of this. I took two parts from the data. One for training and one for testing. After that, I encode the categorical variables and impute them.
If everything is fine, the first 5 rows for train and test will look like this after encoding.
Now it’s the time for imputation. but before that, we have to install fancyimpute. You can install this by running the below command.
pip install fancyimpute
After the successful installation, we can use the KNN algorithm from fancyimpute.
Now, if you want to verify that there are no null values in the dataset, just run the below code.
print(data1.isnull().sum())
print(data2.isnull().sum())
You will get the below output for both:
After imputing all the values and verifying them, now it is time for modeling. According to the problem we have to classify using clustering techniques. I am using K-Means Clustering here. before feeding this data into the model, we have to encode it again.
Now I am going to extract the important features using Principal Component Analysis (PCA). Without this, K-Means works very badly in clustering the data.
Here I am taking two components for PCA. You can try with different numbers.
Now there is a question that how to determine the number of clusters in K-means. there are two methods for this – silhouette score and elbow method. I am using the Elbow method here. We have to plot a graph on different inertias based on different cluster numbers in this method. we have to choose a cluster number from where there is minimal change in values. as this graph seems to be a human’s elbow, so this method name is the elbow method.
If you run the above code, you will get the below output.
From this graph, we can see that 2 is the desired cluster number.
Now we are ready for clustering😁.
If the code is running successfully, you can see the below plot.
after training the model on 2 clusters and predicting on the training set, this is the result of the machine clustering the games into two sections. though I don’t include the price column here, the machine still clusters them into two parts. Let’s see the results in the testing set.
If you run the above code, you can see the below plot:
The games are also divided into the two clusters, but the data points are missing for cluster 2. The testing set may contain only those data points related to cluster 1.
From the above two plots, we can clearly say that the model successfully makes the distinction between the two categories.
The Video Game Clustering Model can be improved by
So, that’s all for today. I hope you like this article. If you want to know about me and want to read my other articles, visit here. For now, goodbye👋.
The media shown in this article is not owned by Analytics Vidhya and is used at the Author’s discretion.
Recently pursuing M.Tech in Artificial Intelligence and love to do anything about Data Science, Machine Learning, and AI. I also like to share my knowledge through Blogs. Ask me anything about Data Science, Machine Learning, and AI at [email protected].
Clustering | Different Methods, and Application...
A Quick Tutorial on Clustering for Data Science...
K-Means clustering with Mall Customer Segmentat...
Clustering Machine Learning Algorithm using K M...
Introduction to K-Means Clustering using MLIB
Understanding KMeans Clustering for Data Scienc...
Simple Explanation To Understand K Means Cluste...
Beginner’s Guide to Clustering in R Program
Understanding Fuzzy C Means Clustering
Introduction to Clustering in Python for Beginn...
We use cookies essential for this site to function well. Please click to help us improve its usefulness with additional cookies. Learn about our use of cookies in our Privacy Policy & Cookies Policy.
Show details
This site uses cookies to ensure that you get the best experience possible. To learn more about how we use cookies, please refer to our Privacy Policy & Cookies Policy.
It is needed for personalizing the website.
Expiry: Session
Type: HTTP
This cookie is used to prevent Cross-site request forgery (often abbreviated as CSRF) attacks of the website
Expiry: Session
Type: HTTPS
Preserves the login/logout state of users across the whole site.
Expiry: Session
Type: HTTPS
Preserves users' states across page requests.
Expiry: Session
Type: HTTPS
Google One-Tap login adds this g_state cookie to set the user status on how they interact with the One-Tap modal.
Expiry: 365 days
Type: HTTP
Used by Microsoft Clarity, to store and track visits across websites.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Persists the Clarity User ID and preferences, unique to that site, on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Connects multiple page views by a user into a single Clarity session recording.
Expiry: 1 Day
Type: HTTP
Collects user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Years
Type: HTTP
Use to measure the use of the website for internal analytics
Expiry: 1 Years
Type: HTTP
The cookie is set by embedded Microsoft Clarity scripts. The purpose of this cookie is for heatmap and session recording.
Expiry: 1 Year
Type: HTTP
Collected user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Months
Type: HTTP
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected includes the number of visitors, the source where they have come from, and the pages visited in an anonymous form.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics, to store and count pageviews.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit.
Expiry: 1 Day
Type: HTTP
Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels.
Expiry: Session
Type: PIXEL
cookies ensure that requests within a browsing session are made by the user, and not by other sites.
Expiry: 6 Months
Type: HTTP
use the cookie when customers want to make a referral from their gmail contacts; it helps auth the gmail account.
Expiry: 2 Years
Type: HTTP
This cookie is set by DoubleClick (which is owned by Google) to determine if the website visitor's browser supports cookies.
Expiry: 1 Year
Type: HTTP
this is used to send push notification using webengage.
Expiry: 1 Year
Type: HTTP
used by webenage to track auth of webenagage.
Expiry: Session
Type: HTTP
Linkedin sets this cookie to registers statistical data on users' behavior on the website for internal analytics.
Expiry: 1 Day
Type: HTTP
Use to maintain an anonymous user session by the server.
Expiry: 1 Year
Type: HTTP
Used as part of the LinkedIn Remember Me feature and is set when a user clicks Remember Me on the device to make it easier for him or her to sign in to that device.
Expiry: 1 Year
Type: HTTP
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Used to store information about the time a sync with the AnalyticsSyncHistory cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Cookie used for Sign-in with Linkedin and/or to allow for the Linkedin follow feature.
Expiry: 6 Months
Type: HTTP
allow for the Linkedin follow feature.
Expiry: 1 Year
Type: HTTP
often used to identify you, including your name, interests, and previous activity.
Expiry: 2 Months
Type: HTTP
Tracks the time that the previous page took to load
Expiry: Session
Type: HTTP
Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings
Expiry: Session
Type: HTTP
Tracks percent of page viewed
Expiry: Session
Type: HTTP
Indicates the start of a session for Adobe Experience Cloud
Expiry: Session
Type: HTTP
Provides page name value (URL) for use by Adobe Analytics
Expiry: Session
Type: HTTP
Used to retain and fetch time since last visit in Adobe Analytics
Expiry: 6 Months
Type: HTTP
Remembers a user's display preference/theme setting
Expiry: 6 Months
Type: HTTP
Remembers which users have updated their display / theme preferences
Expiry: 6 Months
Type: HTTP
Used by Google Adsense, to store and track conversions.
Expiry: 3 Months
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 6 Hours
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 1 Month
Type: HTTP
These cookies are used to gather website statistics, and track conversion rates.
Expiry: 1 Month
Type: HTTP
Aggregate analysis of website visitors
Expiry: 6 Months
Type: HTTP
This cookie is set by Facebook to deliver advertisements when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website.
Expiry: 4 Months
Type: HTTP
Contains a unique browser and user ID, used for targeted advertising.
Expiry: 2 Months
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 1 Year
Type: HTTP
Used by LinkedIn for tracking the use of embedded services.
Expiry: 1 Day
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 6 Months
Type: HTTP
Use these cookies to assign a unique ID when users visit a website.
Expiry: 6 Months
Type: HTTP
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
Expiry: 6 Months
Type: HTTP
Used to make a probabilistic match of a user's identity outside the Designated Countries
Expiry: 90 Days
Type: HTTP
Used to collect information for analytics purposes.
Expiry: 1 year
Type: HTTP
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
Expiry: 1 Day
Type: HTTP
Cookie declaration last updated on 24/03/2023 by Analytics Vidhya.
Cookies are small text files that can be used by websites to make a user's experience more efficient. The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies, we need your permission. This site uses different types of cookies. Some cookies are placed by third-party services that appear on our pages. Learn more about who we are, how you can contact us, and how we process personal data in our Privacy Policy.
Edit
Resend OTP
Resend OTP in 45s