You can’t rest on your #1 ranking-because the guy at #2 isn’t resting. He’s still improving his site — Ryan Jones
We all come across different multi-criteria decision-making problems in our day to day life. Example — Shopping: Which one product should I buy out of X candidate products?
Ranking problems are the most interesting problems a data scientist gets to solve. Like such, I recently came across a ranking problem where we wanted to rank users and pick top K which are most beneficial for our business. To this problem, there is also a catch that right now I have no data to work on meaning this is a cold start problem where data will flow in with time.
Knowing the fact that I have zero training data points, I was sure there would be a better way to handle a ranking problem with multiple-criteria and came across this interesting publication “Triantaphyllou, E. (2000). Multi-criteria decision-making methods. In Multi-criteria decision making methods: A comparative study (pp. 5–21). Springer, Boston, MA.” which teaches about Multi-Criteria Decision Making Methods(MCDM).
Multiple criteria decision-making (MCDM) or Multi-criteria decision analysis (MCDA) is considered as a complex decision-making (DM) tool involving both quantitative and qualitative factors.
After defining the first four key steps (image above) of Multi-Criteria Decision Making Methods(MCDM), in step 5 we process the numerical values to determine a ranking of each alternative.
To do this processing and ranking of different entities with multi-criteria we can use the following algorithms: WSM, WPM, AHP, revised AHP, ELECTRE, TOPSIS, and MOORA methods.
This is the simplest and most commonly used of all. We all have seen this in our school/college report cards too where the objective is to find:
Which student ranked first in a class?
Criteria are defined as — different subjects of a student
Weights of criteria — are credit scores assigned to a particular subject.
WSM Formula —
where: A*WSM-score is the WSM score of the best alternative, n is the number of decision criteria, aij is the actual value of the ith alternative in terms of the jth criterion, and Wj is the weight of importance of the jth criterion.
NOTE: It is very important to state here that WSM is applicable only when all the data are expressed in exactly the same unit (like in report card marks). If this is not the case, then the final result is equivalent to “adding apples and oranges.”
WPM is very similar to above WSM, the main difference is that instead of adding in the model there is multiplication.
One may face the problem of INT Overflow as we are doing multiplication of exponential numbers to handle that use this modification (adding logarithm)to the original formula:
NOTE: WPM only gives alternatives performance value, not the relative ones i.e. we here are doing the pointwise ranking.
In the AHP method, we do a pairwise comparison between different alternatives and then rank them.
AHP method was release two times, the first version [Saaty, 1980] stated to normalize the alternate matrix in such a way that the relative values for each criterion sum up to one.
Then this AHP method was revised by Belton and Gear [1983] who proved that the relative values for each criterion sum up to one is causing ranking inconsistency. Instead of having the relative values of the alternatives A1, A2, A3, …, Am sum up to one, they proposed to divide each relative value by the maximum value of the relative values.
The similarity between the WSM and the AHP is clear. The AHP uses relative values instead of actual ones. Thus, it can be used in single- or multi-dimensional decision-making problems.
Method1 — States that the relative values for each criterion sum up to one.
After Normalization by Method1
AHP Score — (0.45, 0.47, 0.08) → A2>A1>A3
On the above matrix, we introduce a new alternative, say A4, which is identical to A2 (i.e., A2 == A4)
AHP Score —(0.37, 0.29, 0.06, 0.29)→ A1>A2=A4>A3
This creates ranking inconsistency, as earlier (before A4 introduction) we stated A2>A1 and A4 being identical to A2 the ranking should not change.
Method2 — proposed to divide each relative value by the maximum value of the relative values.
After Normalization by Method2.
AHP Score (2/3, 19/27, 1/9, 19/27) → A2=A4>A1>A3.
Method2 of AHP solved the problem of ranking inconsistency but many researchers challenged that identical alternatives should not be considered in the decision process.
I wanted to buy a new mobile phone. So I spend 2–3 hours on Amazon after which I was able to shortlist 5 best smartphones. I was very confused about which phone will be the best value for the money of these 5. So, I followed our learned MCDM techniques —
WSM, WPM, and AHP Methods are simple, fast in the calculation, and easily adjust to fit many sized problems; not data intensive.
Shaurya Uppal
Shaurya Uppal is a Data Science enthusiast, who has worked on multiple data science problems in NLP, Ranking Algorithms, and Recommendation Engine. He has also published research papers in different IEEE conferences. He has a good sense of production, data problems, and can ameliorate business metrics.
LinkedIn: https://www.
Github: https://github.com/
StackOverFlow: https://
Research Paper: https://scholar.google.
Evaluation Metrics For Classification Model
12 Important Model Evaluation Metrics for Machi...
Multi-Criteria Decision-Making Using AHP in Python
Introduction to Bayesian Adjustment Rating: The...
Product Recommendation System Using RFM Analysis
Effective Cross Selling using Market Basket Ana...
Getting Preferred Combination of Attributes Wit...
Understanding basics of Recommendation Engines ...
Market mix modeling – Simplified!
How to Overcome Position Bias in Recommendation...
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